Skip to main content
Workspace member screens control who can access a workspace and what each person can administer. Use Console > Workspace Members to manage people and roles inside a workspace.

​
Difference between member and user

​
Workspace roles

Roles are fixed capability sets defined by Acrity. They are not organization-configurable, so a given role grants the same capabilities in every workspace. Assign the least-privileged role that still lets each person do their work.
For the canonical description of each role and how to think about access, see Roles and access.

​
Manage workspace members

Any role can open Console > Workspace Members and view the list of people with access to the workspace. Only a Workspace admin can:
  • invite new members;
  • change a member’s role;
  • remove a person’s access;
  • resend pending invites;
  • copy an invite link when allowed;
  • review expired or pending invites.

​
Invite a person

Only a Workspace admin can invite members.
1

Open members

Go to Console > Workspace Members.
2

Create invite

Choose the action to invite a member and enter the email.
3

Select role

Choose the most restrictive role that still lets the person do their work.
4

Send

Send the invite. If needed, copy or resend the invite from the same screen.

​
Change role

Only a Workspace admin can change a member’s role. To change a person’s role:
  1. Go to Console > Workspace Members.
  2. Find the member.
  3. Open the member actions.
  4. Choose the new role.
  5. Confirm the change.
Review roles after team changes, employee departures, vendor changes, or responsibility changes.

​
View as

Workspace admins can use View as to see the Console as a specific member sees it. This impersonation view helps you troubleshoot what a member can and cannot access without changing their role. View as is a security-relevant, auditable action:
  • It temporarily presents the workspace with the selected member’s role and visibility.
  • Each use is recorded and can be reviewed in Audit Trail.
  • Use it only to diagnose an access problem, then exit back to your own identity.

​
Leave workspace

Any member can leave a workspace they belong to. Leaving is a self action that removes your own access to that workspace; it does not remove other members. Before you leave:
  • confirm that enough Workspace admins remain (keep at least two per workspace);
  • if you are the last Workspace admin, assign the role to someone else first;
  • transfer any billing or integration responsibilities you own.
To leave, go to Console > Workspace Members, open your own member actions, and choose Leave workspace, then confirm.

​
Remove access

Only a Workspace admin can remove another member. Removing a member revokes their access to the workspace. Before removing:
  • transfer billing or integration responsibilities;
  • review API Keys, webhooks, and credentials created by the person;
  • confirm that enough Workspace admins remain;
  • record the change in your team’s internal process.

​
Access best practices

  • Separate technical administration (Workspace admin) from financial management (Billing Manager) when possible.
  • Remove access for people whose role changed.
  • Review pending invites periodically.
  • Avoid sharing accounts between people.
  • Prefer corporate emails administered by the organization.

​
Common issues

​
Audit

Member, invite, role, and View as events can be reviewed in Console > Audit Trail when you need to check administrative history. See Audit Trail.