Skip to main content

Start a Process (Self-Serve)

Some processes are meant to be started by anyone — like requesting onboarding for a new hire. When an Admin or a manager opens a process to the team, you can launch it yourself with just a title. You don't need to know the steps, and you don't have to pick who does what: that was decided when the process was designed.

This page is for the person who starts a process. If you design or launch processes yourself, see Running Blueprints.

Where to Find It​

Go to Tasks → Start a Process.

info

This tab is available to everyone who can open Tasks — you don't need to be an Admin or a manager, and you don't need access to the Blueprints section.

Starting a process is open to Members, Executives and Admins by default. If your role doesn't allow it, the cards are shown without the title field and the Start button.

What You See​

At the top of the tab there's a Start a process heading and a scope toggle:

ScopeWhat it lists
TenantProcesses that were opened to your whole organization
DepartmentProcesses that were opened to a specific department

Switching the toggle only changes what's listed — it never changes what you're allowed to start. Your last choice is remembered, so the tab opens on the same scope next time.

Below the toggle, each available process appears as its own card:

On the cardWhat it means
NameThe name of the process
Department badgeShown when the process belongs to a department
DescriptionA short explanation, if the person who opened it added one
This process will route toA preview of who will receive the work (only for processes that assign people by role)
Title fieldThe text that identifies this particular run
StartBegins the process (with a confirmation step)

Starting a Process​

  1. Choose Tenant or Department and find the process you need.
  2. Type a title for your run in the title field — for example "ABC Company".
    • What you type is added to the end of the process's default title, so the finished title reads "Company Onboarding - ABC Company". The field shows that default title as a hint before you type. If no default title was set, the name of the process is used instead.
    • You can type up to 120 characters.
  3. Click Start.
  4. Read the confirmation message, then click Confirm — or Cancel if you've changed your mind.

If you click Start with an empty title, you'll be asked to enter a title first. Once the process begins, you'll see a short Process started confirmation.

caution

After you click Start, this warning appears on the card: "You are about to start this process. It cannot be undone and tasks will be assigned to the relevant people. Continue?" Starting a process cannot be undone from this tab — the tasks are created and assigned straight away.

Who the Tasks Go To​

Some processes decide their assignees at the moment you start them. For those, the card shows a This process will route to box with the real names, so you know where the work will land before you commit:

Role shownWho it resolves to
YouThe person starting the process — that's you
Department managerThe manager of your department
GMThe General Manager chosen for that step

You is always listed; Department manager and GM appear only when the process uses them. If a role can't be resolved, you'll see a hint in its place instead of a name:

HintWhat to do
No department set for youAsk an admin to place you in a department
No manager set for your departmentAsk an admin to assign a manager to your department
Not setNo General Manager is set — ask an admin to sort it out

If the preview can't be loaded at all, you'll see "Couldn’t load who this process routes to."

tip

Check this preview before you start. Fixing a missing manager or department first is much easier than dealing with a process that landed with the wrong person.

note

Processes that don't use role-based routing show no preview — their people were already chosen by the admin or manager who opened the process to the team.

What Happens After You Start​

  • A new process run is created, with a title that ends in what you typed.
  • The tasks for the first step are created and assigned to the right people.
  • Those people are notified, and the work appears in their tasks.
  • As each step is completed, the next one starts automatically, all the way to the end of the process.

You'll see any tasks that come to you in My Tasks, exactly like any other task — with the same description, deadline, attachments and completion conditions the process designer set up. See Completion Conditions for how to close them out.

Your Recent Starts​

Under the process list, Your recent starts keeps a read-only log of the runs you started, showing:

  • The run title
  • The process it came from
  • The date and time it was started

Use it to confirm that a start went through and to spot an accidental double start. The section only appears once you've started at least one process.

When Nothing Is Listed​

If no processes are available in the scope you're looking at, you'll see an empty state instead of cards:

ScopeMessage
Tenant"No processes are available to start yet." — an Admin opens a process to your team from the blueprint editor
Department"No department processes are available to start yet." — these are processes opened to your department only

Check the other scope first. If it's empty too, ask an Admin or your department manager to open the process you need to the team. A process is listed only while its blueprint is published.

For Admins & Managers​

You make a process self-serve from the launch panel, on the New Start tab, under Open to Team (Self-Serve):

  1. Set a Default process title — it becomes the first part of every run's title, and people see it as a hint in the title field.
  2. Choose Visible to: Everyone (whole tenant) or a single department (Only {department}).
  3. Tick Let members/managers start this from “Start a Process”.
  4. Click Save for self-serve.

All task steps must have an assignee before you can save it for self-serve — otherwise you'll see the hint "Assign all task steps before opening to the team." The people you picked are saved with it and receive the tasks on every self-serve start.

tip

Use dynamic assignees on the steps you want routed automatically — Whoever starts the process, Starter's department manager, or General Manager. Those are exactly the roles that show up in the starter's This process will route to preview. See Creating Blueprints.

Full details are on Running Blueprints.

Tips​

  • Give a clear, specific title — it's how you and everyone else will recognise this run later.
  • Check the routing preview before starting, so the work lands with the right people.
  • Start once. There's no undo here — check Your recent starts before starting the same process again.
  • Track progress through the tasks you receive, or — if you have access to the Blueprints section — on the Processes tab.