Team Management

Workspace roles

Viewers can view scan results but cannot initiate scans. Members can run scans and view results. Admins manage members, settings, integrations, and scans within the permissions enforced by each endpoint. Owners have additional workspace-level permissions.

Available actions are enforced on the server, not only by hiding controls. Ownership transfer is not a standard member-role change. Contact your administrator rather than assuming any role selector can transfer ownership.

• Team management

Invite and verify access

Verify the workspace displayed on Team before editing memberships. Selected-workspace support is not yet uniform across every administrative endpoint; do not assume the sidebar alone determines the target of a team mutation.

Use Invite Member, enter the member's email, and choose a permitted role. An existing account can sign in with its configured method. A new account may need the invitation or password-reset flow to establish a password. Email delivery requires configured mail infrastructure; the UI reports when no invitation was sent.

Never share credentials to work around a failed invitation. Ask an administrator to verify the membership and delivery configuration.

• Team details
• Password reset

Switch workspaces deliberately

Use the sidebar selector and confirm leaving the current context. Scan and chat client state is cleared and other open tabs are notified. An invalid selection should be resolved by choosing an accessible workspace, not by retrying actions in an unknown context.

For invitations, SSO, billing, and other administrative changes, verify the workspace named on the destination screen. Report inconsistent context before making changes.

• Settings

Base team and scan limits

These configured defaults update with the application's plan configuration. Account role overrides, enabled features, and current server responses govern actual access.