Product guide · English
Bring in your team and tools
Select the correct team workspace, grant collaborators the role they need, and connect tools with credentials scoped to their intended operations.
Steps
- Use the organization switcher to choose or create a team organization. Personal organizations have one member; team invitations are managed from Workspace settings → Members.
- Invite a teammate and choose the role deliberately. Viewers read; Members can perform repository and audit work; Admins manage team configuration. Owners have additional organization-level responsibilities.
- Open Integrations to configure the available source and notification connections. Confirm the target workspace and destination before enabling external delivery; configuring a destination does not prove messages have been delivered.
- For scripts, REST or MCP, have an authorized admin create a key with the required scopes. Store the displayed credential privately and revoke credentials that are no longer needed. Use the API reference for operation-specific scopes.
Read the result
Workspace membership, source-provider authorization and API-key scopes are separate controls. Inviting a colleague does not grant a source provider access to a private repository, and a read-only key cannot start an audit.
Limits and availability
Role and feature availability determine which settings are visible. Integrations may send selected report information to external destinations; use an approved channel and test configuration deliberately. Never put an API key in a repository, screenshot or chat.
This guide describes the implemented workflow. The features available in your workspace depend on account capabilities and configuration; advanced workflows are not all included in Free Quick Scan. Check the available controls and the evidence returned by each run.