Workspace access
Resource access is checked against an explicit workspace and its membership. Owner, member and viewer roles have different permissions; platform administration alone does not grant access to workspace resources.
This overview describes implemented workspace boundaries and data-use controls. Deployment and contractual assurances require their own dated evidence and owner-approved terms.
Resource access is checked against an explicit workspace and its membership. Owner, member and viewer roles have different permissions; platform administration alone does not grant access to workspace resources.
Cross-workspace resource access uses an active directed grant that covers the resource and the action. A sharing contract grants specified access while ownership stays with the originating workspace.
Delegated actions carry the initiating member’s verified workspace identity. Service credentials establish the connection between services; the operation still requires the appropriate workspace authority.
Workspace owners can choose whether eligible runs may be exported for platform learning and which purposes are allowed. Export eligibility checks the recorded consent and the current workspace policy.
Access to a workspace’s own shared knowledge, relayed third-party sources and shared ingestion costs are separate choices. Optional contract terms have their own owner-controlled consent and disclosure.
Privacy and security settings expose account controls and the owner’s platform-learning choices. Workspace owners review sharing contracts and their optional terms in the members settings.