Have more questions? Submit a request

Installing Viewpath - Choosing the Security Level

Viewpath Support -

Article: Assigning access to the Viewpath Projects object in Salesforce

Installing Viewpath - Step 2.  Choose security level

The best practice is to choose “Grant access to all users” so all of your existing profiles are properly configured with the necessary security settings for the numerous elements of the Viewpath managed package. Selecting any other choice will be VERY time consuming later, as you will have to use the Salesforce admin user interface on many pages as you attempt to get it right!

After Viewpath is installed, you can optionally hide it from the profiles that won’t be using it right away. Just edit those profiles and hide the Viewpath Application & Tabs. Using this best practice, you will be done in a few short minutes and it will be easy to unhide Viewpath later if needed.

A second choice is to choose “Select security settings” then setup specific profiles with "Full Access" to Viewpath as shown below.  This works, however, if you ever have to configure some other profile to use Viewpath, it is very time consuming.  Select all possible profiles now, or use our recommendation of “Grant access to all users”.

 SF_SelectSecuritySettings.jpg

If you mistakenly chose to do as Admin only, the fastest recovery is to uninstall Viewpath and re-install choosing the “Grant access to all users”.  

Here are the steps to later enable an existing profile:

1. Create / Apps : Edit on Viewpath, check Visible on Assign to Profiles for the selected profile.

    Results:  Viewpath App in menu, however no tabs appear nor is it in Create New dropdown.

2. Manage Users / Profiles: click Edit on your custom profile.  

    • Under Custom Tab Settings;  set Viewpath Configuration = Default Off and Viewpath Projects = Default On.
    • Under ‘Custom Object Permission’ check Read, Create, Edit and Delete for both Viewpath_Configurations and Viewpath Projects.
    • Click Save.

     Results: Tabs appear and Create New dropdown has our data. You can see Viewpath Projects List.

     Note: Clicking on "New" from either Create New drop-down of the button "New" on Viewpath Projects tab results in this error: 

Insufficient Privileges
You do not have the level of access necessary to perform the operation you requested. Please contact the owner of the record or your administrator if access is necessary.

     Clicking on the tab for Viewpath Configuration gives the same error.

3. Manage Users / Profiles: click the link of your custom profile to view it.  

    • Under ‘Enabled Apex Class Access’ click Edit.
    •  Select ‘Viewpath_VP_Trigger_Validator’ and Add then click Save.
    • Under ‘Enabled Visualforce Page Access’ click Edit.
    •  Add the following:
      • Viewpath_VP_Configuration, Viewpath_VP_Launch_Application, Viewpath_VP_Project_Edit,
      • Viewpath_VP_Project_List, Viewpath_VP_Project_New, Viewpath_VP_SFAPI, 
      • Viewpath vp3API.
    • Click Save.

The Profile screen should look like this:

SF_ManageUserProfiles.jpg

Results:  User can now see the Viewpath UI, however upon creation of a Viewpath project the project list shows an ID instead of the name of the project. If this is the case, just click Go on list view to

4. Setup / Security Controls / Field Accessibility:

    • Select ‘Viewpath Project’, choose ‘View by Profiles’, select the profile in question.
    • Click each Field Access column to set as follows:

Fields

Field Access

Account

Editable

ChatterEnabled

Editable

ChatterGroupId

Hidden

Complete

Editable

Created By

Read-Only

Finish

Editable

Last Modified By

Read-Only

Opportunity

Editable

Owner

Editable

ProjectId

Editable

Project Name

Required

Start

Editable

    • Repeat the process for the tab ‘Viewpath_Configuration’ choosing the appropriate profiles then editing the fields as follows:

Fields

Field Access

Activated Date

Hidden

ApiAuthorized

Hidden

ApiKey

Hidden

ApiKey_Encrypted

Hidden

ApiUsername

Editable

ChatterEnabled

Hidden

Created By

Read-Only

Custom Object Label Name

Required

Last Modified By

Read-Only

Owner

Editable

Results: with the above in place the user should now be able to do everything in Salesforce for Viewpath.


Full screen shots of the above Field Access levels are shown below.


SF_FieldAccessLevels1.jpg

SF_FieldAccessLevels2.jpg

 

 

Have more questions? Submit a request

Comments 0

VIEWPATH

We have a passion for Customer Success - let us know if you have ideas!