Developer
Developers own the agent as a workload. They register it, mint credentials, point the client at a Gateway, and verify governed calls. They also wire Dome into the application when the agent runs in product code.- Agent identity and lifecycle
- Register agents and issue API keys
- Standing or delegated identity when the agent acts for end users
- Develop to authenticate, call tools and models, and handle denials
- Audit events to confirm outcomes
Security
Security owns what each agent may call, what content may leave a backend, and whether the audit trail can prove it. They author and simulate Rules, apply Guards, investigate denials, and export evidence.- Authorization model and scope hierarchy
- Rules, simulate, and Guards
- Quotas when spend is a security control
- Audit events and Export Data
Operator
Operators own tool and model connections, Gateways, grants, and the live signals that show the platform is healthy. They attach backends, expose Gateways, grant agents access, and triage live traffic.- Prepare environments and scope hierarchy
- Tools, models, and Gateways
- Stream Live Events
- Settings and integrations
Platform admin
Platform admins own tenancy, membership, who may administer Dome, and whether the estate stays operable and auditable as teams grow. They set access boundaries, prepare environments, and run export for oversight.- Scopes and permissions
- Manage access and prepare environments
- Stream Live Events and Export Data
- Settings and integrations
Next steps
- Tutorials — Get Started and Role track
- What is Dome? if you want the product overview first
- Setup AI assistant if you want an MCP-connected assistant while you work