03 · Govern · The work around access

Workflows

Automate the tasks around a joiner or a request, without a side door to access.

A workflow handles the work around access: a laptop ready three days before someone starts, a ServiceNow ticket when a conflict is found. It starts on an event, a date, a schedule or a click. A workflow never writes access to a system. When it needs access, it files a request and the normal approval chain decides.

What changes

What you get

01

Starts on an event, a date, a schedule or a click

02

Tasks in the Inbox, with reminders and escalation

03

Access only through a request and its approvals

04

A test run shows every step before anything happens

Screenshot of the product · Fictional demo data
How it works

It works in three steps

Each step records its reason, and the next step uses it.

  1. Start

    Choose when it starts, and see how many people it would run for before you save.

  2. Build

    Combine forms, tasks, conditions, waits, parallel paths and a ServiceNow ticket.

  3. Run

    Every run records the version it ran, and a failed step stops the run with its reason.

What we stand behind

Access that a workflow asks for goes through the same approval chain as any other request, and shows the workflow as its origin.

Included

Included in every price

There is no module to buy for this. The price depends only on how many identities you govern.

How the price works See it in the product tour

Workflows

Automate the tasks around a joiner or a request, without a side door to access.