Understand Active extension status
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Recognise an enabled and provisioned extension.
Where to goAdmin Area → Setup → xConnect → Allocated extensions
Before you start
- Verify 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 helps you do
Recognise an enabled and provisioned extension. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Go to Admin Area → Setup → xConnect → Allocated extensions.
- Find the relevant record, setting or action on the page. Use the record name, reference, current status and surrounding details to make sure you are working on the intended item.
- Complete each field or control that applies to this task. Keep verified existing values intact, supply required information, and resolve any validation message before moving on.
- Use the primary action shown by the workflow—such as Save, Submit, Update, Call, Sign, Upload or Confirm. Submit once, then allow the request to finish before taking another action.
- Reopen the related register, portal, dashboard or call panel. Verify the status, visible values and any audit, activity, document, call or notification evidence created by the action.
Fields and options
Numbering or provisioning ruleRecognise an enabled and provisioned extension.
Rules and limits
- Extension changes are tenant-aware and queued for switch synchronisation when provisioning is enabled.
Check it worked
- The understand active extension status 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
- Validate the change with a controlled test case, contact, extension or approved website origin before relying on it in production.
- Grant only the permissions needed for the task, and keep private documents, call metadata, signing evidence, API credentials and infrastructure paths restricted to authorised users.
Related guides
Was this guide useful?Your response is stored only in this browser.