We use cookies to improve your experience and for marketing. Read our cookie policy & privacy policy.

Getting started · Console & account

User management: roles & permissions

StackUp TeamUpdated July 20265 min read

The Roles & Permissions page is where you manage user access and product capabilities for your team and your clients: invite users, set their roles, control which products they can see, and deactivate accounts that should no longer have access.

⚠
Admin required. Invites and role changes require the Admin role. If you cannot see these controls, ask an administrator of your workspace.

The Roles & Permissions page

Open Settings › Team › Manage Team. At the top, summary cards show total users, active users, standard users, and administrators, so you always know the shape of your team at a glance. Below, a search box and a role filter help you find users quickly in larger workspaces.

Roles

RoleWhat it can do
AdminFull workspace management: invite users, change roles, grant product access, and deactivate accounts, in addition to using the products.
StandardUses the products they have been granted access to, without administrative controls.

Change a user's role directly from the role dropdown on their row. The change applies immediately.

The Users table

Each row is one user and shows their name, email, role, company (the account or client they belong to), product access chips, status, and last login. From the row you can:

  • Change the role via the dropdown.
  • Manage sections — control which areas of the product the user can access.
  • Deactivate — immediately revoke access without deleting the user's history.
💡
Tip: the last login column is the quickest audit tool you have. Review it periodically and deactivate accounts that have gone quiet, especially client-side users.

Inviting users

1

Click Invite User and enter the invitee's email, role, and the product access they should start with.

2

Track the invite. Pending invites appear in the Invites table with their status (for example accepted), delivery state, granted product access, and expiry date.

3

Resend or revoke. Expired or unanswered invites can be resent from the row's actions, and pending invites can be deleted to revoke them before acceptance.

Product access

Access is granted per product, shown as chips on each user's row, for example Pipeline Analysis and Pulse. This is how you give a client visibility into their own reporting without exposing the rest of the platform: create their user under their company, grant only the products they need, and scope sections accordingly.


Was this article helpful?