Setting up Roles, Permission Sets and Profiles

  • Updated

Setting up Roles, Permission Sets and Profiles

You must read this information if you are using the non-Skuid enabled version of Q2 Originate.

Roles help you control access to records and Profiles help you determine record privileges. Role-based Application Configuration, if enabled, allows you to limit access and visibility of application content based on the profile. Let us assume you can view a record. Profiles determine what you can do with this record, that is, only view it or edit it too. Profiles control other system privileges as well. For further granularity of permissions, Permission sets can be used. Permission sets enable you to grant access among logical groupings of users. For example, you can provide View access on a report to every user and Edit access to a much smaller set of users. Cloud Lending leverages Salesforce.com's standard profiles and permission sets. Users can have only one profile, but they can have multiple permission sets. 

Remember, permission sets are for giving access and not for denying access.

You can define your organization's role hierarchy through the Setup, Manage Users, Roles option and assign users to roles.

User profiles configuration

Permissions and privileges on records are controlled through profiles in Q2 Originate. Based on your business requirements, you can provide permissions on the record types to the profiles that you plan to use.

To illustrate this, let us consider that the wizard has been configured to have the following underwriting steps for a loan application:

  1. Capturing application details 

  2. Capturing the parties involved

  3. Doing a credit pull or assessment

  4. Uploading documents

  5. Evaluating score

  6. Verifying necessary details and documents are captured in an application through checklists

An administrator can have access to all the above steps; not each profile should be given access to all the wizard steps though. So if a Loan Officer's work is to capture application details and collate necessary documents, then the wizard should just display steps 1 and 4 to the Loan Officer. A Credit Analyst should be given access to steps for pulling credit reports (Step 3). Similarly, for an Underwriter who will verify all details and check the eligibility of the customer, all the steps should be visible on the wizard. (steps 1 through 5). Showing the wizard steps as per the user profile is called profile driven flow of the Q2 Origination wizard. 

Now, if you want to give access to the application details page to the manager of users with the profile of Credit Analyst, then you can use permission set in such a situation.

Prerequisites

Before you proceed to create a profile and permission set driven process flows, ensure that the following prerequisites are met:

  • The user is a system administrator.

  • The user has knowledge of Salesforce profiles and how to set up and configure profiles.

  • The user has knowledge of Salesforce permission sets and how to set up and configure permission sets.

Steps

To configure a profile, say a Standard Platform User:

  1. Log in to your Salesforce account.

  2. Select Setup.

  3. Go to Administer > Manage Users > Profiles.

  4. Select Standard Platform User under Name.

  5. Go to Apps.

  6. Select Visualforce Page Access.

  7. Select Edit.

    You can view the list of enabled Visualforce pages along with the available pages. 

  8. Select the required page under Available Visualforce Pages. 

  9. Select Add. 

    Make sure you give permissions to the objects being accessed on the pages visible to that profile.

  10. Select Save.

    The required Visualforce pages appear in the page access list of the Standard Platform User. 

You must give Update rights to the Application object of Q2-Origination, with the Landing Sequence field having Read and Edit access. When giving access to Visualforce pages, you must give access to the necessary pages of the wizard steps that are accessible to that profile along with the following pages: 

  • genesis.errorPageGenesis (redirects to this page if some error occurs while processing the wizard steps)

  • genesis.wizardComposition (this is the wizard template used in your visualforce page)

  • genesis.wizardCSSPage (this defines the css which is applied to the wizard)

Permission set driven flows

Follow the same steps as defined for profile-driven flow, just with the difference of creating permission sets instead of profiles. The Manage Assignment button in each permission set page enables you to assign users as per profiles to these permission sets.

Profile and permission set driven flows 

These flows combine both permissions and profiles. Follow the steps as defined for both - profile-driven flow and permission sets driven flow. The wizard will show a union of pages given access in profile and permission sets assigned to the user, that is, if the user profile gives access to Visualforce pages A & B from a wizard, and permission sets assigned to the user give access to Visualforce pages C, D & E. Then, when the user selects on an application, the wizard will show all the 5 pages named A, B, C, D, and E.

User time zone configurations

To configure the time zone, follow the steps:

  1. Log in to your Salesforce account.

  2. Go to User > Settings > Language & Time Zone.

  3. Select the following fields as required:

In This Article