Assign steps to a role, not a name

Build a workflow once and give each step to a role — Approver, Reviewer, On-call Nurse. Then, every time you start a run, pick the person who fills each role for that run. The same process, the right people, every time.

Start your free trial — no credit card required.

Client Onboarding Workflow
Collect signed agreement AMAccount Manager
Review for compliance RVReviewer
Approve & activate account APApprover
Send welcome kit Dana Ruiz

Steps assigned to roles — and to people — side by side.

Stop rewiring assignments every single run

When steps are pinned to named people, every vacation, hand-off, or new hire means editing the workflow. Assign to roles instead, and the workflow stays put — you just choose who plays each part when the run kicks off.

Assigning to named people
  • Every workflow hard-codes one person per step
  • Someone leaves — hunt down every step they owned
  • Copies of the same workflow, one per teammate
Assigning to roles
  • One workflow, roles that never need re-editing
  • Update who's in a role once — every future run follows
  • Pick the person per run, right when you start it

From role to running work in three steps

1

Create a role

Name a role — Approver, Reviewer, Shift Lead — and attach the people who can fill it. Leave it open to anyone, or narrow it to a specific short list.

2

Assign steps to it

In the workflow editor, assign any step to that role instead of a person. Different steps can go to different roles — and you can still assign some steps to a specific person.

3

Resolve it per run

When you start a run, Manifestly asks who fills each role this time. Their steps land in that person's assignments, and everyone gets notified as usual.

Give a step to a role while you build

Every step can be assigned to a person or a role. Picking a role means the step belongs to whoever fills that role in each run — no name baked in. Mix and match freely: a fixed owner for one step, a role for the next.

  • Assign to a role, a specific person, or the run's initiator on any step.
  • Reuse the same role across many workflows — roles live at the department level.
  • See at a glance which workflows a role is used in before you change it.
Assign — “Review for compliance”
Person
None
Role
RVReviewer
Or assign the step to the run initiator — whoever starts the run.

Choose who fills each role, run by run

Start a run and Manifestly gathers every role your workflow uses and asks you to resolve each one to a specific person. Same workflow on Monday and Friday — different people, no edits. Once chosen, each person's steps show up in their assignments and they're notified.

  • Roles resolve at every entry point — a run you start now, a scheduled run, or a shared run link.
  • Add someone new to the role right from the run form when the person you need isn't on the list yet.
  • Roles that map to one obvious person fill themselves in, so there's nothing to pick.
Start run — Resolve roles to a person
Account Manager
DRDana Ruiz
Reviewer
PSPriya Shah
Approver
AKAlex Kim
Three roles resolved — steps route to the people you picked.

How a role decides who's picked

A role's people list shapes what you're asked when a run starts.

Nobody attached

The role is open — pick anyone on the account to fill it for this run.

One person attached

That person fills the role automatically — nothing to choose.

A short list attached

Choose from just the people who belong to that role — no scrolling the whole directory.

The Initiator role

Resolves to whoever starts the run — perfect for “the person kicking this off.”

The same roles, wherever runs begin

However a run starts, Manifestly resolves its roles the same way — so a workflow behaves consistently no matter who launches it or how.

Run you start Scheduled run Shared run link
  • Roles are managed at the department level and reused across every workflow there.
  • The moment a role resolves to a person, their steps and notifications behave like any direct assignment.
  • List your roles over the v2 API and pass them when you start a run so each one resolves to the right person.
# List the roles available to your token
GET /api/v2/roles
 { "roles": [
      { "id": 41, "name": "Approver", "department_id": 8 },
      { "id": 42, "name": "Reviewer", "department_id": 8 }
    ] }

# Start a run and resolve each role to a person
POST /api/v2/runs
{
  "run": {
    "workflow_id": 305,
    "roles_to_users": [
      { "role_id": 41, "email": "alex@acme.co" },
      { "role_id": 42, "email": "priya@acme.co" }
    ]
  }
}

The /roles endpoint returns the roles in the departments your token administers, each with its members. Role assignments also travel with a workflow's JSON export and import.

A built-in role for whoever starts the run

Every account has a reserved Initiator role. Assign a step to it and that step always lands on the person who started the run — ideal for “confirm the details you entered” or “close this out” steps. No list to maintain; it just follows the run's starter.

  • Resolves automatically — the initiator is filled in before the run even begins.
  • Works alongside your own named roles on the same workflow.
Initiator
Reserved role · resolves to the run's starter
Auto
Confirm the request details Initiator
Started by Dana Ruiz → this step is hers, instantly.

Where role-based assignments shine

Approvals & reviews

Send review and sign-off steps to an Approver or Reviewer role.

On this run the approver is Alex; next week it's whoever's covering — the workflow never changes.

Shift & on-call work

Assign steps to Shift Lead or On-call roles that different people fill each day.

Start the shift run and drop today's lead into the role — their steps route to them.

Onboarding & hand-offs

One onboarding workflow with IT, HR, and Manager roles reused for every new hire.

Pick this hire's manager at run start; IT and HR steps land with the right teams automatically.

Role-based assignments, answered

Assigning a step to a person pins it to that named user in every run. Assigning it to a role leaves the actual owner open — you choose who fills the role each time you start a run, so the same workflow can serve different people without any edits.

Only when there's a real choice to make. A role with exactly one person attached fills in automatically. A role with a short list lets you pick from just those people, and an open role lets you choose anyone on the account. The Initiator role always resolves to whoever starts the run.

Yes. Roles and direct assignments live side by side. Give one step to a fixed owner and the next to a role — whatever fits the process. Every step can go to a person, a role, or the run's initiator.

It's a reserved, built-in role that always resolves to the person who started the run. Assign a step to Initiator when it should belong to whoever kicks the run off — there's no people list to maintain and nothing to pick at run start.

Roles are resolved to specific people at the moment a run starts, so a run in progress keeps the people you assigned to it. Updating a role's people list changes who's offered the next time you start a run from a workflow that uses it.

Yes. The v2 API's /roles endpoint lists the roles in the departments your token administers, each with its members. When you start a run over the API you can pass a roles_to_users list that maps each role to a person by email, and a workflow's role assignments travel with its JSON export and import.

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

Assign Workflow Steps to Roles, Not Names

With Manifestly, your team will Never Miss a Thing.