Skip to main content
A project groups related chats and gives Hive instructions and files that apply to all of them. Use one for anything you come back to: a client engagement, the quarterly board pack, a hiring round, month-end close. Instead of repeating “use our house style and these three files” in every chat, you set it once on the project.

Create a project

1

Open Projects

In the sidebar’s chat history, choose New project next to the Projects heading. Select the Projects heading itself to see every project you can open.
2

Name it

Give it a Project name — for example “Q3 board reporting” — and pick a colour.
3

Add custom instructions (optional)

Standing guidance Hive follows in every chat in the project: audience, tone, format, what to include or avoid. Up to 4,000 characters.
4

Start chatting

Type in the Start a new chat in … box at the foot of the project page, choose New chat on the Overview, or choose + on the Chats tab. A new chat opens in the project with what you typed already in the composer; nothing is sent until you send it. Every chat there carries the project’s instructions, files and skills.If the project is shared, a strip above the input shows who will see the chat: up to four of the people in it and “Visible to N people + future project members”. Choose OK, share with project before your first question; until you do, Ask stays off. If the project’s people change before you send, Hive asks you to confirm again.

Choose the model for a new chat

The Start a new chat in … box has the same model picker as the Ask composer, offering the same models: the ones your workspace allows you to use. Pick one before you start the chat, and the chat opens with that model chosen in its composer, just as if you had picked it in Ask. The first answer uses it, and it stays chosen for your next questions until you pick another. Leave Workspace default (Hive Auto when your workspace routes automatically) selected to let your workspace and personal settings decide. When your workspace has Auto mode set up, Hive Auto is also a choice of its own there. The choice applies only to the chat you are starting. A project does not keep a default model, so the next chat you start from the project begins on the workspace default again. To attach files or choose tools, start the chat and use the full composer: the + and Tools buttons in the project’s box are not available there.

Organise projects in the sidebar

Your projects are listed under the Projects heading in the sidebar. Each one shows as a folder in the project’s colour; select the folder to show or hide the project’s chats.

Change a project’s colour and icon

Open the project’s ⋯ menu in the sidebar and choose Colour and icon (on the Projects page, the same item is in each project’s ⋯ menu). Pick one of the eight colours and one of twelve icons, such as a building, a chart or a globe, then choose Save. The sidebar shows the icon in place of the folder, in the project’s colour, and the Projects page shows it on the project’s card. The colour and icon belong to the project, so everyone it is shared with sees the same ones. Only the project’s owner and its editors can change them. Changing the colour or icon does not move the project in anyone’s list; renaming it or changing its instructions still counts as a change.

Reorder your projects

Put your projects in the order you want them in the sidebar:
  • Drag a project up or down the list and drop it where you want it. A line shows where it will land.
  • Use the menu: open the project’s ⋯ menu and choose Move up or Move down.
  • Use the keyboard: move focus to a project in the sidebar and press Alt+↑ or Alt+↓. Screen readers announce the project’s new position.
The order is yours alone: reordering a project someone shared with you never changes their sidebar, and anyone a project is shared with can place it in their own list, viewers included. Projects you have not placed yet, such as a new one or one just shared with you, are listed after the ones you placed, most recently changed first. The Projects page keeps its own sort menu and is not affected.
Projects cannot be put inside other projects. To keep related work together, give the projects the same colour or icon and place them next to each other.

Manage projects from the Projects page

Select the Projects heading in the sidebar to open the Projects page. It lists every project you own and every project someone has shared with you. Each card shows the project’s colour, name and description, how many of your chats, files and skills it has, up to three of the people with access (their profile picture, or their initials), your role (Owner, Editor or Viewer) and when it was last active. A project was last active when it, its people or its settings last changed, or when you last used one of your chats in it, whichever is later. A chat counts once someone has asked something in it: a new chat you only uploaded a file into or picked an agent for is not counted, does not make the project active, and is not listed. Above the list:
  • Search projects finds projects by name or description.
  • All, Owned by me, Shared with me and Archived filter the list. Shared with me is every project someone else owns. Archived projects appear under Archived only.
  • The sort menu orders projects by Last active (the default), Name or Created.
  • The two buttons on the right switch between cards and a compact table. The table shows the same projects, with the same menu on each row.
Each project’s ⋯ menu offers only what your role allows: Delete asks you to confirm first. The project’s chats are kept and move back to your unfiled chats; its instructions and files are deleted (see Project files are a Library folder). Workspace admins can open a project they were not added to from a direct link, read-only. It is not listed on their Projects page.

Leave a project

To stop seeing a project someone shared with you, open its ⋯ menu on the Projects page and choose Leave project, then confirm. You lose access to the project straight away: its files, skills, instructions and the other members’ chats. The project’s owner can add you again.
  • Your chats stay in the project. Chats you filed in it are not moved: the project’s members can still read them, as they could before. You can still open your own chats from search.
  • The owner cannot leave their own project. To stop using it, delete it.
  • You can leave even when your workspace has turned off chat sharing, because leaving only removes access.

Archive a project

When a project’s work is done but you want to keep it, archive it instead of deleting it. Only the project’s owner can archive or restore it. Choose Archive in its ⋯ menu on the Projects page, or Archive project in the project’s own ··· menu. Nothing is deleted. An archived project:
  • is hidden from the sidebar, from the project pickers and from the Projects page’s other filters, for everyone in it. Find it under Archived.
  • stays readable: its instructions, people, files, skills and chats can all still be opened and read, and a direct link to it still works.
  • takes no changes, and its chats take no new questions. Nobody can rename it, change its instructions, colour, icon, skills or people, add or remove pinned files, add files from the Library, start a chat in it or file a chat into it. In its chats, nobody can ask a new question, edit and resend the last one, approve or reject a pending action or confirm a Create or Run card, attach or remove a file, create, upload or import a document, open a Library file for editing, share the chat with someone new, or save to Drive. A chat in an archived project says “This project is archived — restore it to continue.” and its Ask button is off. Comments, and documents already open in its chats, stay editable. A Create or Run card pressed just before the archive still finishes and shows what it made, so it is never offered again after a restore. The project page says it is archived and offers its owner Restore.
  • does not count towards your limit of 100 projects.
People in an archived project can still leave it, its owner can still delete it, and a chat’s owner can still take their chat out of it (it then continues as an ordinary chat of theirs). To change anything else, restore it: choose Restore in its ⋯ menu (under Archived) or on the project page. A restored project counts towards your 100 projects again, so a restore is refused while you already have 100. The project’s folder in the Library is read-only too: while the project is archived, nobody can add, rename, move or delete files or folders in it. Its files can still be opened and downloaded. In the Library, Upload files and New file are off in that folder and any folder inside it, and the page says “This project is archived. Restore it from the project to upload or create files here.”

Add a chat to a project

You can file a chat you already started, from inside the chat or from the sidebar:
  • In the chat: choose Add to project in the composer, or the project’s name there if the chat is already in one, then pick a project. No project takes the chat out of its project.
  • In the sidebar: open the chat’s menu and choose Add to project or Move to project.
Filing a chat shares it with everyone who can open the project, including future members, and sharing a chat shares everything in it, including answers Hive built from your apps, files and Brain. So Hive first shows who that is and asks you to confirm with Move and share. If the project’s members change before you confirm, Hive asks you to review them again. Taking a chat out of a project moves it straight away. Only the chat’s owner can move it.

Ask Hive to add it

In your own chat on the web you can also just say it: “add this to the Plant project”, or “put the case study in Plant”. Hive knows your projects by name, so it never asks what Plant is. It shows an Add to Plant card listing what it adds:
  • This chat, filed into the project as above.
  • A file you sent in this chat: “this” with a file attached means the file. Hive copies it into the project’s files; the chat keeps its own copy. A file still being processed can be added once it is ready.
The card says that everyone with access to the project, including future members, can read what you add, and how many named collaborators the project has. Nothing moves or is copied until you press Add, and the same rules as the sidebar apply: you need to be the project’s owner or an editor, the project can’t be archived, and if its members change before you press Add, Hive adds nothing and asks you to look again. If the chat is added but a file then cannot be (the project is out of room, say), the card says so and offers just the file again. Once added, Open Plant takes you to the project. You can ask what is in a project too: “which projects do I have?” or “is the case study in Plant yet?” Hive reads your projects and a project’s files the way the Projects page lists them.

Inside a project

Above the tabs, three cards summarise what every chat in the project inherits: Instructions, Context (the pinned files) and Skills. Choose a card to edit the instructions or open its tab. On a phone the cards stack in one column. A project page opens on its Overview and has four tabs: Choose Edit instructions to change the project’s Project instructions at any time. Changes apply to the next message in every chat in the project. To link straight to a tab, add ?tab=chats, ?tab=files or ?tab=skills to the project’s address. Without it, the project opens on the Overview.

Activity on the Overview

The Activity card shows the five latest things that happened in the project, newest first, one line each (point at a line to read it whole). Show all lists the rest of the latest 30, and Show less folds them away again:
  • someone was added, had their access changed, was removed, or left;
  • a file was added to the project’s files, credited to whoever added it, on the project page or in the Library;
  • a chat was started in the project, once someone asked something in it (choose its title to open it);
  • a skill was written for the project;
  • the project was created.
Everyone who can open the project can read its activity, including workspace admins who open it from a direct link. Renaming the project and editing its instructions are not recorded, so they do not appear. Because the feed names the chats started in the project, it is not available to AI clients connected through the Hive MCP server.

People and roles on the Overview

The People card lists everyone with access: the owner first, then each person with their role. If you own the project, change someone’s access there with Can view or Can edit, or choose Remove to take it away. Everyone else sees the roles but cannot change them. When your workspace has turned off chat sharing, you can still lower someone’s access or remove them, but not give anyone more access.

Add skills from the library

On the Skills tab, choose + and then Add from library. The Add skills list shows every skill you can use, in three groups, and the search box searches all of them:
  • Your Library: your own skills and the skills shared with the workspace on the Skills page. Each shows a Workspace or Yours tag.
  • By Hive: the skills in Hive’s skill packs, tagged with their pack.
  • Workspace packs: the skills in packs your workspace uploaded, tagged with their pack.
Packs an admin made unavailable are not listed, and you only ever see your own workspace’s packs. Each skill shows the first sentence of its description; hover over it to read the rest. Choose a skill to add it to the project. Choose it again, or choose x on the skill in the Skills tab, to remove it from the project.

Library skills are linked

Choosing a skill from Your Library links it to the project:
  • A linked skill is not copied. It stays in the Library, marked From library on the tab, and when someone changes it on the Skills page the project uses the changed version.
  • A workspace skill applies to everyone’s chats in the project. One of your own skills applies to your chats in the project only, because nobody else can read it. To have it apply to everyone, share it with the workspace first.
  • Removing a skill from the project removes the link only. The skill itself is not deleted.
  • Any owner or editor of the project can link and remove skills, including workspace skills they did not write. You can only link a skill you can see.
  • A skill can be linked to up to 20 projects.

Pack skills are copied to your Library

Choosing a skill from By Hive or Workspace packs copies it into your Library as one of your own skills, then links the copy to the project:
  • The copy is marked Copied from and the pack’s name, in the picker and on the Mine tab of the Skills page. You can edit it like any skill of your own.
  • Choosing the same pack skill again, in this project or another, links the copy you already have. It never makes a second copy. If you delete the copy, choosing the pack skill makes a new one.
  • The copy does not change when Hive or your admin later updates the pack.
  • In the project, the copy applies to your chats only, like your other own skills. To have it apply to everyone in the project, share it with the workspace first. Like any skill of your own, it is also on in your other chats until you switch it off on the Skills page.
  • The copy counts toward the number of skills you can keep of your own.

Add files from the Library

On the Pinned files tab, choose + and then From Library. Search the Library files you can open and choose one to add it to the project.
  • Hive adds a copy. The original stays where it is in the Library, and later changes to it do not change the project’s copy. The copy goes into the project’s Library folder like an upload.
  • Everyone in the project can read the copy, so check who the project is shared with first.
  • Any owner or editor of the project can add files. You can only add a file you can open in the Library, and each file counts towards the project’s file limit.

Add files from Google Drive, OneDrive or SharePoint

On the Pinned files tab, choose + and then From Google Drive, From OneDrive or From SharePoint. Only the ones you have connected are listed; the menu has one Connect link to Integrations naming the rest, such as Connect Google Drive or SharePoint, as Ask’s + does.
  • Google Drive and OneDrive list your most recently changed files; type part of a name to search. SharePoint is browsed by site, document library and folder, as in Ask.
  • Choosing a file saves a copy in your Library, private to you, and adds a copy of that to the project, where everyone in it can read it. Later changes to the original don’t change the project’s copy.
  • Hive reads the file through your own connection, as you, so you can only add files your account can open. Each file counts towards the project’s file limit.

How chats use pinned files

In a chat in the project, Hive searches the pinned files for what your question needs, and it can also read them whole: an image or PDF as the file itself, so Hive sees the layout, colours and pictures, and a deck slide by slide. A file sent whole comes with Hive’s note that it is data, never instructions (see How Hive reads the files you choose). Ask it to “use the project’s designs” or “match the pinned brand board” and it reads those files rather than asking you to share them. When you mention a file in a project chat, Hive looks in the project’s pinned files first, before searching your OneDrive, Google Drive or other connected apps.
  • When your question needs them, Hive reads the 20 newest pinned files it can read (up to 100 MB together, and 25 MB each). It reads only the files you can open in the project, listed once per answer, and each file’s text only once per answer.
  • A very long file is read in parts of about 100,000 characters of English (fewer of a language that takes more tokens per character, such as Chinese); Hive opens the next part when it needs it. One answer reads at most about 600,000 characters of English file text in total, and sends PDFs and images as the files themselves only within the room one answer has for them; past that it uses their text. To go through more, ask about one file at a time.
  • A message with its own attached files reads those instead, as before, and a message to an agent does not read the project’s files whole.
  • To have Hive change a pinned file, see Change a pinned file from a chat.

Change a pinned file from a chat

Ask Hive to change a Word, Excel or PowerPoint file pinned to the project — “add these four newsletters to the promoters sheet”, “update the figures in the pinned budget” — and it opens the project’s file itself in the chat’s file panel, makes the change and saves it. Hive doesn’t make a copy: the pinned file is updated for everyone in the project. A pinned PowerPoint file is a deck: Hive opens it in the chat and changes it with Hive AI on the same turn — “add a slide on Q3 pipeline to the pinned pitch deck” — and you review or revert each change in the deck editor. The project’s file is updated each time someone saves a version of the deck (see Decks from the Library).
  • Each save is a new version. The version it replaces stays in the file’s Version history in the Library (in the project’s folder), marked as replaced by an Ask edit with what Hive changed. Anyone who can edit the file can Restore it there, and a restore can itself be undone. Hive’s answer says the project file was updated and that the previous version can be restored.
  • Only people who can edit the project. Hive offers this to the project’s owner and editors with the Operator role or above in the workspace, in their own chats in the project. For a project viewer, or a file that isn’t Word, Excel or PowerPoint, Hive says plainly that the project file was not changed and gives you the changes to make, or offers a new file with them.
  • Someone else’s change is never overwritten. If the file changed after Hive opened it, Hive offers its edit as a proposal for you to review instead of saving over the newer version; see Edit a Library file in Ask.
  • Attaching a copy of a pinned file to a message gives Hive a separate file of the chat to edit; the pinned file stays as it was.

Use a pinned file as a design

A PowerPoint, Word or Excel file pinned to the project can be the design of a new file, or of the file you have open: “make a launch deck on the Brand deck design”, “apply the pinned brand template to this document”. Hive takes the look — a deck’s slide masters, layouts and theme, a document’s styles, header and footer, a workbook’s cell styles — from a copy of the pinned file, and never changes the pinned file itself.
  • The copy is saved as a Private file template of your own in the Library, named after the pinned file and its version, such as Brand deck (project copy 1a2b3c4d5e6f).pptx, and Hive checks it like any file template before it saves it: a file that fails the check is not copied at all. Asking for the same unchanged file again reuses that copy. After the pinned file changes, Hive makes a new copy, so you get its latest look; files made on an earlier copy keep theirs.
  • Hive can use only a pinned file you can open in the project, the same files it reads for you, and only once it has been fully read and passed Hive’s safety checks. Saving the copy needs the Operator role or above; with another role, Hive uses only your Library file templates.
  • A Library file template you can use comes first: a pinned file is used only when no template has the name you gave, and the answer names the copy it used. In a chat shared with you, pinned files are never a design: Hive can give the open file a Library template’s look, and a new file it makes there takes no design. See Apply a template’s design.
  • You don’t have to name it: when Hive makes a new file in the project’s chat, it sees the names of the project’s pinned Word, Excel and PowerPoint files and prefers a pinned design that fits. See How Hive designs a new presentation.

Project files are a Library folder

Every project has a folder in the Library with the project’s name, labelled Project. It holds the project’s pinned files, and it is the same set of files in both places:
  • A file you upload on the Pinned files tab is filed into the folder once Hive has read it. Until then it shows as processing on the project page only.
  • A file you add to the folder in the Library, including in a subfolder, is a project file too: every chat in the project can draw on it.
  • Removing a file from either place removes it from both.
  • Choose Open in Library on the Pinned files tab to open the folder.
The folder belongs to the project. Its people are the project’s people, with the same access: editors can add and remove files, and viewers can read them. When someone leaves the project, they lose the folder too. You rename, share and delete it from the project, not from the Library. Deleting a project deletes its folder and the project owner’s files in it; files other people added to the folder move to the top of the Library. Within about 20 minutes Hive permanently deletes each deleted file’s stored copy, the text Hive read from it and its search index, unless the same file is still used elsewhere in the workspace. See Deleted files. In the Library, the folder’s menu offers Open project in place of sharing, renaming and deleting. Workspace admins can read a project without being added to it, but the Library shows its folder only to the project’s people. You can also give an agent a project as a source. See Give an agent a project.

Share a project

Projects are private to their creator by default. To work on one with colleagues, share it with named people in your workspace and choose their access:
  • Editor — can chat in the project and change its instructions, files and skills.
  • Viewer — can read the project. They see “You have view-only access to this project.”
To share a project you own:
  1. Open the project and choose Share.
  2. Under Add people, type part of a colleague’s name or email. The people who match drop down under the search box; click one, or use the arrow keys and press Enter. They are added with Can view access. Members without a seat aren’t offered: they can do nothing in the workspace until an Owner or Admin gives them one.
  3. To give them more access, change Can view to Can edit next to their name.
To stop sharing with someone, choose Remove next to their name. Copying the project link does not give anyone access: only the people listed in Share, and workspace admins, can open the project. The top of the project page shows up to three of the people with access to the project. Each person appears as their profile picture, or as their initials if they have not added one. Hover over a picture to see the person’s name. Only people in the same workspace can be added, and workspace admins can read projects but being an admin does not make you a project owner or let you reshare it. Your shared projects are listed under Settings → Account → Shared projects.
Sharing a project shares its chats, instructions and pinned files — not your connected accounts. Each person’s questions use the connections they are allowed to use.
A chat in a project can also be shared on its own with someone who isn’t in the project. Their questions in that chat follow the project’s instructions and skills too, so every answer in the chat is shaped the same way, and Hive can tell them what those instructions say. They still don’t get the project’s pinned files, can’t open the project, and can’t see its other chats.

Limits

A project counts every file it lists: everything in its Library folder (including files added from the Library) and any upload still shown as being read, held for review or failed. Once it lists 50, uploads to the project are refused until you delete a file, in the project or the Library. Adding files to the folder from the Library is not refused, but those files count too. The Pinned files tab lists all of them, even past 50. An upload that would take the project past 50 files is refused with a message that names the cap, and nothing from it is added.

Tips for good project instructions

  • State the audience and the output. “Board members; one-page summaries with a numbers table first.”
  • Name the sources to prefer. “Use the pinned management accounts before live Xero data.”
  • Say what to avoid. “Never include client names in drafts meant for external sharing.”
  • Keep them stable. Put one-off requests in the chat, not in the project instructions.

Ask Hive

Citations, files and actions.

Library

Files and folders for your workspace.

Agent Studio

When a project should become a reusable agent.

Workflows

Automate the repeatable parts.