Users and permissions
Set up people, application service accounts, and AI clients with permissions on the models they need.
On this page
Choose an identity for the client
- Member
- Use a person’s own account for console work. Console and MCP access can be managed separately.
- Service account
- Give each application its own token and model role. Use the username
svc/<name>for HTTP, Bolt, and Gremlin clients. - Personal MCP token
- Use the owner’s model permissions and tenant scope for authorized AI work.
Grant a role on the intended model
- Sign in as an administrator and open Access Control. Create a member or service account.
- Create a role, add the target model, and select actions. Add the identity to that role.
- Verify the account by running a small query on the intended model and checking access to a model outside its role.
- Query and export
- Query covers schema inspection, reads, and graph exploration. Full Arrow export requires both query and export on the same model.
- Modeling and publication
- Modelers can edit and validate drafts within approved sources. Publication controls activating, rolling back, or taking a model offline. Administrators manage connectors and physical table access.
- Audit
- Review configuration and revision history with an audit role.
Constrain rows by tenant
Set a model role’s logical partition predicate, for example tenant_id = 1. Map tenant_id into all relevant node and edge business keys and both relationship endpoints, with compatible types. GraphLake enforces the scope on supported client queries, exploration, and exports.
Conflicting tenant values on the same model are rejected. To segregate sensitive columns, use database views or a separate model projection. Shared CSR generations are available for unscoped queries.
Rotate credentials and verify
Rotate an application’s token in its service-account settings. Put the new token in the client’s secret store, reconnect, and verify the old token no longer grants access. Role changes can invalidate existing sessions, connections, and download tickets.
See the access control reference for legacy service-account files, enterprise login, and audit handling.