Roles and permissions

For: an Owner or Admin deciding who gets what. Takes about 5 minutes.

What this means

This article is about Stacktic roles. A role is the access level someone has inside Stacktic itself. There are three: Owner, Admin, and User.

A Stacktic role is different from a tool's owner or admin, like whoever manages your Figma account. If you're trying to find out who's responsible for a specific tool, see Primary owners vs. operational contacts.

The three roles

Every person you invite gets one of three roles. You pick it when you send the invite. You can change it any time from /settings/members.

• Owner. Owners can do everything, including managing settings.
  • "Settings" means the whole /settings area: Members, Teams, Departments, Integrations, Signals, Radar, Switchboard, Reminders, the Tool Registry, Tool fields, and General. General includes canceling the account.
  • Only an Owner can add or manage another Owner.
• Admin. Admins can do everything except manage settings.
  • That covers the day-to-day running of the stack: tools, access, signals, people, offboarding, and Switchboard.
  • An Admin can't open Settings, invite or remove members, or cancel the account.
• User. Users can access tools, people and signals.
  • A User can manage every tool. They can add, edit, archive, and merge tools. They can work in every tab on a tool's page, including Docs, Workflow, and Integration. They can manage access, handle signals, and answer access requests.
  • A User can read people's profiles but can't edit them.
  • A User can't run an offboarding, use Switchboard, or open Settings, unless a team gives them more (see below).

When you invite someone, Admin is the default. Invite someone as a User when their job is managing tools. If they also need offboarding or Switchboard, add them to a team. It's easier to grant a permission later than to take one back.

Giving a User more with a team

A team is how a User gets offboarding or Switchboard without becoming an Admin.

Go to Settings → Teams. Add a team, or click an existing team in the list to open its panel. Then add the people who need it.

Anyone can be on a team: a User, an Admin, or an Owner. But an Owner or Admin already has everything a team could grant, so teams are really for Users.

Then check the permissions the team should hold:

• Offboarding: start, schedule, and cancel offboarding runs.
• Switchboard: open the Switchboard review dashboards.

Nothing changes until you click Save. Then everyone on the team can do it, starting the next time they load a page. If you close the panel without saving, Stacktic asks before throwing your changes away.

Remove someone from the team, or archive the team, and they lose it just as fast. Archiving takes effect straight away, without a Save.

There's no Tools permission to check. Every User already manages tools.

Each member has their own profile page (/settings/members/{their name}). It lists every permission they hold and why: their role, or which team gives it to them. So you never have to guess.

Owning a tool

Every User can manage every tool. So being a tool's primary owner doesn't unlock anything extra in Stacktic.

Ownership is about responsibility. The primary owner is who Stacktic asks about the tool. A signal that fires on a tool you own is assigned to you. If someone is covering for you as your delegate, they get those signals while the delegation is open.

What a User sees day to day

With no team permissions at all, a User can:

• See Home, browse Tools and People, and work Signals. That means snooze, dismiss, assign, and use the fix buttons on a signal's page.
• Open Radar, if your organization has it turned on.
• See their own to-do list at My Tasks.
• Add a tool. The form starts with you as the primary owner, and you can pick someone else.
• Manage any tool:
  • edit its details, notes, custom fields, owners, departments, and accounts;
  • upload and edit docs;
  • manage its Access tab;
  • set up its access workflow;
  • connect its integration;
  • verify, archive, merge, or delete it.
• Open Requests to see every access and new-tool request. From there they can answer or cancel a request, retry a failed step, and request access on someone's behalf. Nobody can approve their own request.
• Open a person's profile and read everything on it: Overview, Access, Activity, and Signals. They can also manage that person's access from their Access tab. Editing the person's details takes an Admin.

A User won't see Offboarding, Reminders, Activity, Switchboard, or Settings in the sidebar at all. The exception is a team that adds the Offboarding or Switchboard permission. Those items show up in the sidebar the moment the permission does.

Reminders, Activity, and Settings stay with Owners and Admins. Settings stays with Owners only.

Security notes

• A permission takes effect, or goes away, on the person's very next page load. There's no waiting, and they don't need to sign out.
• Archiving a team removes every permission it was granting, for everyone on it, immediately.
• You can bring back a removed member with Reactivate… on the Inactive tab of /settings/members. That doesn't bring back what they had. You pick their role again, and they come back on no teams. Add them to a team yourself if they should have its permissions.
• A permission you hold through a team works the same way in Slack as it does on the web. For example, someone with the Offboarding permission through a team can start or schedule an offboarding from either place.

Troubleshooting

See also

• Setting up your organization
• Primary owners vs. operational contacts