Team permissions

Make sure to know who to reach out to if you’re stuck and want, for instance, to delegate a step. You can update team permissions by going to Company > Teams.

The tables on this page describe the built-in roles. On the Enterprise plan, a custom role can grant a specific set of workspace permissions, such as managing colleagues and teams only.

Show or hide app pages

Built-in roles always include the main left-nav sections. A custom role can clear the permissions that open whole sections or pages, so people with that role do not see those items in the navigation. On Company > Roles, each permission group matches a product area. The permission at the top of a group controls whether that section appears in the left nav:

Area on the role page	What it controls in the app
Home	The Home page. Without it, the app opens on the Inbox instead.
Workflows	The Workflows section (running workflows and Start). Work they are already involved in still appears in the Inbox.
Automations Library	The Automations library section.
Workspace	The Company section. Without it, every page under Company is hidden.
Workspace — colleagues permissions	The Colleagues page (colleague names can still appear elsewhere).
Workspace — teams permissions	The Teams page.

Other areas (Portals, Roadmap, Data tables, Data, and pages inside Automations library) have their own show permissions on the same screen. See Custom roles for how the tree selects dependent permissions when you turn a section on or off.

You can use the conversations widget available in each instance to reach out to a lead or team member. See Learn Next Matter as workflow participant

Task	Admin	Workflow lead	Instance lead (the user starting the instance)	Team lead	Colleague (a team member assigned to a step)	Light user
View and start a private instance	✅	✅	✅		✅	✅
Edit and delete a private instance	✅	✅	✅
Skip or delegate a step	✅ (they can delegate steps assigned to a team or a specific person)	✅ (delegation only possible if the lead is an admin, or a team lead and the step is assigned to their team)		✅ (delegation is possible only if the step is assigned to their team)
Delete private instance	✅	✅	✅
View private workflows	✅	✅	✅		✅ (if folder and process visibility allow it)
Stop single instances	✅	✅	✅	✅ ( only if it’s an instance they created)	✅ (only if it’s an instance they created)	✅ (only if it’s an instance they created)
Stop instances from the Workflows > Overview page	✅	(not supported unless you’re an admin workflow lead)	✅
View details of a completed integration step	✅	✅ (when the step fails and they reclaim it from the tech lead)	✅		✅ (when they are also instance leads or tech leads)
Update workflows	✅	✅
Duplicate workflows	✅	*only possible if they own the folder they’re duplicating into
Create instances from private workflows	✅	✅	✅		✅
Change and delete a private workflow	✅	✅
Change workflow leads	✅
Connect and disconnect an integration	✅
Invite colleagues to Next Matter	✅
Create private and public folders and remove them	✅	✅	✅		✅
Move workflows between folders	✅	✅	✅		✅
Move/duplicate workflows to private folders	✅	*only possible for folder owners
Create teams and add and remove team members	✅			✅	✅ (add team members to teams they lead)
Assign or remove the team lead status	✅
View portals	✅					✅
Create/edit portals	✅
Test portals as a light user (Light user view)	✅
Start workflow from a portal	✅	✅ (if added to portal)	✅ (if added to portal)	✅ (if added to portal)	✅ (if added to portal)	✅ (if added to portal)

As an admin, you can set roles for any user, including yourself. Note that if you demote yourself to a colleague, you cannot promote yourself back to the admin level again.

If the workflow lead changes after an instance has been created, the new lead doesn’t have permissions to stop or delete this instance.

Overview

Build

Organize

Run

Report

Manage your account

Manage workspace

Show or hide app pages

​Show or hide app pages

Show or hide app pages