Projects
A project gathers the chats, files, notes and links for one piece of work, gives every chat in it the same instructions and knowledge, and lets you bring in collaborators with a role.
Updated October 2026Library and knowledge3 of 3
Short answer
Create a project
- Step 1
Start a new project
Choose Projects in the sidebar, then New project. The list page filters by All, Mine, Shared and Recent, with pinned projects on top. - Step 2
Name it and write the instructions
The name is the only required field. Instructions act as a system prompt for every chat in the project; they are added beneath your organization’s instructions, never in place of them. A description helps collaborators and shows on the overview. - Step 3
Pick default knowledge bases
Select the knowledge bases every chat in the project should search. A chat can still choose its own set, which replaces the defaults for that chat. See Knowledge bases.
The project workspace
A project opens at /projects/<id> with tabs across the top. Comments live in a side rail rather than a tab, and members are managed from the Share dialog.
| Tab | What it holds |
|---|---|
| Overview | Description, instructions, pinned notes and recent activity at a glance. |
| Notes | Block-editor documents you write inside the project, with pinning and “use as context”. |
| Files | A folder tree of Library files plus any connected SharePoint or OneDrive folder. |
| Links | Web links with a preview, tags and “use as context”. |
| Chats | Every chat filed in the project, whoever started it, and a button to start a new one. |
| Settings | Name, description, instructions and default knowledge bases; delete the project. Editors and owners only. |
Files
The Files tab is a folder tree. Add files by dropping them on the page, with Upload or Upload folder, or with From Library to link files you already have. Uploads land in your Library first and are then linked into the tree, so the same file can sit in several projects. Adding and arranging files needs the editor role.
Connected SharePoint and OneDrive folders
An editor can connect one SharePoint or OneDrive folder to the project from the SharePoint card. Akili stores references to the items, not copies, and keeps the tree current: a delta sync runs every 15 minutes and Microsoft change notifications trigger one sooner, picking up new files, renames, moves and deletions. Sync now forces a pass.
- Delegated or application mode. Delegated uses the connecting member’s Microsoft account; application mode uses an organization-level Microsoft app registration your administrator set up.
- Index the folder. Turn indexing on and Akili creates a knowledge base named after the project with a “SharePoint” suffix, adds it to the project defaults and keeps its documents in step with the folder.
- Push a note. A project note can be pushed to the connected folder as a Word document.
Chats
Start a chat from the Chats tab, or file an existing chat you own into the project. Starting or continuing a chat needs the editor role; viewers and commenters can read every chat in the project. The model comes from your picker, not from the project.
Each turn in a project chat carries, in addition to your message:
- The project instructions.
- A context block with the names of the default knowledge bases, the notes marked “use as context” (up to a cap), the title and description of links marked the same way, and the paths of the project files.
- Passages retrieved from the default knowledge bases, or from the knowledge bases the chat selected instead.
Notes and links
A note is a document written in the same block editor Studio uses, with a pin for the overview and a Use as context switch that adds its text to every chat in the project. Each note has its own address, so you can send a colleague straight to it. Deleting a note removes its comments.
A link must be an https address; duplicates are refused. Akili fetches a safe preview with the page title, description and image, lets you tag the link, and can mark it as context, in which case the title and description, not the page, reach the chat.
Comments
Open the comments rail to discuss the project as a whole, a note, a file or folder, or a link. Replies are one level deep. Mention a collaborator with @; only people who already have access can be mentioned, and a mention sends them an email. Posting needs the commenter role. The author can edit a comment; the author or an editor can resolve it; the author or the owner can delete it.
Members and roles
Open Share on the project to invite people by email, with an optional message. Your effective role is the highest of: owner, your direct membership, and the general-access role when the project is open to your organization. Only the owner manages members, general access and links.
| Role | Can |
|---|---|
| Viewer | Open the project, read notes, links, files and every chat in it. |
| Commenter | Everything a viewer can do, plus post and reply to comments. |
| Editor | Everything a commenter can do, plus edit settings, files, notes and links, start chats and continue them. |
| Owner | Everything an editor can do, plus manage members, general access and share links, and delete the project. |
General access
- Members only. Only invited members and the owner can open the project.
- Organization. Everyone in your organization gets the role you choose, without an invitation.
- Link. Anyone with a share link gets the role on that link.
Share links and the public page
- Step 1
Create the link
In Share, create a link for the whole project or for one folder or file. Choose the role (viewer, commenter or editor; a link can never grant owner), whether downloads are allowed, and an expiry of none, 7, 30 or 90 days. - Step 2
Send it
The link opens at/projects/shared/<token>. Only a hash of the token is stored, so a lost link cannot be recovered; rotate it to issue a new one. - Step 3
Revoke it when done
Revoke or rotate from the same dialog. An expired or revoked link shows an unavailable page. The dialog also counts how often each link was opened.
The public page shows the project name and the file tree, with a download button per file when the link allows it. Files from a connected SharePoint folder are never listed on the public page.
Inherited sharing
Everything inside a project follows your project role. You do not share chats, notes or files one by one: a viewer can read every chat and note, a commenter can discuss them, and an editor can change them and continue chats, including chats other members started. Members invited by email do not need to belong to your organization.
Good to know
- Chats outlive the project. Deleting a project detaches its chats and keeps them; everything else in the project is removed. There is no archive state.
- Uploads follow your plan. The upload buttons disappear when your plan does not include file uploads; otherwise the per-file size limit of your plan applies.
- Instructions stack. Platform preamble, organization instructions, then project instructions. A project cannot override what your organization set.
- Some tabs are deployment options. Overview, notes and links, and SharePoint connections, are each a setting an operator can turn off for an installation. If a tab is missing, ask your administrator.
- Mobile covers the basics. The Akili mobile app lists and creates projects and shows the overview, notes, chats and settings; files, links and sharing are web only.
Frequently asked questions
Do project files get read into every chat?
No. A chat in a project sees the project instructions, the list of file paths, pinned-as-context notes and links, and whatever the project’s default knowledge bases retrieve. To make file contents searchable, connect the folder with indexing on or add the files to a knowledge base and set it as a default.
Can I invite someone who is not in my organization?
Yes, members are invited by email address. If the address already has an Akili account it is linked at once; otherwise the invitation is honored when that person signs up. They get the role you chose, nothing else in your organization.
What happens to chats when I delete a project?
Chats are detached and kept in their owners’ chat lists. Files, notes, links, comments, members, share links and the SharePoint connection are deleted with the project. Only the owner can delete it.
Is there a limit on how many projects I can have?
No. Projects are not metered by plan. The per-file upload limit of your plan still applies to files you add.
Why can a visitor with a share link not comment or edit?
A share link can carry a viewer, commenter or editor role, but the public share page itself only reads and, when allowed, downloads. The higher roles take effect once the visitor signs in and the link is honored as their access to the project.