Overview

Model branch and department hierarchy for scoped access, reporting, and routing.

Audience

• Admin
• Ops

Product Area

Workspace Model

Prerequisites

• Organization created

Steps

1. Create branch tree

Add legal entities and branch ownership to mirror operational structure.

1. Map departments

Assign department cost centers and escalation owners.

Expected Result

The Workspace Model 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

• Flat hierarchy causes routing conflicts: Model parent-child branch relationships explicitly.

Related Articles

• Set RBAC and Matter Permissions

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.