Pipedrive User Management Guide

• Model type: hybrid
• Description: Pipedrive uses a hybrid model combining permission sets (role-based templates controlling what actions users can perform, e.g., export data, delete records, manage pipelines) and visibility groups (controlling which records a user can see based on team/group membership). Permission sets are assignable per user. Visibility groups are hierarchical. Admins bypass visibility restrictions.
• Custom roles: Yes
• Custom roles plan: Professional plan and above (permission sets with custom configuration); visibility groups also require Professional or above
• Granularity: Action-level permissions (e.g., can export, can delete, can add products) via permission sets; record-level visibility via visibility groups (owner-only, team, company-wide). Granularity increases on higher plans.

1. Log in as an Admin or Account Owner.
2. Click your avatar (top-right) and select 'Company Settings'.
3. Navigate to 'Manage Users' in the left sidebar.
4. Click the '+ Add users' button.
5. Enter the new user's email address.
6. Assign a permission set (defaults to the company default if not changed).
7. Optionally assign to a visibility group.
8. Click 'Send invitation'. The user receives an email invite to set up their account.

Required fields: Email address

Watch out for:

• Adding a user immediately consumes a paid seat and triggers billing at the next billing cycle (or immediately on monthly plans).
• The invited user must accept the email invitation before they appear as active; pending invites still count toward seat usage on some plan configurations.
• Permission set and visibility group must be configured after invite or at invite time; defaults may be too permissive.
• SSO-enforced accounts (Ultimate plan) may require the user's email domain to match the configured SSO domain.

• Can delete users: No
• Delete/deactivate behavior: Pipedrive does not permanently delete user accounts. Users can only be deactivated (set to inactive). Deactivated users cannot log in and do not consume a paid seat, but their account record and associated data remain in the system. This preserves data integrity for historical records, activity logs, and deal ownership.

1. Log in as an Admin or Account Owner.
2. Navigate to Company Settings → Manage Users.
3. Locate the user in the active users list.
4. Click the three-dot menu (⋮) next to the user's name.
5. Select 'Deactivate user'.
6. Confirm the deactivation in the dialog. The user is immediately logged out and loses access.

Watch out for:

• Deactivated users cannot be permanently deleted; their email address remains reserved in the system and cannot be reused for a new account in the same Pipedrive company.
• Automations and workflow rules assigned to a deactivated user will fail silently or stop executing - these must be manually reassigned before deactivation.
• If the deactivated user was the owner of active deals in a pipeline, those deals remain in the pipeline but may not appear in standard 'my deals' views for other users until ownership is transferred.
• On annual billing, seat reduction credit is typically applied at renewal, not immediately - verify with Pipedrive billing support for mid-cycle deactivations.
• SSO-provisioned users deactivated in the IdP (e.g., Okta) are deactivated in Pipedrive via SCIM only on the Ultimate plan; on lower plans, IdP deactivation does not automatically deactivate the Pipedrive account.

• Where to check usage: Company Settings → Billing → Subscription (shows current seat count and active users); also visible under Manage Users where active vs. inactive users are listed
• How to identify unused seats: Navigate to Company Settings → Manage Users and sort or filter by 'Last login' date to identify users who have not logged in recently. Pipedrive does not provide a built-in 'unused seat' report natively; admins must manually review last login timestamps.
• Billing notes: Pipedrive bills per active seat. Deactivating a user frees the seat at the next billing cycle. Adding a user mid-cycle on monthly plans typically results in prorated billing. Annual plan seat reductions are generally credited at renewal. There is no free viewer or read-only seat tier - all users with access consume a full paid seat.

Every app in your stack that relies on Pipedrive data is affected when user access is misconfigured or stale. Pipedrive bills per active seat with no free viewer or read-only tier, so every user with access consumes a full paid seat regardless of how little they use it.

Deactivating a user frees the seat at the next billing cycle - not immediately. On annual plans, seat reductions are credited at renewal. Mid-cycle deactivations on monthly plans are typically prorated, but this should be confirmed with Pipedrive billing support.

Automations and workflow rules assigned to a deactivated user fail silently without notification. Admins must audit and reassign these manually before offboarding, or pipeline automation breaks without any alert.

The most consistent complaint across the Pipedrive community is that deactivated accounts cannot be permanently deleted. The former employee's email address remains permanently reserved in the system and cannot be reused for a new account in the same Pipedrive company.

Admins on lower plans (Lite/Growth) report that permission sets are limited or unavailable, making it difficult to restrict what regular users can see or do.

The separation between visibility groups and permission sets - two independent systems that must be configured independently - is a recurring source of confusion.

SCIM and IdP-based provisioning is locked to the Ultimate plan. Mid-market customers on Premium or below must manage every user lifecycle event manually, with no automated deprovisioning when an employee leaves.

Common complaints:

• Users report that deactivated accounts cannot be permanently deleted, leaving former employee email addresses permanently reserved in the system.
• Admins note that automations and workflow rules assigned to deactivated users fail silently without notification, requiring manual audits before offboarding.
• Users on lower plans (Essential/Advanced, now Lite/Growth) report that permission sets are limited or unavailable, making it difficult to restrict what regular users can see or do.
• Billing complaints about seat counts not adjusting immediately upon deactivation on annual plans, with credits only applied at renewal.
• Users report confusion about visibility groups vs. permission sets - the two systems are separate and must be configured independently, which is not obvious from the UI.
• SCIM/IdP provisioning is locked to the Ultimate (formerly Enterprise) plan, meaning mid-market customers on Professional/Premium must manage users manually.
• No CSV bulk import for users - users must be invited one at a time via email, which is cited as a friction point for large team onboarding.

Manual user management in Pipedrive is viable for small teams on Lite or Growth plans where the user count is stable and turnover is low. The process is straightforward: invite by email, assign a permission set, optionally assign a visibility group.

For teams with regular onboarding and offboarding, the manual process creates real operational risk. Silent automation failures on deactivation, no built-in unused-seat reporting, and the inability to delete accounts mean that access hygiene degrades over time without active auditing.

Teams on Premium or below who need IdP-driven provisioning face a hard ceiling: SCIM requires the Ultimate plan with SAML SSO configured. If automated provisioning is a requirement, that plan gate is the deciding factor.

Bottom line

Pipedrive's manual user management works for small, stable teams but accumulates operational debt quickly at scale. There is no read-only seat tier, no built-in unused-seat report, and no automatic cleanup of stale automations on deactivation - every one of these requires a manual admin action.

Teams managing more than a handful of users should establish a documented offboarding checklist that covers deal reassignment, automation reassignment, and billing cycle timing before deactivating any account.