Overview

Define obligation controls, owners, and due-date policies for monitored regulations.

Audience

• Compliance
• Ops

Product Area

Compliance

Prerequisites

• Compliance workspace enabled

Steps

1. Select regulatory scope

Choose frameworks and jurisdictions relevant to the tenant.

1. Assign owners

Map each obligation to accountable role and escalation chain.

Expected Result

The Compliance 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

• Unowned obligations: Block publish until every obligation has an owner.

Related Articles

• Configure Deadline Escalation
• Read Status Page and Subscribe

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.