Projects
Projects
A project is the thing everything else hangs off: tasks, sprints, ideas, costs, repositories, documents, domains, servers, mail and monitors all point at one (module projects). Who is on a project decides who can see its tasks, sprints and brain.
In the sidebar under Projects → Projects.
What you see
The Projects page
The Projects page shows the projects you can see, ten at a time, loading more as you scroll. Show projects as switches between Cards and Table, and Filter projects narrows the list.
Each card shows the project's colour and name, and how it is doing in a few words: Overdue tasks, Sites down, Needs attention, what it spent this month (or Not priced), and Last activity (for example "3 days ago", or "No activity yet"). The whole card opens the project. The ⋯ on a card holds Apply a kit, Readiness, AI spend, Edit and Delete, as far as you may use them.
You can Pin to the top any project. Pinned projects come first on your own Projects page. Pins are yours alone.
The table shows the same projects as rows, with key, status, tags, and links to the repository and live site.
With no projects yet, the page says "No projects yet" and offers New project.
A project's home page
Opening a project shows its home page:
- The project's name, kind, stage, live site and repository, and an About line.
- How it is doing: the same signals as its card, Spend this month against its budget as a bar, and Recent activity.
- Everything filed under this project, one section per kind of thing: tasks, sprints and epics (as plans), ideas, documents, outlines, folders, links, reminders, domains, servers, apps, monitors, mailboxes, mail addresses, social accounts, connectors and more. Each section shows a few lines and Show all. A domain stored in several places (at the registrar, in Cloudflare, in the mail server) is one line saying how many listings it has; open it to see each listing.
- Attach: file something that already exists under this project. The picker searches, lists unfiled things first, and says when something is under another project: attaching moves it here.
- Remove on a line (or Remove all on a several-listing line) takes it out of the project. Nothing is deleted. Tasks can be moved to another project but are never just removed.
- After Attach or Remove, Undo puts each thing back where it was.
- Edit project, and in the ⋯: Brain and Readiness.
Each line opens the item itself in its own module. A section only shows things you may see.
Which projects you see
You see the projects you created and the projects someone added you to, at any level. Administrators see every project in the workspace. A caller that does not act for a person sees none.
What you can do
Create a project
- Press New project.
- Fill in Name. The other fields are optional:
- Key: a short code such as
WEB. Left empty, the key becomes the whole name upper-cased, so type one if the name is long. The key also names the project in document addresses, so choose it once. - Colour, Description, Repository and Live URL.
- Kind: ecommerce, logistics, saas, content, service or internal. It decides which readiness checklist applies on top of the base one. Leave it at "Not sure" rather than guess.
- Stage: idea, building, launched or scaling. It sets how far along readiness expects the project to be.
- Monthly budget and Budget currency (USD unless you change it). If recorded costs in a month pass the budget, the project's managers are told once that month. Spend in another currency is converted where a rate exists.
- Key: a short code such as
- Press Create. You become the project's manager.
Start a project from a kit
- Press New project from kit (or press ⌘K and type the kit's name).
- Pick a kit, write the project's name and, when the kit uses one, its address.
- Pick the model the kit's team should run on, or leave the default.
- Read the preview, then press Create. The project, its board and first tasks, the brain outline, a monitor and the team are made at once.
- Each outside step (a domain, DNS records, an app, a mailbox) waits on its own card under Approvals.
- The result offers the rule presets named for each new agent; press Apply on the ones you want.
If there are no kits yet, the dialog offers to add the starter kits. To fill an existing project, use Apply a kit in its ⋯. See Kits.
Edit a project
- Press Edit in a card's ⋯, or Edit project on its home page.
- Change any field and save.
Archiving, tags, a logo, status and the project's documentation site are changed through the agent tools, not this form.
Delete a project
Press Delete in a card's ⋯ and confirm. This deletes the project for good, with its board, tasks, members, repositories, shortcuts, vitrine and log. Modules that keep rows about a project, such as its brain and its project facts, remove theirs too. To put a project away instead, archive it. Deleting needs projects:manage and manager level on the project.
File things under a project
Use Attach on the project's home page, or let the Librarian find what belongs where. Something already under another project moves here, which needs editor level on that project too.
Members, repositories and the rest
These are reached through the agent tools (and the API) rather than this screen:
- Members, at one of three levels: a viewer reads, an editor changes the project, and a manager also changes who is on it. The last manager cannot be removed or lowered.
- Repositories, linked so commits and releases can be attributed to the project.
- Shortcuts: a row of links at the top of the project.
- Vitrine: a tree of labelled facts, text or numbers, about the project.
- Activity log: lines saying what was done or what went wrong. This is the narrative people read, not the audit trail.
Who can do what
| Permission | Label | Lets you |
|---|---|---|
projects:read | View projects, and pin them on your own Projects page | Open Projects, read the projects you can see, and pin them |
projects:write | Create and edit projects | Create projects, edit them, link repositories, attach and remove things, and keep shortcuts, vitrine and log |
projects:manage | Archive projects and manage members | Delete projects and change who is on them |
A permission is not the whole story. On a given project you also need the right level: editor to change it, manager to delete it or change its members. The person who created a project is always its manager. Administrators count as managers on every project. A viewer sees the home page without Attach or Remove. See People, roles and permissions and Sharing and visibility.
What runs on its own
Nothing in this module runs on a schedule. The monthly budget check belongs to Costs. The nightly filing of things under projects belongs to the Librarian.
For agents
Agents can find, create and update projects, file things under them, and keep members, links and notes up to date. Changes go through your approval rules. Deleting a project, detaching things, making its documentation site public or private, changing members, and removing a shortcut or vitrine entry are classed as destructive: under the default approval policy a person is asked first. Each approval card says plainly what it is, such as "Archive X" or "Change X: fields", and attach and detach cards name the project and the things. See Agents and approvals.
Find and read
projects.list, projects.find, projects.get, projects.home (everything filed under a project, by kind), projects.activity, projects.cost (recorded spend so far, per currency), projects.suggestKinds (a suggested kind and stage, with reasons, for a person to confirm), projects.attachableKinds, projects.unassigned (everything filed under no project, with a suggested project where a name lines up).
Create and change
projects.create, projects.update, projects.remove, projects.setVisibility, projects.log, projects.undo (take back a change an agent made from your own message).
File things under a project
projects.attach, projects.detach. Only the link goes when detaching; nothing is deleted. Tasks cannot be detached, only attached to another project.
Repositories
projects.connectRepo, projects.disconnectRepo. The repository itself is untouched.
Members
projects.addMember, projects.setMemberLevel, projects.removeMember.
Shortcuts and vitrine
projects.addShortcut, projects.removeShortcut, projects.addVitrineEntry, projects.updateVitrineEntry, projects.moveVitrineEntry, projects.removeVitrineEntry.
Over MCP the same tools are named projects__list, projects__create and so on. See API keys and MCP access.