Skip to main content
Users get access to one workspace at a time. A user’s role and user access then determine what they can see and change.

Manage users

Organization administrators open Settings > Workspace > Users to invite users, change roles, revoke invitations, or remove a user from the workspace. Workspace administrators can review the users there and set each user’s user access. Removing a user blocks their workspace access immediately. Choose an active replacement user during removal to transfer owned records and follow-up work. Without a replacement, ownership can be removed. Unfinished summaries pass to an eligible reviewer; approved history keeps its original attribution. Removal also revokes the person’s workspace access keys and chat identity links. It does not delete their account or remove access to other workspaces. You cannot remove yourself or the last active workspace administrator.

Administrator boundaries

  • An organization administrator manages users (invitations, roles, and removals), organization-wide settings, billing, user access templates, branding, organization-wide sources, and the organization’s Slack and Teams apps.
  • A workspace administrator manages the active workspace: its name and rules, context, workspace sources, CRM and accounting integrations, workflows, lead forms, and task plans.
  • A user works with the features and records their access allows.
One person can have different access in different workspaces.

User access

Organization administrators open Settings > Organization > User access. The page holds templates: saved choices of what a user can see and do. Create a template with New template. Each template sums up its access as Can see: everything or Can see everything except: followed by what it hides. Turn on Default for new users for the template new users should get when they are invited. One template can be the default, and you can still choose another template in the invitation or change the access per user later. Test access with a normal user account when you change a template. Administrator access can hide gaps in the intended user setup. Areas checkboxes hide whole product areas. The meeting control is Meetings & briefings. It hides briefings, meetings, and summaries together. Contacts hides companies, people, their detail pages, import, and create actions. Calendar integration hides prompts to connect a calendar and the Google or Outlook setup. Meetings can still be added with the invite address. Actions checkboxes hide specific edits: Add and edit notes, Add tags, Change owner, Manage company relationships, and Delete and archive. Existing notes, tags, owners, and relationships stay visible. Add tags only hides the tag picker. Work follows the organization’s plan and each user’s seat. A user template does not turn Work on or off. Older templates can still show a Work (legacy) group. That group no longer controls Work. User access does not activate a paid feature on its own. Work, meeting, or other plan requirements must also be satisfied. Access checks apply to navigation, records, imports, the Assistant, MCP, and the public API.