Dashboard, statistics and platform readiness

Review your current extension

Confirm the signed-in user’s visible local extension and phone readiness.

Audience: CRM administrators, staff callers, customer contacts, voice-platform engineers and website operatorsPermission: ViewModule v1.1.3
Exact navigationAdmin Area → Setup → xConnect
Before you begin
  • Confirm the module is active and use the exact navigation shown above.
  • Use an account with the stated module and core CRM permissions.
  • Use known test records when changing statuses, visibility, saved filters or global navigation.

What this guide covers

Confirm the signed-in user’s visible local extension and phone readiness. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Open Admin Area → Setup → xConnect.
  2. Locate the record, setting or action used to review your current extension.
  3. Complete the displayed fields or controls exactly as described in this guide.
  4. Select the available save, submit, update, call, sign, upload or confirm action.
  5. Return to the related register, portal, dashboard or call panel and verify the recorded result.

Fields, choices and supported possibilities

Dashboard evidenceConfirm the signed-in user’s visible local extension and phone readiness.

Code-backed validations and workflow rules

  • Statistics are refreshed from stored xConnect records and runtime reconciliation where available.

Expected result and verification

  • The review your current extension workflow completes without a validation, permission or availability error.
  • The relevant case, document, proposal, call, extension, widget session, timeline or audit evidence shows the expected state.
  • Any client-visible or public result appears only where the code explicitly allows it.

Security, privacy and operational checks

  • Use a controlled test case, contact, extension or website origin before production rollout.
  • Grant the minimum permissions needed and protect private documents, call metadata, signing evidence, API credentials and infrastructure paths.