SOURCE-BASED ANALYSIS · NO HANDS-ON RATING
Model seeing and doing as separate decisions
Pipedrive uses visibility groups to control which records a user can see and permission sets to control which actions a user can perform. Ownership, the item-level Visible to setting, pipeline visibility and administrator roles can further affect the result. A person who can open a deal may still be unable to edit, export or merge it.
Start from job outcomes
For a fictional sales organization, define the smallest access needed by a representative, a team lead and a reporting reviewer. The roles below are proposed test fixtures, not Pipedrive defaults.
| Fixture | Required outcome | Negative check |
|---|---|---|
| Representative | View and update owned deals | Cannot edit another group's restricted deal |
| Team lead | Review the team pipeline | Cannot change account-wide settings |
| Reporting reviewer | View approved Insights results | Cannot export or delete source records |
Test effective access, not configuration labels
Create synthetic records with different owners and visibility scopes. Sign in with approved limited accounts and test both an allowed action and a prohibited action. The official documentation notes that administrator permissions can bypass some visibility restrictions, so an administrator's view is not evidence of what a regular user sees.
- List the records, pipelines and actions required for each job.
- Assign the appropriate visibility group.
- Review permission-set actions such as editing, exporting and merging.
- Inspect item-level overrides and hidden pipelines.
- Test allowed and denied actions with limited users.
- Record the approver, review date and removal condition.
Check reporting and automation side effects
Insights and automations depend on the underlying records users can access. A narrower result or failed automation may reflect visibility rather than a faulty filter. Compare the same synthetic record set as an administrator and a limited user, then document the expected difference.
Accept the matrix when every user can complete required work without unnecessary data or administrative access. Plan-dependent limits for custom groups and permission sets should be verified in the current account rather than inferred from this guide.
Sources and verification
Official documentation checked on 2026-10-29. Worked examples are hypothetical planning exercises, not measured product benchmarks.