Console
Share a database with your team.
Give each teammate access through their own account. People and their connected agents work with the same current state and database rules.
Open a database, then select Members. Membership applies to that database only. Only its owner can invite people, change roles, cancel invitations, or remove members.
Choose a role
| Role | Access |
|---|---|
| Viewer | Read records and schema, export projections, and authorize read-only MCP applications. Cannot write data, decide reviews, or create API keys. |
| Editor | Viewer access plus proposing updates, deciding reviews, creating API keys, and administering schema through authenticated console access. Cannot manage members. |
| Owner | Full database administration, including invitations and member roles. The owner cannot be changed or removed through Members. |
Give an analyst Viewer access to inspect and export current state. Give a support operator Editor access to propose updates and resolve reviews. Every write still goes through ontology and policy checks.
Invite and accept
- As the owner, enter the teammate’s email in Members and choose Viewer or Editor. Viewer is the default.
- Select Send invitation. The email link expires after seven days.
- The teammate opens the link and signs in or creates an account with the invited email. That email must be verified before acceptance.
- After acceptance, the database appears in their database list. They can authorize their own applications from Connections.
Pending invitations
The list shows sending, pending, expired, or failed delivery states. Cancel invalidates a pending invitation. To replace a pending invitation, cancel it and invite again. Send again is available for expired or failed invitations; it issues a new link and invalidates the old one.
Change or remove access
- Editor to Viewer: keys created by that member for this database are revoked, and their database MCP grants become read-only.
- Viewer to Editor: write permissions become available. Revoked keys are not restored; update read-only application grants separately if write access is needed.
- Remove: database access, the member’s keys, and their database application grants are revoked. Earlier observations and history remain.
Human and agent authority
OAuth access is limited by the member’s current role and the granted access level. API keys carry agent authority; sharing an editor’s key does not give someone viewer-only access.
In Model-driven Restricted mode, agents can propose data updates but cannot change schema. Human schema administration uses an authenticated owner or editor session in the console. A key created by an owner still carries agent authority.
If a link does not work
Check the invited, verified email and ask the owner to check expiry, cancellation, or failed delivery. Members and Connections are inside each database; they are not global sharing pages.