Workspaces & governance
Understand workspace ownership, key restrictions and the signed-in settings behind governance controls.
Organization and workspaces
An organization owns workspaces. A workspace isolates inference keys, usage and operational settings. Choose the correct environment and workspace before creating a key or uploading a file. A model in the public catalogue can still be blocked by your key or workspace policy.
Roles and credentials
Owners control billing and membership. Admins manage keys and other settings; members read and run. Inference keys call model APIs. Management keys have explicit scopes and workspace access and cannot replace a signed-in session for sensitive settings. See Management API.
Presets and BYOK
Key model access restricts the models available to a key. A preset supplies defaults where the request does not specify them; it is not a separate provider. BYOK stores a customer-supplied provider credential through the signed-in settings flow. Route availability, price and fallback behavior remain specific to that provider and policy. Configure these surfaces in the console; management keys cannot modify them.
Limits, account security and data
Set key and workspace controls as described in Rate limits & caps. Keep model keys on your server and use the available account-security settings. Read Privacy for the distinction between request metadata, queued async content, retained answers and uploaded media.