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. That opens the project list.
- Switch Cards / List / Timeline in the top bar. The choice is remembered in this browser.
- Search and status sit on the list header, with a star and an archive icon. The archive icon lists finished projects on their own. The star hides every project you have not starred. Cards, List, and Timeline follow those filters. Hold the pointer on an icon to read what it does.
- 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, from its card or from the list. 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. Show in Projects (on by default) lists that project here, on the dashboard, and on a client file. Turn it off and those lists leave it out — Redirect to Tickets is hidden then, because there is no project row to open. The Tickets list stays in the left rail either way.
Cards show the client under the name. Move the pointer onto a card and the progress bars slide up and fade in, in the space the card already holds: accepted deliverables on top, tasks done under that. The task bar leads and its fill grows while it slides in. The deliverable bar follows a moment later. Moving the pointer away reverses that. A project with no deliverables keeps a faded bar in that spot. Hold a bar and a honey drop names the count and what it measures. The bars themselves show only the fill. The task bar counts verified or ordinary done work only. Unverified agent completions are not part of that count. The hive’s support project shows a headset mark where other cards show a description. Keep the pointer on a card and, after a few seconds, it lifts off its place. A faint skeleton stays in the grid so the other cards do not move. The lifted card grows toward the room it has: left when it is near the right edge, right when it is near the left, and the same for up and down. The bars, the favorite star, and the menu hide. Lines appear one after another, about a tenth of a second apart — a quiet day, tasks someone moved, work waiting on you. If you made a batch of tasks, that is the first line: how many came back and are waiting in a status, then who still has the rest. One or two tasks are a short indented list, with a faded # in front of the number. Names match Chat display under Profile, and the face sits beside the name. Task names in that feed are bold. The card does not say who is online. Moving the pointer off the card puts it back. Keyboard focus does the same after a few seconds. Hold Command, Control, or Alt and click the card to open that feed right away; the project does not open. A touch screen does not.
Members who have not been added to any project see an empty list and a note to ask a manager.
Timeline
Section titled “Timeline”Timeline is every project on one chart, in the same order as the list. The name and the length in days sit on the bar. The hive’s support project is on the chart when Show in Projects is on, and left off with Cards and List when that is off.
- A solid bar is the project’s start and end, when a manager has set them.
- A lighter bar is the span of dated tasks and deliverable targets. It is a forecast. Dragging it writes the project’s start and end. It does not move the tasks.
- A diamond is a milestone: a name and a date, and optionally the deliverables that reach it. It marks the date. It does not block a status, an acceptance, or a task. This is not a progress fee on an invoice.
- Weeks, months, and quarters are remembered in this browser. A line marks today.
- Managers drag a bar or a diamond, or use Edit dates and Add milestone on the row. Other people can look, and can open a milestone without changing it.
- A missed milestone is the only one drawn in the alarm colour.
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 |
The person who creates the project is added as a member. Add other 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.
Dates. Optional start and target end. Members can see them; only managers set them. The start date also anchors due dates when you create the project from a template.
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.
Links. Labels and addresses for this project, such as setup, staging, and production. In chat, /projects lists them. The label is what people click. Managers edit the list. Everyone on the project can insert a link.
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 press the archive icon on the Projects list, to see them on their own. 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.