Organizations, teams, and access

An organization is the primary boundary for members, sources, semantic definitions, saved work, credentials, and usage.

Member access

Invite users from Team and assign the least-privileged role that supports their work. Separate administration, source management, building, and viewing where your plan supports it.

Machine access

Use scoped API keys for server integrations. Name each key after its workload and environment, record an owner, and rotate or revoke it when ownership changes.

Review regularly

Audit inactive members, stale keys, source owners, privileged roles, and externally shared resources. Organization boundaries do not replace row-level tenant scoping for customer-facing use cases.

See API keys and authentication and Tenant and row scoping.