Permission Sets and Other Technical Documentation

SRP provides several permission sets and custom permissions. Information about SRP permissions is available below. For more technical resources, see the Technical Documentation Pack on the Certinia Community.

• Permissions
• Data Dictionary

SRP Permission Sets and Custom Permissions

SRP contains a dedicated permission set for each integration flow and an additional permission set for administrators. More information is provided in the sections below.

Permission Sets and Custom Permissions for Integration Flows

For a user to run an integration flow, you must assign a custom permission specific to the flow that the user is running. This ensures that only the relevant user can run each flow and reduces the number of object and field-level permissions required. The custom permissions use the following naming convention: Create [Target Object] from [Source Object], for example, Create Sales Invoices or Credit Notes from Billing Events.

In addition, you must assign the Create Documents without an Accounting License custom permission to users running the PSA to Accounting flows. Users synchronizing regions, practices, groups, and projects to dimension records must also be assigned the Manage Supporting Records without an Accounting License custom permission.

Access to the custom permissions, Apex classes, fields, and Visualforce pages required for running the integration flow is included in the managed permission set for that flow. The label of each permission set starts with SRP - , followed by the name of the integration flow, for example, SRP - Billing Events to Sales Invoices or Credit Notes.

The permission sets also provide read access to the relevant field for the flow that SRP adds to other objects. For example, the SRP - Billing Events to Sales Invoices and Credit Notes permission set provides access to the Company field on the Region, Practices, and Group objects, as well as the Services Product field on the Project, Assignment, Expense Report, Milestone, and Timecard objects. These fields are not required to run an integration flow. Because the managed permission sets only provide read access, you must create a separate permission set to provide edit access for those fields.

Warning:

The SRP permission sets were designed to complement existing Accounting and PSA permission sets and permission set groups. This means that they do not provide access to Accounting and PSA objects. For example, if you only assign the SRP - Billing Events to Sales Invoices or Credit Notes permission set to a user, they cannot run the flow. For a full list of the minimum permissions required to run each flow, see Minimum Permissions Required to Run Integration Flows.

Note:

Due to a Salesforce limitation, you must manually provide access to the Expense Reimbursement Account on the Salesforce Contact object. This field is used in the Expense Reports to Payable Invoices or Credit Notes flow. For more information, see Contact Fields.

Permission Set for Administrators

The SRP - Administration permission set contains the permissions required to access the SRP Administration tab and Lightning components within it.

The following actions on the SRP Administration page require additional permissions.

Additional Permissions for the Components on the SRP Administration Page

Action	Required Permissions
Manage Scheduled Jobs	The relevant permission set for the integration flow that you want to schedule or delete. For example, to schedule the Create Journals from Miscellaneous Adjustments job, the SRP - Miscellaneous Adjustments to Journals permission set is required. [Optional] To view the process run records that are created after every execution of a job, you must have view access to the Process Run and Process Log objects.
Manage SRP Mappings	The FDN Core - Mapping permission set. This provides you with the ability to view the FDN Mappings component and to create, view, edit, and delete mappings using the component. View access for each source and target object included in a mapping process. For example, to create custom mappings for the Billing Event to Sales Invoice process, you must have access to the Billing Event, Billing Event Item, Sales Invoice, and Sales Invoice Line Item objects. View access for the fields on the source and target objects that you want to create custom mappings for. This is because, when adding a custom mapping, the component only displays fields that you have access to.

Minimum Permissions Required to Run Integration Flows

Depending on your requirements, you might want to create your own permission sets, instead of using the managed permission sets provided by default. For more information about the minimum permissions required to run each integration flow, see the related pages.