Status Workflow

Control which status moves are allowed, which need a reason, and which need approval.

Overview

An asset moves through 14 default statuses from Planned to Stolen. The workflow decides which moves exist; each transition can require a reason and/or an approval through the shared approval engine. An emergency override lets a user authorise now and have it approved afterwards.

When to use status workflow

• You want a status such as Operational to be reachable only after commissioning.
• You need approval before an asset is marked Lost, Stolen or Decommissioned.

Prerequisites

• Standard setup loaded (Configuration → Org Structure → Load standard setup)

Step by step

1. 1Open Status WorkflowIn Assets, open Configuration → Master Data → Status Workflow.
2. 2Review the transitions
3. 3Change a rule
4. 4See it on an asset

Permissions

These permission keys control access (granted to roles in Administration → Roles & Permissions):

• assets.status.read
• assets.status.manage
• assets.asset.status
• assets.asset.approve

Automation

• Changes on this screen are written to the asset audit trail and the asset timeline.

Related features

• Commissioning
• Asset Register