Configure xConnect and synchronise
Set WSS URL, domain and isolated switch path, then generate module-owned configuration.
Exact navigationServer administration → supplied xConnect deployment runbook
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
Set WSS URL, domain and isolated switch path, then generate module-owned configuration. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Open Server administration → supplied xConnect deployment runbook.
- Locate the record, setting or action used to configure xconnect and synchronise.
- Complete the displayed fields or controls exactly as described in this guide.
- Select the available save, submit, update, call, sign, upload or confirm action.
- Return to the related register, portal, dashboard or call panel and verify the recorded result.
Fields, choices and supported possibilities
Deployment actionSet WSS URL, domain and isolated switch path, then generate module-owned configuration.
Code-backed validations and workflow rules
- Use read-only audit first, module-owned paths, same-operation rollback and live verification.
- Do not change unrelated voice services or enable PSTN.
Expected result and verification
- The configure xconnect and synchronise 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.