Check the CRM requirement — xConnect | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/xconnect-installation-versions-permissions-requirements Publisher: Pixie Technologies LLC Installation, versions, access and permissions Check the CRM requirement Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Confirm xConnect targets CRM 3.0.* before activation. Audience: CRM administrators, staff callers, customer contacts, voice-platform engineers and website operators; Permission: Administrator; Module v1.1.3; Where to goAdmin Area → Setup → Modules 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 Confirm xConnect targets CRM 3.0.* before activation. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow. Follow these steps - Go to Admin Area → Setup → Modules. - 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 WorkspaceAdmin Area → Setup → Modules ActionVerify xConnect targets CRM 3.0.* before activation. Rules and limits - You can use this action only when the supplied module exposes it and your signed-in account has both the required module permission and the relevant core CRM access. - Background helpers are documented inside the user-facing workflow they support; they are not separate menu actions and should not be treated as manually callable screens. Check it worked - The check the crm requirement 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 Understand xConnect (https://pixiecrm.com/help-centre/xconnect-installation-versions-permissions-overview)Understand module version 1.1.3 (https://pixiecrm.com/help-centre/xconnect-installation-versions-permissions-version)Installation, versions, access and permissions (https://pixiecrm.com/help-centre/topic/xconnect-installation-versions-permissions)Browse all xConnect guides (https://pixiecrm.com/help-centre/category/xconnect)Visitor Intelligence & Live Engagement (https://pixiecrm.com/help-centre/category/visitor-intelligence-live-engagement)Add and manage customer contacts (https://pixiecrm.com/help-centre/add-and-manage-customer-contacts)Configure customer contact permissions (https://pixiecrm.com/help-centre/configure-customer-contact-permissions)Understand roles and permissions (https://pixiecrm.com/help-centre/understand-roles-permissions-and-visible-menus)Data, privacy and security (https://pixiecrm.com/help-centre/category/data-privacy-security)Review the activity log (https://pixiecrm.com/help-centre/review-the-activity-log)