Understand buying-team permissions and history
Understand contact access boundaries and diagnose missing relationships or rejected edits without exposing restricted customer information.
Where to goSales CRM → Deals → Open opportunity → View buying team → History
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
- Use your normal staff account and open an opportunity within your permitted scope.
- View the buying team only when you can access its currently linked native customer.
- Select History beside an available contact to inspect the latest association actions, actor and time.
- Read the role, influence and position recorded with each action. Role names use the current role definition.
- If a record becomes unavailable, refresh and follow the error guidance rather than trying to bypass customer permissions.
Behavior and limits
- Sales CRM View all deals does not independently grant access to native customer contacts or their relationship notes.
- Own-view staff can only open their own opportunities. A permitted opportunity view still needs native customer access before the buying team is exposed.
- Adding, editing, retiring and restoring associations require opportunity Edit and current customer access for both editor and opportunity owner.
- Moved, deleted or formerly linked customer contacts are masked. Their detailed association history is unavailable while the contact is outside the current customer scope.
- History shows the latest 100 association actions with role/influence/position metadata. Prior note text is not retained. General opportunity history records a generic association action without exposing contact details.
- Association edits have their own revision checks and also verify the opportunity context. They do not change the parent opportunity revision or fire unrelated opportunity automations.
- Identical create-request retries reuse the same association, while conflicting reuse is rejected. Unique contact associations prevent duplicate records.
Check it worked
- Check access using each intended staff role through your normal sign-in process.
- Confirm an unavailable association contains no former contact name, contact ID, role or notes.
- Compare a recorded action’s actor and timestamp with the change you made.
Troubleshooting
- A permission or unavailable-customer message requires the normal customer-access configuration; a CRM role alone is insufficient.
- A stale association or opportunity message requires a refresh before saving again.
- If the session or request token expires, sign in normally and refresh the page. Never share passwords or session cookies.
- For support, provide the opportunity ID, association ID if visible, intended action and exact error text, without unnecessary private customer information.