Projects
A project belongs to a client and is the hub for everything else: tasks, documents, time, features and decisions, chat, and the knowledge base. Project detail is the page people live on.
Find and open a project
Section titled “Find and open a project”Open Projects in the left rail.
- Switch Cards / List in the top bar. The choice is remembered in this browser.
- Search, status, and Archived sit on the list header.
- Each project has a permanent display number in the hive (it does not change if you rename it).
- You can favourite a project in this browser. Favourites do not change sort order for anyone else.
- Opening the hive’s support project (managers pick this in Organization settings) goes to Tickets when Redirect to Tickets is on. Turn that off and the same click opens the project board. The Tickets list stays in the left rail either way.
Cards show the client under the name, a thin progress bar with the task count under it, and, if set, a faded logo behind the content. The hive’s support project shows a headset mark where other cards show a description.
Members who have not been added to any project see an empty list and a note to ask a manager.
Create a project
Section titled “Create a project”Managers (and admins) create projects.
- On Projects, add a project.
- Name it. Pick a client, or leave the client unset if you must — most work should sit under a company.
- Optionally start from a template (built-in or one your hive saved).
- Open it.
A project channel is created at the same time. You do not set that up separately.
Project status vs task status
Section titled “Project status vs task status”The project has its own lifecycle: planning, active, on hold, completed, cancelled. That is not the task catalog. Completing a project is “this engagement is over.” Completing a task is “this card is done.”
Setting the project to completed or cancelled:
- Archives it.
- Closes leftover open non-support tasks in the same step. Recurring tasks do not spawn a next one.
- Support tasks stay open (residual work after close). See Support.
Reopening to planning, active, or on hold un-archives it. It does not restore the old task statuses.
Who can see a project
Section titled “Who can see a project”| Role | Access |
|---|---|
| Admin or manager | Every project |
| Member | Only projects they were added to |
Add people from project settings → members. Being in the hive is not enough. Assignees on a task must also be project members (managers bypass).
On the project page
Section titled “On the project page”The primary job is the task board, table, or map. Other sections stay closed until you open them, from the project’s section nav:
- Features, decisions, assistant
- Documents, time, Activity, automations
That is deliberate. Digests, files, and time exist — they are not a second toolbar shouting for attention.
Activity keeps the digest on top (What changed / AI handoff). The Log underneath is every event on this project — task names and other items are links.
The ⋯ menu on the project goes to settings and less-used actions.
Project settings (managers)
Section titled “Project settings (managers)”Open project settings from the project. The project name in the top bar goes back to the project.
Members. Who can open this project. Add a member (plus) sits next to Add everyone, then the Invited members list.
Statuses. Empty means “use the hive catalog.” A non-empty list is a full override, not a merge. See Tasks.
Board layouts. Up to 12 named column sets. See Boards.
Budget and currency. Optional. Members never see the budget figure or rates.
Logo. Upload, clear, or Find logo. Discovery looks at project files (and a linked Drive folder) for an image whose name looks like a logo. It only fills an empty logo — it will not overwrite one you set. After create, a search also runs on its own after a few hours.
Git remote. Optional repo URL and default branch. This exists so agents can tell they have the wrong project open, and so a linked pull request has a home.
Drive. On Team, attach a Google Drive folder and sync. See Plugins.
Templates
Section titled “Templates”Managers can save this project as a template (with toggles for which sections to include: features, tasks, decisions, notes, members). Templates are hive-wide.
Three built-ins always exist: software delivery, client website, support desk. You cannot edit or delete those.
Use a template for a repeating shape (retainer site, campaign, audit). Do not use it as a substitute for Propose from knowledge when the real brief is already in Documents — the proposal path reads the actual material.
Limits on a saved template are generous (hundreds of tasks). Subtasks-of-subtasks are not stored.
Progress on the card
Section titled “Progress on the card”The percentage is a cache: the mean of per-feature completion, plus a bucket for tasks that are not on a feature. It updates when tasks and features change. It is a signal for the list, not a timesheet and not billable hours.
Archived projects
Section titled “Archived projects”Two steps.
Mark finished. Set the project to completed or cancelled. You cannot add ordinary work. The exception is a support task — leftover client work after the engagement closed. These projects drop out of My Work, Schedule, and the dashboard (except those support tasks). Open the project itself, or turn on Archived on the Projects list, to see them. Reopen the status to bring it back.
Archive to file. Managers can pack the whole project (tasks, files, chat, meetings, knowledge) into a downloadable file from project settings. Starting that pack freezes the live project: the card, the project page, and chat all say Frozen, and nobody can change tasks or send messages until you cancel or finish. Download the file, confirm it, then remove the project from the hive, or Cancel archive to unfreeze and keep working. If a restore gets stuck, Cancel archive also unfreezes. Restore a removed project later from Settings → Cold archives, or by uploading the file.