The rule that keeps access correct runs itself.

The rule is a workflow. It runs on the directory change itself, and every step it skips says why.

Govern, policies and workflows

A leaver from trigger event through to execution, step by step
01Where it goes wrong

The rule that keeps access correct lives in someone’s head, or in a runbook nobody opens.

02How it works

How it works

A policy binds a trigger and a population to one reusable workflow, and one recipe then serves many rules

Workflows are versioned and each execution keeps an immutable snapshot of the version that ran

Outbound API and webhook steps pass an SSRF guard before they are allowed to call anything

03With Nuvio

Ask the specialist that owns this work.

Ask in your own words. The Policy and Workflow Agent runs as you, and any action it can take ships off until an admin turns it on.

How Nuvio is governed

Policy and Workflow Agent

Drafts and tunes the automation rules that keep access correct between reviews.

  1. You asked: Alert me when a contractor gets an admin role
  2. Nuvio answered: Contractors picked up admin roles twice this quarter. Here is the rule that would have caught both. Turn it on?

    Ready for you

    The rule is drafted for you to enable

    Govern, workflows

04Where it fits

The jobs it is bought for.

Day one to last dayA leaver stops being reachable on the day they leave
No standing accessAdmin that arrives for four hours and leaves on its own
05On your own tenant

See it on your own tenant.

Book a demo

Connect your directory and see your first findings the same day.

The graph behind it