Create/Update Permission Set for Foxit API User (Salesforce)
Explains how to create or update a permission set for the Foxit API user within Salesforce.
Answer
Purpose
To create a Salesforce Permission Set named FoxitAPIUser and grant full object and field permissions for Foxit Envelopes (FoxiteSign__Envelope__c).
ScopeFollow this SOP when provisioning or updating permissions for users or integrations that require full access to Foxit eSign Envelope records in Salesforce.
PrerequisitesBefore starting, confirm:
- You have Salesforce admin or permission-set management rights.
- You know the object name: FoxiteSign__Envelope__c.
1) Go to Permission Sets
- Log in to Salesforce.
- In Quick Find, type Permission Sets.
- Click Permission Sets in the results.
- Click New to create a new permission set.
2) Create the Permission Set
- In Label, enter: FoxitAPIUser
- In API Name, enter: FoxitAPIUser
- (Salesforce may auto-fill API Name after Label — verify it matches.)
- Click Save
3) Open Object Settings
Inside the Permission Set, find and click Object Settings.
4) Locate the Foxit Envelopes object
- In the Object Settings search bar, search for:
- Foxit Envelopes
- or API name FoxiteSign__Envelope__c
- Click Foxit Envelopes (FoxiteSign__Envelope__c) to open its settings.
5) Enable Object Permissions
- Click Edit.
- Enable the required object permissions (as shown in the doc), typically:
- Read
- Create
- Edit
- Delete
- View All
- Modify All
- Write (if applicable in your org’s UI)
- Click Save.
6) Enable Field-Level Security
- Still within the object’s settings, scroll to Field Permissions.
- Check/select all fields as shown in the document.
- Click Save.
After saving:
- Re-open the Permission Set → Object Settings → Foxit Envelopes.
- Confirm:
- All intended object permissions are enabled.
- All fields are set correctly for visibility/editing as needed.
- If this Permission Set already exists, skip Step 2 and start from Step 3 to update permissions.
- Grant only the permissions required for the integration’s role if your security model prefers least privilege (this SOP currently grants broad access).