Asset Restrictions

Overview

The Asset Restriction feature lets you flag an individual asset as restricted, signalling to planners, schedulers, and dispatchers that the asset has a known issue, limitation, or temporary condition that must be considered before work is planned or executed against it.

When a restriction is active, the system can either warn users that the asset has limitations (but still allow planning and dispatching to proceed), or block dispatching entirely until the restriction is lifted.

Restriction indicators appear across the platform — in the asset list, site overview, the employee and team planner views, and when creating or dispatching activities.

Who Can Use This Feature

You need the Update Asset (updateAsset) permission to enable, configure, or remove a restriction on an asset. If you do not see the restriction controls described below, contact your system administrator to review your permission role.

All users with read access to assets can see restriction indicators, regardless of their permission level.

Where to Find Asset Restriction Settings

You can manage an asset's restriction from two places:

1. Asset Modal
Navigate to Sites → Assets, then double-click any asset to open the Asset Modal. Scroll to the Asset Restriction section within the General tab.

2. Asset Side Panel (Site Overview)
Open the Site Overview dashboard and click on an asset to open its side panel. Expand the Asset Restricted card in the panel.

How to Enable a Restriction

1. Open the asset using either method described above.

2. Locate the Asset Restricted toggle and switch it on.

3. Two additional fields will appear:

   • Restriction Behaviour (required) — Choose how the system should respond when someone tries to plan or dispatch work against this asset:

     • Warn — Allows planning and dispatching to proceed, but displays a visible warning everywhere the asset appears, prompting users to take note before continuing.

     • Block — Prevents dispatching of activities linked to this asset. Planners can still create and view work orders, but the system will actively stop the dispatch action until the restriction is lifted.

   • Restriction Reason (required) — Enter a short explanation of why the asset is restricted (e.g., "Awaiting inspection after incident on 2026-04-10"). This text is displayed to users as a tooltip, inline alert, or toast notification depending on the context.

4. Save your changes. The restriction takes effect immediately across all views.

How to Remove a Restriction

1. Open the asset modal or side panel.

2. Switch the Asset Restricted toggle off.

3. The reason and behaviour settings are automatically cleared and reset to defaults.

4. Save your changes. The restriction is lifted immediately.

How Restrictions Affect Planning, Scheduling, and Dispatching

Assets List
A warning or alert icon appears next to the asset name in the asset list. Hovering over the icon shows the restriction reason as a tooltip.

Site Overview — Asset Side Panel
A prominent warning banner is shown at the top of the asset's side panel. The icon colour and tooltip text reflect the restriction behaviour and reason.

Activity Modal (Creating or Editing an Activity)
When opening an activity linked to a work order on a restricted asset, a highlighted inline message is displayed:

• Block behaviour — A red danger banner reads: "Planning blocked: [reason]"

• Warn behaviour — A yellow warning banner reads: "Planning allowed with restrictions: [reason]"

This message is visible before any dispatching action is taken, giving planners a clear prompt to review the situation.

Employee Planner View
Activity cards in the Employee Planner that are linked to a restricted asset display a yellow warning icon (���) on the activity block. Hovering over the activity title reveals the message:

"One or more assets on this activity have an active restriction."

This warning is combined with other planner warnings (e.g. skill gaps, employee count mismatches) and does not prevent the activity from being visible in the planner.

Team Planner View
The same warning icon and hover message appear on activity cards in the Team Planner view, for both single-asset and multi-asset activities. If any asset on the activity has an active restriction, the warning is triggered.

Dispatching
Asset restriction has a direct enforcement role at the point of dispatch:

• When a dispatcher attempts to dispatch an activity linked to a work order on a restricted asset, the system runs a validation check on the server before confirming the dispatch.

• If the restriction behaviour is set to Warn, the dispatch is permitted, but the dispatcher may see a warning notification.

• If the restriction behaviour is set to Block, the dispatch is rejected. A toast notification is shown to the dispatcher with the message:

  "Planning blocked: [reason]"

  The activity cannot be dispatched until the restriction is either removed or changed to Warn.

The following table summarises the impact by behaviour type:

Important Limitations and Notes

• Restriction does not retroactively affect already-dispatched activities. Only activities being dispatched after the restriction is set are affected.

• Restriction applies at the work order level via its linked asset. If a work order is not linked to an asset, no restriction check is applied.

• Multi-asset activities are also covered. In the planner views, if any asset on the activity has an active restriction, the warning is shown on the activity card.

• Disabling the restriction clears all restriction data (behaviour and reason). If you temporarily remove a restriction, you will need to re-enter the reason when re-enabling it.

• Both Behaviour and Reason fields are required when enabling a restriction. You cannot save an enabled restriction without selecting a behaviour and providing a reason.

• Restriction status is asset-level, not site-level. Restrictions must be managed individually per asset.

Use Case Examples

• Planned maintenance window: Set a Warn restriction with the reason "Scheduled for full inspection — confirm with site manager before planning." Dispatching remains possible for urgent work, but planners are alerted.

• Safety incident pending investigation: Set a Block restriction with the reason "Asset quarantined following adverse event on 2026-04-12. Do not dispatch until cleared by HSE team." No activities can be dispatched to this asset until the restriction is lifted.

• Temporary operational constraint: Set a Warn restriction with the reason "Reduced load capacity until component replacement on 2026-04-20." Dispatching is allowed, but crews are informed before going to site.