Projects and teams¶
Everything in Autopoetic — conversations, the knowledge repository, agents, API keys — lives inside a project, and projects belong to your customer account. Multiple people can share a project with different roles.
Projects¶
From the Projects page you can create projects, search and filter by name, and see each project's conversation count and last activity.
When creating a project you pick a mode:
- Fresh start — an empty project.
- Copy knowledge from a project — forks an existing project you administer. The fork copies the knowledge repository, agent templates, project-level agents, preambles, and each agent's accumulated personality — the forked project's agents start as the same characters yours have become. Conversations, tasks, API keys, and integrations are not copied, and the new project gets fresh encryption keys.
Project settings¶
On the project detail page (admin actions shown; editors and viewers see them read-only or not at all):
- Rename the project.
- Context — the project preamble applied to all conversations (see your first chat).
- Agents — custom project agents (see agents).
- Members — invite and manage teammates.
- API Keys — programmatic credentials (see below).
- Project Knowledge — links to the knowledge graph, changelog, and events (see the knowledge repository).
- Leave / Delete — leaving removes your access; deleting requires typing the project name and permanently destroys all conversations and data.
Roles¶
| Role | Can do |
|---|---|
| Viewer | Use Ask mode and read the knowledge repository. No conversations. |
| Editor | Everything a viewer can, plus conversations: chat, fork, revert, publish. |
| Admin | Everything, including project management, members, API keys, fork, and delete. |
Inviting teammates¶
Admins invite members by email with a role — the invitee must already have an Autopoetic account.
- Invitations are listed under Pending Invitations until accepted, declined, or expired, and can be canceled.
- Invitations expire after 3 days.
- Invited users see the invitation on their Invitations page, where they can accept or decline.
- The project always keeps at least one admin — the last admin cannot be removed or leave.
API keys¶
Admins can create API keys for programmatic access — the single credential used by every API surface (see the API overview):
- Open API Keys on the project detail page and create a named key (e.g. "Production CI").
- Copy the credentials immediately — they are shown only once, while the page is open.
- Exchange them for an access token as described in API authentication.
Deleting a key immediately stops any integration using it.
Security¶
Conversations and knowledge are encrypted at rest — the service decrypts them while you are actively chatting in order to respond, and they are stored encrypted otherwise. Each project has its own keys; forking a project generates fresh ones.