Manage
Manage is where a project's operating parts live. Think of it as the "how this project runs" section: the AI agents that do the work, the credentials those agents are allowed to use, and the support channel back to the ACE team. That is different from project Settings (who owns it, what it is called) and from Workspaces (who is a member).
There are three pages here:
- Agents: the agents available to a project, the shared context every one of them reads, and each agent's own tools, model, and prompt. Project-scoped.
- Secrets: a per-project vault for the API keys and tokens agents need to do their work. Project-scoped.
- Support: open a ticket and chat with the ACE team, including what it means when ACE staff temporarily step into your workspace to help. Workspace-scoped (not tied to a single project).
A fourth page, Usage, also lives under the same Manage sidebar group, but it is billing-and-credits territory. See the Billing guide instead, specifically Usage.
Where to find it
Left sidebar → Manage, containing Agents, Secrets, and Support (plus Usage, see above). Agents and Secrets always act on whichever project is currently selected in the sidebar; Support is not project-scoped.
Who can do this?
| Page | To view | To manage |
|---|---|---|
| Agents | agent:read | agent:manage, and only while the project is active or mutable |
| Secrets | secret:read | secret:manage, and only while the project is active or mutable |
| Support | Any workspace member | Any workspace member (there is no separate "manage" tier; you manage your own tickets) |
Agent and secret grants are set per project member in Settings → Workspace → People & access, under the Knowledge & automation and Secrets groups respectively. See the People and access guide.
How this connects to the rest of the platform
- Agents read Knowledge. The "Knowledge" workspace layer on the Agents page is the same reference library covered in the Knowledge guide, including the codebase maps Discovery generates automatically.
- Agents draw tools from Integrations. A tool tied to a provider (GitHub, Slack, an MCP server) stays selectable but dormant until that provider is connected. See the Integrations guide.
- Secrets back MCP servers. When you connect a custom MCP server from the Agents page, its optional auth reference points at a key stored in Secrets, and the value itself never leaves the vault. See MCP servers.
- Support tickets can lead to a support session. If ACE staff need to work directly inside your workspace to resolve a ticket, that access is temporary, scoped, and always shows up afterward in your workspace's own Audit log. See Support mode and the Audit guide.
- Agent saves are commits, not instant updates. Every save on the Agents page writes to your project's docs repo; it takes about a minute or two to actually reach the running agents. Secrets, by contrast, apply immediately, with no sync delay.