Rencore
Approval Workflows
Route sensitive remediation through multi-step approval chains before execution. Configure approvers, delegation, escalation, and full audit trails per workflow.
Approval Workflows route governance actions through human review before execution. Approvers can be roles, individuals, or chains; delegation handles vacations; escalation handles non-responders; every decision is logged. Sensitive actions, deleting users, revoking access, modifying permissions at scale, require sign-off; routine cleanups run automatically. Human-in-the-loop where it matters, automation everywhere else.
When approvals belong in a workflow
Automatic remediation is the default for low-stakes governance actions, removing an anonymous sharing link, archiving a stale site, revoking an unused API key. For higher-stakes actions an approval gate is the right pattern: deleting a user, downgrading a guest’s permissions, releasing a license, modifying tenant-wide configuration.
The pattern is the same as production change management. Routine changes run automatically; significant changes require sign-off; everything is audited.
How approvals route
Each approval step is configured with approver criteria, a specific user, an Entra ID group, a role, or a relation (the resource owner, the site collection administrator, the manager of the affected user). At runtime the platform resolves the criteria and routes the approval to the resolved approver. Delegation and escalation rules handle the exceptions.
Beyond remediation
Approvals appear in workflows beyond cleanup. Provisioning new workspaces requires owner approval; onboarding flows route through manager approval; access reviews use attestation as a form of approval. The engine is the same; the trigger differs.
Frequently asked questions
Can I build custom automations in Rencore?
What is Rencore governance?
How do Rencore policies work?
Trusted by
