This topic will walk you through how to manage Ironclad's Salesforce integration permissions.
Note: This article is intended for users setting up the Ironclad Salesforce Integration for the first time or for those doing a fresh install of the Ironclad Managed Package.
- If you are looking for documentation on package versions 2.1 and below, refer to Salesforce Integration Overview (Legacy).
- If you want to upgrade from a version below 2.2 to a version above 2.16, refer to Upgrade the Ironclad Salesforce Integration.
- If you installed an early-access package (between version 2.4 and 2.12) and are now switching to the official release package (2.16+), refer to Upgrade Early Access Package to Official Release.
Ironclad’s Salesforce Integration Permissions
Because you cannot update a permission set from a managed package, it is standard to clone a managed permission set and add to it if your company’s needs change. With this in mind, you should add your newly created lookup fields to a cloned permission set.
In this example, we must clone the Ironclad Standard User permission set. If you plan to assign Ironclad Admin permissions to non-admin Salesforce users, you should clone the Ironclad Admin permission set as well.
Manually Add Permissions
If you prefer to not use the managed package’s permission sets and want to incorporate the required permissions into existing permission sets, add the following object permissions:
Base Ironclad Access
Object Name | Object Permissions | Tabs Settings |
---|---|---|
Ironclad Approvals | Read | -- |
Ironclad Contracts | Read | Visible |
Ironclad Signatures | Read | -- |
Ironclad Workflow Configurations | Read | Visible |
Ironclad Workflows | Read | Visible |
Launch Ironclad Workflow | -- | Visible |
Error Logs | Read, Create, Write, Delete | — |
For each object that has a lookup field for Ironclad Workflows | Read, Write |
Additional Ironclad Admin Permissions
Object Name | Object Settings | Tab Settings |
---|---|---|
Ironclad Approvals | Create, Edit, Delete | |
Ironclad Contracts | Create, Edit, Delete | Visible |
Ironclad Signatures | Create, Edit, Delete | -- |
Ironclad Workflow Configurations | Create, Edit, Delete | Visible |
Ironclad Workflows | Create, Edit, Delete | Visible |
Launch Ironclad Workflow | -- | Visible |
For each object that has a lookup field for Ironclad Workflows | Read, Write |
Clone Packaged Standard Permission Set
- In Salesforce, navigate to Setup > Users > Permission Sets.
- Click Clone located next to the Ironclad Standard User permission set.
- Enter a Label and API Name. Click Save.
Add Lookup Object Access to Cloned Permission Set
After you clone the standard permission set, you must add access in your cloned Permission Sets to the object that you created a lookup field for. In this example, we are adding access to the Contact object because we previously created a lookup field for contacts on the Ironclad Workflow object.
- In Salesforce, navigate to Setup > Users > Permission Sets.
- Select the Ironclad Standard User Clone permission set, and then click Object Settings.
- Select the object name that you want to edit. In this example, Contacts. The permissions are currently set to No Access.
- Click Edit.
- Under Object Permissions, select Read and Write permissions. Click Save.
- Repeat this process for each object type that you added a lookup field for.
- If you cloned the Ironclad Admin User Clone permission set, repeat this process for the permission set.
Assign Permission Sets
After you’ve cloned and updated your permission sets, you must assign them to the proper users. This section walks you through how to assign the Ironclad Standard User Clone permission set, but if needed, you can use the same steps to assign the Ironclad Admin Clone permission set as well.
- In Salesforce, navigate to Setup > Users > Permission Sets.
- Select the Ironclad Standard User Clone permission set.
- Click Manage Assignments, and then click Add Assignments.
- Select the users you want to add to the permission set, and then click Assign.