Roles & permissions
Under Users & Access, the Permissions feature (Premium) adds granular role-based access beyond Admin vs base user, so mid and large MSP sales ops can separate who builds the catalog from who sells.
Illustrative dashboard · your data will vary
Why it matters for MSP sales ops
Role–permission mappings
Admins create roles and map them to documented permissions; users can hold multiple roles (union of permissions).
Nine resource permissions
Including Quote editor, Quote template editor, Product viewer/editor/importer, Pricing book editor, Company editor, Whitespace viewer, Procurement editor, plus Admin toggle.
Viewer license option
Premium Viewer is read-only on products and is not counted against seats.
MSP vs portal users
Access model distinguishes MSP users from customer portal users.
In Salesbuildr
- Open Users & AccessSettings → Users & Access → Users / Permissions.
- Define rolesCreate role–permission mappings for how your sales ops actually splits catalog, quoting, and oversight.
- Assign peopleGive users one or more roles; permissions combine.
- Pair with approvalsManager routing for Advanced Approval Workflow uses the same access model.
Permissions (role-based access) is available on Premium, so you can separate catalog ownership, quoting, and oversight as your team grows.
Help center: Users & Access 9328580 · Access & Permissions 1324059 · Security & Legal 9581906
See it on your quoting motion
We show the live settings paths, not a generic deck.
Related: Advanced approval workflows · Pricing books · Portfolio