Admin

Admin is the technical layer beneath the everyday features: how phones are provisioned, where they physically are (for emergency calls), how the system talks to other software, and the dial codes users press for features. You will set most of this up once and rarely touch it again.

Webhooks

Tenant-wide webhooks — outbound HTTP requests the PBX fires on call events so other systems can react in real time. You configure one URL and method per event, and the password field is write-only (leave it blank to keep the existing value). Each event expands to its settings and has an on/off state; they are off until you configure them. Events include:

• When a call ends (CDR) — the full call-detail record, the most common hook.
• Wake-up calls — when one fires, is cleared, or is missed.
• Do-not-disturb — when DND is enabled or cleared.
• …and other lifecycle events.

These are the tenant-level equivalent of the per-extension webhooks in Directory; use these when you want every call (not one extension's) to notify an external system.

Devices

The provisioned desk phones on your tenant, each bound to a MAC address and assigned to one or more extensions. The table lists each device's MAC, pairing, name, vendor, model, firmware version, address, RPS status, extension, and button template. Row actions let you Add, Edit, Reload (push config to the phone), Reset, or Delete a device.

This is where a physical handset becomes usable: add the phone by MAC, assign it to a person, and it provisions automatically (via RPS, the redirection provisioning service) on next boot. Once a device exists here, its keys are set by the extension's Buttons tab (Directory) or a shared button template (below).

Locations

The physical addresses associated with your tenant, used for E911 (emergency-call routing to the right dispatcher), billing region, and per-location call routing. Each location has a Name, City, State, Country, and active flag; + Add location creates one. Getting these right matters: emergency services are dispatched to the location tied to the calling extension.

Location assignments

Maps each extension to a physical location. The table pairs each user (extension) with its current location; set it and Save. Extensions inherit the location for E911 routing and per-extension billing. Use this after creating locations to tell the system where each person actually sits.

Button templates

Reusable, per-vendor/model button-key profiles (for example Yealink or Snom phones). A template defines what each line key, soft key, and expansion-module key does; apply it to many extensions so a whole fleet of the same handset gets identical keys without configuring each phone by hand. Create one with Add and name the models it targets.

User page control

The tenant-wide default for what app features users may see and edit on their own user page. Each feature has three states — enabled, disabled, or system default. It mirrors the per-extension User Page Field Control (Directory); set the tenant baseline here, and override per person there. Controls are grouped: Page-level (which extensions, calls, and home-screen widgets the mobile app exposes), App settings, Features, Call Forwarding, Mailbox, Profile picture, Preferences, Device selection, Notifications, Desktop phone buttons, Cell phone numbers, Tokens and Passkeys, CRM Settings (including Google and ActiveSync), and Monitoring and call pickup.

CRM integrations

Connect the phone system to external CRM, helpdesk, identity/directory, messaging, and video-conferencing tools, so inbound calls pop the matching contact and outbound activity is logged automatically. The page is a catalogue grouped by category, with a Configure → on each connector — for example HubSpot, Salesforce, Zoho CRM, Pipedrive, and Microsoft Dynamics 365 under CRM (several are OAuth-only). Pick a tool, authenticate, and calls start linking to the right records.

Star codes

The feature dial codes users press on their phones — for example *72 to enable call forwarding. Codes are grouped by purpose: Making Calls (redial, call return, intercom), Transferring calls, Voicemail, Recording, Mobile phone, Anonymous Calls, Call Center, Call Forwarding, and Miscellaneous. Each feature has a code field; leave a field blank to disable that feature for everyone on the tenant. (This page is also linked from the Settings sidebar for convenience.)

Everyday tasks

• Add a new desk phone → Devices → Add, enter the MAC, assign the extension; it provisions on next boot.
• Make emergency calls route correctly → create the site under Locations, then map people to it under Location assignments, and set each person's emergency caller ID in Directory.
• Configure a fleet of identical phones → build a Button template and apply it.
• Pop customer records on calls → CRM integrations, configure your CRM.
• Change or disable a feature code → Star codes, edit or blank the field.
• Send every call's CDR to another system → Webhooks → When a call ends (CDR).

Next: Status — the live, real-time view of what the system is doing right now.