Give everyone exactly the access they need

Manifestly's permission levels let you decide who can build workflows, who can start and assign runs, and who simply works on the tasks handed to them — so the right people have control and everyone else stays focused.

Start a free trial — no credit card required.

Team & permissions Settings
DR Dana Ruizdana@acme.co Admin
PS Priya Shahpriya@acme.co User
AK Alex Kimalex@acme.co Member
JL Jordan Leejordan@acme.co Limited

When everyone can edit everything, nothing stays reliable

Give the whole team the keys and someone will eventually rewrite the workflow everyone depends on, or wander into runs that aren't theirs. Roles put a clear line between the people who maintain your processes and the people who run them.

Without roles
  • Anyone can rewrite a live workflow
  • People see runs that aren't theirs
  • No clear owner for your processes
With roles
  • Admins own and edit the workflows
  • Everyone sees only what they should
  • Participants just work their tasks

Set access in three steps

1

Invite your people

Add teammates by email. New invitees join as Users by default — ready to run your workflows without being able to change them.

2

Pick each person's role

Choose Admin, User, Member, or Limited for each teammate. Change it any time as responsibilities shift — the update takes effect immediately.

3

Everyone sees the right thing

Manifestly enforces the role everywhere — in the app and over the API. People only see and touch what their role allows, with no extra configuration.

Four roles, from full control to focused participation

Every teammate has one role. It decides what they can build, what they can start, and what they can see — a clean ladder from complete ownership down to a single set of assigned tasks.

  • AdminFull access. Creates and edits workflows, manages users and settings, and runs anything.
  • UserStarts and assigns runs and works across the department — but can't edit the workflows themselves.
  • MemberWorks only on the runs and tasks they're assigned. No monthly limits.
  • LimitedSame focused access as a Member, capped to a set number of runs per month — ideal for occasional or external participants.
What each role can do
Capability AdminUserMemberLimited
Work on tasks assigned to them
Start and assign runs
See every workflow and run in the department
Create and edit workflows
Manage users, roles, and account settings
Members and Limited users differ only in the monthly run cap — both stay scoped to their assignments.

Participants see only what's theirs

Members and Limited users don't browse your whole account. They see the runs they've been invited to and the tasks assigned to them — nothing else. There's no workflow library to wander through and no other team's runs in view, so external partners and occasional contributors get a clean, focused workspace.

  • No access to workflows or runs they aren't part of.
  • Their view is just the assignments waiting on them.
  • Great for contractors, vendors, and cross-team hand-offs.
Alex's view (Member)Member
My tasks
Review vendor invoiceAccounts Payable · due Fri Assigned
Upload signed W-9Vendor Onboarding · due Mon Assigned
Everything else in the account is hidden — no workflow library, no other runs.

Separate teams under one roof with departments

Larger organizations can split a single account into departments — each with its own workflows, runs, and members. Someone can be an Admin in one department and a Member in another, so access follows the team, not the whole company.

  • Each department keeps its own workflows and runs walled off from the rest.
  • Set a person's role per department — admin here, participant there.
  • A master admin on your top-level account oversees every department.
Acme Corp Master admin: Dana
Operations
PriyaAdmin
AlexMember
Finance
AlexAdmin
JordanUser
Field Ops
PriyaUser
JordanLimited
Alex is an Admin in Finance but only a Member in Operations — roles are set per department.

What an Admin controls

Workflows

Create, edit, and archive the workflows their team relies on.

People & roles

Invite teammates, set each person's role, and remove access when they leave.

Runs

Start, assign, and manage any run in the department, end to end.

Settings

Manage account settings, integrations, and webhooks for their department.

How teams put roles to work

Process owners as Admins

The people who design and maintain your SOPs get full edit rights.

Your ops lead keeps every workflow current; nobody else can change them by accident.

Day-to-day team as Users

Everyone who kicks off and assigns runs, without touching the templates.

Team leads start the daily and onboarding runs and assign the steps to their people.

Contractors as Limited

Outside collaborators who only need the tasks handed to them.

A vendor completes their assigned onboarding steps and sees nothing else in the account.

Permissions, answered

There are four roles. Admins can create and edit anything and manage users and settings. Users can start and assign runs and work across the department but can't edit workflows. Members can only work on the runs and tasks they're assigned. Limited users have the same focused access as Members but are capped to a set number of runs each month.

Both can only work on the runs and tasks they're assigned — they can't create workflows, start runs, or browse the rest of the account. The only difference is that Limited users are capped to a set number of runs per month, while Members have no such cap. Limited is a good fit for occasional or external participants.

Admins manage the people in their department — inviting teammates, setting each person's role, and removing access. Changes take effect right away, in both the app and the API.

Yes. If your account is split into departments, a person's role is set per department — they can be an Admin in one and a Member in another. A master admin on your top-level account has oversight across every department.

No. They see only the runs they've been invited to and the tasks assigned to them. There's no workflow library to browse and no visibility into other teams' runs, which makes these roles well suited to contractors and cross-team hand-offs.

Yes. The same roles govern access through the v2 API. When an action runs on behalf of a user — including AI agents authenticated with OAuth — it's limited to exactly what that user's role allows.

Other Features

Design your process

Workflow Customization

Shape exactly how each workflow behaves — logic, data, timing, and documentation.

Trusted by organizations big and small for their recurring workflows

Compass logo
Sheraton logo
Foxconn logo
Coldwell logo
Plural Sight logo
BDO logo
KW logo
UT Austin logo

Utilize User Permissions to Control Access

With Manifestly, your team will Never Miss a Thing.