The step goes to whoever starts the run

Assign a step to the Initiator role instead of a named person. When someone starts a run, Manifestly hands those steps straight to them — no per-run reassigning, no guessing who’s responsible.

Start free trial. * No credit card required.

Run: Employee IT Request In progress
Submit your equipment request Initiator
resolves to the person who started this run
Submit your equipment request DRDana Ruiz
Dana started the run, so Dana owns the step — automatically.

Stop reassigning the same step on every run

When many people run the same workflow — a request, an onboarding, a report — the starter’s own steps have to be pointed back at them every single time. The Initiator role does that for you, so the workflow is set up once and every run assigns itself.

Without the Initiator role
  • Pick the right person by hand on every run
  • Steps land on the wrong owner when the starter changes
  • A shared template can’t hard-code one name
With the Initiator role
  • Assign the step once, in the workflow
  • Every run routes it to whoever started it
  • One template works for the whole team

Set it once, and every run assigns itself

1

Assign the step to the Initiator

In the workflow editor, open a step’s assignment and choose Assign to run initiator instead of picking a named person.

2

Someone starts a run

Anyone launches a run from that workflow — from the app, a shared link, a schedule, or an automation.

3

The starter gets the step

Manifestly resolves the Initiator role to the person who started the run and assigns their steps to them — automatically.

One workflow, the right owner on every run

The Initiator role is a placeholder in your workflow. Nothing is hard-coded to a single person, so the same template fits everyone. Each time a run starts, that placeholder resolves to the individual who kicked it off — and their steps show their name and avatar just like any other assignment.

  • Mix it freely with people and regular roles in the same workflow.
  • Every run gets a fresh, correct owner — no stale name left behind.
  • Notifications and reminders reach the actual starter, not a placeholder.
Workflow: Employee IT RequestTemplate
Submit your equipment request Initiator
each run resolves the placeholder to its starter
Run 1Submit your equipment request DRDana Ruiz
Run 2Submit your equipment request PSPriya Shah
Run 3Submit your equipment request AKAlex Kim

One click when you build the step

Assigning to the Initiator is part of the normal step-assignment flow. Open a step, and alongside choosing a person or a role you’ll see Assign to run initiator. Pick it and you’re done — the step now follows whoever runs the workflow.

  • No new object to create — the Initiator is ready to use.
  • Use it on one step or on many across the same workflow.
  • Switch a step back to a person or role any time.
Assign · Submit your equipment request
Person
Choose a person…
or
Role
Choose a role…
Or route to the starter
Initiator selected

A built-in role, managed for you

The Initiator is a reserved system role — not something you set up or keep in sync. It has no fixed member list because it never points to a fixed person; it always resolves at run time to whoever started the run. That’s why its name is locked and it can’t be repurposed.

  • Reserved name — you can’t create another role called “Initiator.”
  • No member list to maintain — the run’s starter is the member.
  • Exposed on the v2 API with an initiator flag so integrations can spot it.
Role settings
Initiator
Resolves to the user who creates the run.
People — set automatically per run
# List the roles in a department
GET /api/v2/roles
{
  "name":      "Initiator",
  "initiator": true,
  "members":   []
}

Made for workflows anyone can start

Employee requests

IT tickets, expense reports, PTO, access requests — anything a person raises for themselves.

The requester starts the run → the “provide details” steps are theirs from the first click.

Self-guided onboarding

A new hire or new customer works through their own run of tasks.

They start their run → every “do this yourself” step lands on them, while approvals route to a role.

Shared team procedures

One SOP that dozens of teammates run, where the starter owns the follow-through.

Whoever launches the run → picks up the hands-on steps without anyone assigning them.

The Initiator role, answered

The person who starts the run. When you launch a run interactively, that’s you — the Initiator role even pre-fills with your name on the start form. Steps assigned to the Initiator go to that same person.

“Assign to me” pins a step to one specific person right now. The Initiator role stays dynamic: it’s set on the workflow once and resolves to a different starter on each run, so the same template works for everyone.

No. “Initiator” is a reserved system role. Its name is locked, it has no fixed member list, and it’s managed for you so it always resolves to the run’s starter. You simply assign steps to it — there’s nothing to set up.

Yes. A single workflow can send some steps to the Initiator, others to specific people, and others to regular roles. Use it on as many or as few steps as you like.

Yes. Roles returned by the v2 API include an initiator flag, so an integration can tell the Initiator role apart from the regular roles you’ve created.

Once the run starts, the Initiator resolves to a real person, so assignment notices, due-date reminders, and activity all reach that individual exactly as they would for any other assignee.

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

Automatically Assign Steps to the Person Who Starts the Run

With Manifestly, your team will Never Miss a Thing.