Using SteelBrick CPQ Permission Sets

by Community Manager on ‎08-12-2015 05:04 PM - edited on ‎06-12-2017 04:22 PM by Community Manager

Permission Sets are the best way to ensure your admins and users have the correct field and object level permissions when upgrading to new SteelBrick releases. Any new objects or fields are included in the permissions and only require you to assign them to your users. This also allows you to retroactively grant other users permission to access their org. 


Note: After an upgrade if your users see error messages in the client about missing permissions, it means their profiles do not have object or field level permissions granted for those new fields added since you last upgraded. If you use the SteelBrick permission sets, you will avoid this error altogether.



Granting SteelBrick CPQ Permission Sets:

  1. Navigate to: Setup | Manage Users | Permission Sets.PermissionSets.png
  2. Click SteelBrick CPQ User to grant access to standard user permissions across all SteelBrick CPQ objects.
  3. Click Manage Assignments. Here you will see the users that are currently granted that particular Permission Set.
  4. Click Add Assignments to add one or more new users to the Permission Set.
  5. Using either a List View, or sorting by the Profile or Role fields, locate your set of sales users.  Check the box next to each relevant users and click Assign.

To assign permissions to your admin users, repeat the above steps using the SteelBrick CPQ Admin permission set and select your admin users. 


Note: Want to automatically assign the sales user permission set to licensed CPQ users? See Script to Automatically Assign CPQ Permissions to Licensed Users.


Permission Sets are updated following each SteelBrick CPQ product release to reflect any new Fields, Objects, etc. For more information on Salesforce Permission Sets, see What are permission sets?

The existing Permission Sets can be cloned in order to create a custom permission set. Permission sets cannot be linked to a Salesforce Profile. 

Note: Read permission is required on ALL managed objects from the SB CPQ package.

by naureenhameed
‎02-01-2016 01:52 AM - edited ‎02-01-2016 02:35 AM



Thanks a lot for heads up and prompt support (as always from Steelbrick)

Looks like granting permission set worked for our early bird Steelbrick user in Europe. Shes able to create quotes now.


by Carol
‎02-01-2016 01:17 PM - edited ‎02-01-2016 01:24 PM


I'm working through the new SteelBrick CPQ User permission set and comparing to our most widely used profile for SB CPQ access.  We have several (User, Approver, Read Only) on different profiles.  I'm noticing that SteelBrick has many instances where the new CPQ User permission set allows a type of access that we do not. For example: if we gave all users access to the permission set, it appears that users who are not supposed to see discount levels would see them... and on other objects would be able to delete items that they should not. 


It would be really helpful to have a list of fields (and their associated objects) that must be set to a certain minimum R level for users to be able to quote. Good examples are the ones that my users found.. (see attached screen shot). It's better to know these new fields upfront and as an admin be able to address and set appropriate CRED.

Any chance there's a list some where?





by reneemidd
on ‎05-02-2016 01:02 PM

Does a user need to be granted CPQ User Permissions to add Products directly to an Opportunity?

by Carol
on ‎05-02-2016 08:15 PM


Hi reneemidd,


In my experience, users can add products to the Opportunity in two ways, either 1) by marking the SteelBrick Quote as Primary, which transfers the products to the Opportunity (Opportunity Products related list object)  OR 2) by hovering over the Products related list on the Opportunity, clicking add product.   The former is SteelBrick functionality and would require CPQ license / permissions.  The latter is standard Salesforce functionality and does not (it does require appropriate profile permission in Salesforce, however!).


cheers,  -Carol

by marcelorossi
on ‎10-19-2016 08:38 PM

I have permissioned a user for CPQ User but it has been 24 hours and they are still unable to see the quote object, is there something I am missing?

by q2amycg
on ‎08-10-2017 09:53 AM

Another important note when you are setting up end user permissions for CPQ:


Any field required for calculation or displayed in the quote line editor (fields listed in the Line Editor field set on the Quote, Quote Line and Quote Line group objects) is required to have read access for the end users. If they do not have at least read access, the QLE VisualForce page will not render the quote lines (blank page).