Docs / Capability guide
API keys, users, SSO and audit
Manage integration credentials, sign-in, and audit records.
All capabilities · Related guide · Agent prompt for this capability
When to use this example
When a team member leaves or an integration changes owners, review who can still access the workspace and which keys are in use. Reading users, key metadata and recent audit events together gives the administrator a basis for that review.
What the example gives you
The workspace inspector exports users, API-key metadata and audit records without returning key secrets. It does not revoke access or change sign-in policy; apply any approved changes through the relevant API operations.
Before you start
Tenant administrator access; identity-provider metadata for SSO and a separate emergency sign-in method.
Run the example
Extract the archive and follow README.md for setup, commands, and expected results. Start with workspace_inspect.py. Local tests use sample data.
Python tools accept --help. To connect to your workspace, supply the deployment URLs, credentials and resource IDs required by the tool.
Connect it to your application
Inspect users and API keys by role and scope. Create a dedicated key for each integration and store it in the environment or a secret store. Keep operator credentials out of customer applications.
Configure OIDC or SAML with the documented callback and metadata; test sign-in before enforcing the new policy. Rotate keys and confirm the old credential stops working after its intended overlap.
Read audit records for each administrative mutation. Use the privacy-request workflow for access/erasure requests; do not implement a custom cross-tenant database scan.
Check the result
Missing credentials fail, out-of-scope resource IDs cannot be read, and rotations leave a working authorized path. A successful login alone does not verify resource-level isolation.