Customer work, connected.

Help & supportMyAccount
Custom software development brief

Complete Login requirements

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Describe authentication, MFA, SSO or access expectations.

Audience: CRM administrators, project teams, developers, authorised client contacts and public prospectsPermission: Secure-link recipientModule v1.1.1
Jump to steps
Where to goSecure recipient link → Custom Software Development Brief
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

Describe authentication, MFA, SSO or access expectations. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Go to Secure recipient link → Custom Software Development Brief.
  2. Go to the relevant custom-software section section containing Login requirements.
  3. Enter or select Login requirements using the supported value described below.
  4. Continue to the next step or save the current brief so autosave records the value.
  5. Reopen the brief or review page and confirm the value is shown correctly.

Fields and options

Login requirementsDescribe authentication, MFA, SSO or access expectations.

Rules and limits

  • The field is stored as part of the current request or intake answer set.
  • Leave an optional field blank only when the form permits it; required fields must pass server-side validation.

Check it worked

  • The complete login requirements 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.

Security, privacy and operational checks

  • 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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page