Roles and data scopes
Organization roles, membership, and data scopes work together. Seeing a project does not imply permission to modify every resource. Reading documents does not grant membership or workflow administration.
Assign permissions according to each member’s responsibilities. Give members the scope they need to complete work and reserve administration for the relevant owners.
API tokens
Create and manage credentials on the API tokens page. Use read-only access for retrieval and search; grant write access only when the task needs it.
Project allowlists, IP restrictions, expiration, and revocation are checked during authentication. Revoke exposed credentials promptly and review relevant audit records.
Keep real tokens out of public pages, URLs, screenshots, document bodies, and repositories. Agents are constrained by the token’s account and scope.
Identity integrations
The platform supports OIDC, LDAP / AD, two-factor authentication, and SCIM 2.0 configuration. Prepare the addresses, application settings, and permissions required by your identity system.
Use dedicated administration interfaces for identity configuration. Login and 2FA stay in their dedicated flows. Retain a recovery method when changing configuration, then verify sign-in, sign-out, and member deactivation.
Review audit records
Audit records help trace important operations. Check reverse proxy configuration so recorded client IPs reflect actual visitors.
The product interface, built-in assistant, and MCP use the same business permission rules. Reading back data verifies the outcome of a write; audit records identify who acted and when.
Troubleshoot access
- Confirm account status and organization membership.
- Check project membership and roles.
- Check the resource’s own visibility rules.
- For API requests, also check token access level, allowlist, IP, and expiration.
Continue with troubleshooting.