How to Manage Pipeline Permissions in Sparkforge
Pipeline Permissions in Sparkforge let you set who can view, edit, or fully see each Opportunities pipeline. Share with all users, pick specific users and roles, or exclude exceptions, with 60 days of audit log history.
Pipeline Permissions control visibility and editing rights for individual pipelines inside Opportunities. Use them to keep sensitive deals private, give each team member a clean pipeline view, and protect stage structure without changing broader sub-account roles.
What Pipeline Permissions Do
Admins choose how each pipeline is shared. The same rules apply on web, mobile, and through the API. Dashboards and metrics honor pipeline access and Assigned Data.
Configure Pipeline Permissions
- Go to Opportunities → Pipelines.
- Click the key icon next to a pipeline to open Manage permissions.
- Pick a Sharing mode: Share with all users, Share with selected users/roles, or Exclude specific users.
- For each user or role, choose an Access level: View Only, Edit, or No Access.
- Optionally click Copy link to share direct access with teammates who already have permission.
- Click Save.
Sharing Modes
- Share with All Users — one click sets everyone to View Only, Edit, or No Access.
- Share with Selected Users — pick individuals or roles and set their level.
- Exclude specific users — keep the pipeline global, then remove access for a few exceptions.
Access Levels
- View Only — can move and update opportunities. Cannot add, edit, or delete stages or pipelines.
- Edit — full control to add, edit, and delete pipeline stages, including the pipeline itself.
- No Access — the pipeline is hidden in web, mobile, and API responses.
Admins always retain full access regardless of permission settings.
Audit Logs and Safeguards
Sparkforge logs every create, update, or revoke action with user, pipeline, action, and timestamp for 60 days. Filter the log under Settings → Audit Logs by user, module (Pipeline Permissions), action, and date range.
The system blocks revoking access from any user who currently owns opportunities in that pipeline. Reassign ownership first, then update permissions.
Frequently Asked Questions
What is the difference between View Only and No Access?
What if a user already owns opportunities and I set them to No Access?
Do permissions sync to the mobile app?
Can I assign permissions by role instead of user?
Will permission changes break automations?
How long are audit logs retained?
Was this article helpful?
Thanks for the feedback.