Skip to content
New: Mac downloadRead →

Permissions

Manage access across teams and workspaces

Vesso permissions help administrators control page visibility, workspace scope, and team access so users see the areas they need without unnecessary exposure.

Page access

Control which pages and product areas a user or role can access.

Workspace scope

Keep users focused on the workspaces, records, and teams relevant to their role.

Super admin oversight

Give designated administrators broad access for configuration, support, and governance.

Team membership

Use team joins and associations to keep collaboration boundaries accurate.

Set up access intentionally

  1. Start with the user's role and the work they need to perform.
  2. Grant access to the pages and workspaces required for that role.
  3. Use team membership to keep collaboration and ownership clear.
  4. Reserve super admin privileges for trusted operators who need broad oversight.
  5. Review access regularly when teams, responsibilities, or customer boundaries change.

Coordinate permissions with assignment rules

Permissions control what users can access, while assignment rules determine who owns records and follow-up. Use both together so accounts and contacts are visible to the right people and assigned to the right owner.

  • ✓Keep territory, team, and owner fields current.
  • ✓Use bulk assignment when ownership needs to change across many records.
  • ✓Check workspace scope before troubleshooting missing records.
  • ✓Document admin conventions so future access changes stay consistent.

Data Explorer and reporting boundaries

Data Explorer requires effective read permission, then applies ownership and reporting hierarchy to rows. Related data inherits parent or account visibility. Custom Reports and AI-generated queries use the same checks.

Sensitive analytics fields, including meeting transcripts, recording URLs, task comments, and form response data, require workspace administrator access. They are hidden from non-admin schemas and results, and explicit queries for them are rejected. This restriction is specific to analytics access.

Understand Data Explorer permissions →

AI clients and email administration

MCP scopes limit tools in addition to credential, workspace, and actor checks. Members can revoke their own OAuth connections, while administrators can revoke workspace connections. Viewer grants stay read-only. Removing an unsubscribe from the administrative list also requires a workspace administrator.

Admin best practice

Use the least access that still lets someone do their job. Broader access should be deliberate, documented, and reviewed as your organization changes.