Purpose and location
Model organizational boundaries used by administration, emergency routing and reporting.
Open Organization → Locations & Teams. The available controls depend on the active edition, module entitlement, role and tenant scope.
Before you start
Use a tenant-scoped administrator unless the task genuinely requires platform access. Create plans, locations and roles before assigning them to people or endpoints.
Capture the current value or export the affected records before a bulk or routing change. This gives the operator a precise comparison point and makes a supported transaction undo easier to assess.
Step-by-step workflow
Complete the steps in order. Do not combine an initial configuration with unrelated cleanup; small, attributable changes are easier to test and reverse.
- Create locations before assigning users or dispatchable addresses.
- Create teams for delegated administration and reports.
- Move users only after checking inherited access.
Field reference
Use the reference below while completing the form. Fields hidden by edition, module entitlement or role are intentionally unavailable to the signed-in user.
- Location
- Operational site and administrative boundary.
- Team
- Logical user grouping inside the tenant.
- Timezone
- IANA timezone used for schedules and presentation.
- Administrators
- Delegated users allowed to manage the boundary.
Acceptance checks
A saved record is only the beginning of validation. Run every relevant check below and retain the call-session ID, time and result when telephony is involved.
- Sign in as an affected ordinary user and confirm the intended access.
- Verify the change appears in the audit trail with actor, source IP and target.
Common mistakes and safe recovery
If a check fails, stop adding changes. Restore the previous value or use a supported transaction undo, regenerate PBX configuration, then repeat the smallest failing test.
- Avoid shared administrator accounts; individual identities make audit and rollback dependable.
What to include in a support case
Provide the tenant, module and object name, local time with timezone, expected result, observed result and the most recent successful state. For a call problem, include the logical call-session ID and the redacted SIP/SDP text diagnostic before requesting PCAP.
Never paste passwords, private keys, raw license payloads or unredacted customer media into a ticket. Use the one-time diagnostic grant and attachment controls when support requests additional evidence.