Documentation
Use Primentra
Getting Started
Data Grid
Approvals
Set up
Modeling
Business Rules
Users & Roles
Sign-in & Security
Install and run
Installation
Administration
Integration & API
Architecture
Migrate from MDS
Migrating from MDS
Documentation/Approvals/Role: Administrator

Role: Administrator

On this page

An administrator has every approver action, plus two powers no approver has: they may review any request, and they may Force approve.

What an administrator may do

  • Review a request for any entity, without being on its approver list.
  • Approve their own submission, whatever the entity's self-approval setting.
  • Force a request through, whatever the approval strategy.

The queue on My Approvals therefore shows every pending request in the installation, not only those for assigned entities.

Force approve

Force approve applies a request immediately and skips every approval requirement, including a pending multi-approver vote.

When to use it

  • A required approver is unavailable and the change is time-critical.
  • The request went to approvers who are no longer responsible.
  • An urgent correction must reach the master data before the normal cycle finishes.

How to use it

  1. Open the request from Settings › My Approvals.
  2. Scroll to the bottom of the decision column. Force approve is below Reject and is shown to administrators only.
  3. Read the Administrator override warning.
  4. Enter a reason. It is optional, but it is the only record of why the override happened.
  5. Click Force approve.

An orange Force approved banner confirms that the changes were applied.

A force approval cannot be undone from the UI. It is written to the audit log with the action force_approved, the administrator's identity and the reason. See Audit Log.

What the submitter sees

The changes go live the same way a normal approval applies them. The submitter gets the standard "your changes have been approved" email, with the administrator as the reviewer.

Other administrator tasks