Workspaces And Navigation
Open /app on your deployment to enter the workspace. The workspace selector determines which agents, credentials, and usage you are working with. Check it before creating an agent, connecting an account, or changing shared settings.
Choose a workspace
| Workspace | What belongs here | Who can access agents |
|---|---|---|
| My workspace (no Team selected) | Your private work inside the Organization | You and Organization roles authorized to administer agents |
| Organization / Team | Shared work for an assigned Team | Authorized Team members and Organization agent administrators |
Private work in My workspace remains subject to company policy and administrative oversight. Membership in the same Organization does not automatically give coworkers access to each other's private agents. Team membership and Organization roles are separate; see Roles And Permissions.
Selecting a different workspace changes the view. It does not move an agent or copy a connected account. Use the agent's ownership controls for transfers, and review credentials and recipients afterward.
The sidebar selector shows the Organization name above My workspace or Team: [name]. The breadcrumb also names the current workspace. Team entries in the selector include their current agent counts, including paused agents.
Find the right control
These paths are relative to your deployment's address, such as https://your-deployment.example.
| Destination | Path | Use it for |
|---|---|---|
| Agents | /app/agents | Create agents, open chats, and inspect work |
| Outbox | /app/outbox | Review email waiting for approval, where enabled |
| Integrations | /app/integrations | Connected apps, MCP servers, and Organization API specs |
| Secrets | /app/data/secrets | Reusable credentials in the selected scope |
| API keys | /app/data/api-keys | Developer credentials available to your role |
| Usage | /app/usage | Consumption and limits for the selected workspace |
| Governance overview | /app/governance/overview | Admin readiness and a map of the sections below |
| Access | /app/governance/access | People and roles, Teams, org chart, access reviews, identity, and machine identities |
| Policies | /app/governance/policies | Authentication, agent creation, messaging, data retention, security rules, and network access |
| Evidence | /app/governance/evidence | Agent runs, data flow, security activity, rule findings, and exports where enabled for your role |
| License | /app/governance/license | Company term, seats, and license import available to your role |
| Organization settings | /app/settings | Organization name and logo, AI providers, email delivery, shared templates, and custom instructions |
| Profile | /app/profile | Your account settings |
Open an agent to use its chat and working panels. Open Settings for its charter, activity state, contacts, integrations, and ownership. The Agent Settings guide explains those controls.
Missing agents or controls
First check the workspace and selected Team. Then check that your invitation was accepted and your membership is active. A Viewer can see permitted resources without being able to send messages or edit them. Specialized administrators see controls for their assigned responsibilities.
An empty Agents page names the workspace you are viewing. If agents exist in other Teams you can access in the same Organization, Browse Teams shows those destinations and their agent counts. Select a Team to open its agents. From a global personal workspace, this list includes accessible Teams across your Organizations. Creating a private agent remains a separate action in your current workspace.
Some features depend on deployment configuration or entitlement. A missing control does not necessarily mean the resource was deleted. Ask an Organization administrator to check access before recreating agents or reconnecting accounts in another scope.
Older /console/... bookmarks may redirect into the current app. Use the current navigation when following older screenshots. See Troubleshooting for other common access and workflow problems.