Overview

Set escalating alerts and fallback assignees for deadline-sensitive obligations.

Audience

• Compliance
• Ops

Product Area

Obligation Clock

Prerequisites

• Obligation set configured

Steps

1. Configure lead times

Set warning and critical thresholds per obligation criticality.

1. Define escalation recipients

Assign primary, backup, and executive escalation recipients.

Expected Result

The Obligation Clock workflow completes without unresolved validation errors, and the result is visible to the intended roles.

Security and Audit Notes

• Use the least-privileged role that can complete the task.
• Confirm the resulting change or decision appears in the workspace audit trail when the workflow changes customer data or access.

Limits and Preconditions

• Available controls depend on the tenant plan, enabled modules, jurisdiction, and administrator policy.
• If a named control is not visible, confirm entitlement and role access before treating the behavior as a product failure.

Troubleshooting

• Escalation loops: Avoid assigning the same user across all escalation levels.

Related Articles

• Configure Compliance Obligation Set

Escalation

If the documented result cannot be reached after the checks above, capture the workspace identifier, affected product area, timestamp, and a redacted error message, then use Support. Never include secrets, privileged legal content, or customer documents in the initial report.