Sales CRM · Feature guide

Understand contact-map access and resolve problems

Check customer visibility, management permissions, version conflicts and contact membership without changing existing access rules.

Audience: authorised staffPermission: Authorised staff; administrators manage capabilities through the existing staff permission workflowReviewed 30 October 2026

Where to goSales CRM → Relationships; existing staff permissions when administration is required

Before you start

Use your own authorised staff account in the intended Pixie CRM workspace. The Sales CRM module must be available and your role must include the permissions stated above. Existing leads, customers, communications and customer portal pages retain their normal access rules.

Follow these steps

Confirm that you can open Sales CRM and the intended native customer.
If viewing works but editing does not, check the Manage customer contact reporting maps capability.
If a saved map shows unavailable contacts, review their current membership through the normal native customer workflow.
If a review or save is rejected, read the message and correct the indicated relationship or reopen the current map.
Refresh the map after another editor has made changes.

Behavior and limits

Sales CRM View or View Own permission is required to enter the feature, and native customer access is checked independently. View all opportunities alone does not reveal restricted customer contacts.
Managing a map requires its separate capability. Adding this feature did not automatically grant that capability to existing staff.
A customer map is shared customer relationship information rather than an opportunity-owned record. Staff with native access to that customer and Sales CRM viewing access can read its map even if they do not own a particular opportunity.
Reporting-manager links do not grant staff permissions, share opportunities, enable customer portal access or expose another customer’s contacts.
Current customer access is checked on reads, previews, saves, state changes and completed-request retries. Changed contact membership is checked before accepting a save.
Most recent completed save retries return their existing result without duplicate history. Older or changed requests require reopening the current version.
Every workspace stores its own map definitions and history. Native universal module distribution does not share maps between workspaces or bypass subscription and explicit module-disable rules.
No message, notification or invitation is sent when a contact is added, removed, assigned a manager or restored in a map.

Check it worked

Check that an authorised viewer can read the map without gaining editing controls.
Confirm a user without native customer access cannot read the map or search its contacts.
Check that existing customer and contact records remain unchanged after a map edit.

Troubleshooting

Customer map unavailable can mean the customer was removed, your access changed or Sales CRM is unavailable in the current workspace.
A changed-version message protects another editor’s work. Reopen the current map instead of retrying stale values.
A missing-contact message requires an existing contact from this customer; a contact from a different customer cannot be inserted by entering its identifier.
A circular-relationship message requires changing the recorded manager chain; increasing permissions will not make a cycle valid.