Setup, administrator access and schema readiness

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 the module targets CRM 2.3.*.

Audience: CRM administrators, integration developers, external portal backend teams and security reviewersPermission: AdministratorModule v1.0.0

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 the module targets CRM 2.3.*. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Go to Admin Area → Setup → Modules.
Find the record, endpoint, field or action used to check the crm requirement.
Complete the displayed values exactly as described in this guide.
Select the available save, submit, send, upload, create, update or confirm action.
Return to the related register, portal, activity log or API response and verify the expected result.

Workspace or endpointAdmin Area → Setup → Modules

PurposeVerify the module targets CRM 2.3.*.

The action is available only where the supplied module exposes it and the signed-in user or API client meets the stated access conditions.
Internal helpers are documented under the visible workflow or endpoint they support rather than presented as invented menu pages.

The check the crm requirement workflow completes without a validation, permission, ownership or availability error.
The related record, portal view, activity entry, notification log or API response shows the expected state.
Client-visible, public and API data remains limited to the code-backed ownership and visibility rules.

Use controlled test records and non-production credentials before wider rollout.
Grant least privilege and protect secure links, personal data, uploaded files, signatures, API tokens, allowed origins and server IPs.

Was this guide useful?Your response is stored only in this browser.