Domains
A domain groups context into a named set that agents ask for by name: entities (one per object), the briefs it delivers, and the skills it carries. Domains are the product’s one access model — whoever holds a domain receives what it carries.
What a domain is for
Teams need different context from the same objects. A domain is a purpose-built access point for one of them: Sales Desk carries Account, Opportunity and Contact curated for pipeline work, while Finance carries the same accounts plus payment terms and invoice history.
A “Sales Desk Context” tool names the sales_desk domain, and the planner picks it by purpose. What the domain carries lives in the domain record, so you change the tool’s coverage without touching the tool.
One entity per object
A domain maps each object to exactly one entity:
| Object | Sales Desk | Finance |
|---|---|---|
| Account | account_360 | account_360 |
| Opportunity | opportunity_360 | finance_view |
Both use the same account_360. A domain references entities rather than owning them, so editing it changes both. Adding a second entity for one object is refused, and the conflict is named.
What a domain carries is separate from an entity’s home — the domain whose managers maintain it. Home matters only under domain management.
Change it anytime
Add or remove from either side: a domain’s Roster tab, or an entity’s own Domains tab. It is one fact with two doors. Every tool naming the domain picks up the change on its next call, with no redeploy. This is not versioned; each entity still serves whatever version it has active.
Rows you have no rights over are shown, marked and not editable: hiding a domain you cannot change would answer “who receives this?” with a lie.
Ask about an object the domain does not cover and the call names what it does cover, so the agent can re-plan.
When to add one
Start without one — records load through each object’s default entity. Add a domain when a second team needs its own view of an object, or when a tool should be named for a job so a planner picks it by intent.
Notes
- Record sharing on the domain decides who can discover it. Install shares General with everyone; give someone another domain and General drops away for them. → Domain access
- A domain never grants or restricts data access. Every query runs as the calling user, so a domain widens what an agent may ask for, never what its user may see. → Security
- Each domain has a colour and an icon, both cosmetic. Agents are never told about either.
- Deleting a domain leaves its entities alone, but they reach nobody until another domain carries them. The default domain cannot be deleted.
What’s next
- Domain access — who sees which catalog
- Building domains — the how-to