Salesforce Setup
User Licensing, Access Control, Permission Sets, and Community Partner
Last updated
User Licensing, Access Control, Permission Sets, and Community Partner
Last updated
Salesforce setup begins when a user installs Valorx Managed Package from . Salesforce Admins would be able to install it in Sandbox or Production Orgs.
Once Valorx package is installed, Salesforce Admins can proceed to the below setup steps: 1. : Production level access. 2. : Configures access at different levels. 3. : User-level functionality that gives access to various tools and functions. 4. : Ensure profiles group user have "API Enabled" permission for Salesforce access.
Salesforce Admins should be able to provide licenses to the users who require Valorx access. On the setup → installed packages, find the Valorx package. Against the Valorx package, click on Manage Licenses.
Package Manager window will open where you will find an overview of Valorx licenses along with a list of users who currently possess the license. Additionally, you will be provided with options to either add or remove user license assignments.
The first section "Enable for Platform Integrations" will have the information regarding the below
Package Name: This refers to the name of the package that is being managed within the Salesforce platform. It serves as a unique identifier for the particular package.
Status: The "Status" represents the current condition or state of the package. It could indicate whether it is active, inactive, installed, uninstalled, or any other relevant status.
Expiration Date: The "Expiration Date" is the date when the current license or subscription for the package is set to expire. After this date, the access or usage of the package might be restricted, or a renewal might be required.
Enable for Platform Integrations: This is a feature or setting that allows the software package or integration to interact and integrate with other platforms, systems, or applications within the Salesforce. Enabling this option ensures that the package can seamlessly work with other integrated components.
Publisher: The "Publisher" refers to the organization or entity that developed and released the software package or integration. It identifies the source or origin of the package.
Allowed Licenses: "Allowed Licenses" denotes the total number of user licenses that the organization is permitted to assign for this particular package. It signifies the maximum number of users who can use this package.
Used Licenses: "Used Licenses" indicates the current number of user licenses that have been assigned and are actively being used by users for the specific package.
In the second section of "Licensed Users", you have the option to add or remove users. To add users, simply click on "Add User." This action will display a list of available users from which you can make your selection. After choosing the desired users, click "Add," and their information will be displayed under the "Selected Users" section.
In this section, you can discover details about the permitted number of licenses and the current allocation status. Access to Valorx Fusion is granted exclusively to users who have been assigned a license.
As a part of our managed package, we ship a field on the User object called Valorx User Access (see image below). This can control user’s access level using this picklist.
There are three different access levels available:
Design Studio: Design or any changes to the app can be made with the permission level.
Runtime + Express Mode: Run the Valorx apps along with the ability to create apps in Express mode.
Runtime Only: Run the app but no changes can be made.
Valorx ships with three standard permission sets. Admin, Design Studio, and Runtime + Express Mode.
Admin: Admin permission set controls Valorx User Access field on the User object. Valorx User Access controls user’s access levels in the Valorx client. Admin permission set does not include Runtime or Design Studio permissions.
Design Studio: Assign Design Studio permission set to those who need to design and promote apps. This permission set includes everything included in Runtime + Express Mode permission set.
Runtime + Express Mode: These permission sets provide different levels of access to Valorx package components. Most end users would require Runtime + Express Mode permission set.
Before proceeding, please note that if you prefer not to apply these changes at the Profile Level, you may opt to make these adjustments at the Permission Set Level instead.
Please make sure that the profile of the user(s) who are going to use the Valorx Fusion has the permission to access the Salesforce data via APIs. This can be ensured by checking the “API Enabled” setting listed under Salesforce profile settings. The setting should be turned on for the Users to work on Salesforce data through Valorx Fusion product.
Please refer to the step-by-step instructions and the image below to see how to enable the "API Enabled" permission:
Log in to Salesforce as an Admin. Then, navigate to “Setup”.
In the Setup menu, go to “Administration”. Under the “Administration” section, select “Users”.
Click on "Profiles" and select the profile of the user (in this case Standard user clone).
Scroll to the System and click on "System Permissions".
Click on the "Edit" button.
Search for "API Enabled". Enable or check the “API Enabled” option.
Click “Save”.
A community user is an individual with authorized entry to a designated community within a Salesforce organization. In Salesforce, the access and permissions for community users can be managed using diverse settings and configurations. Companies have the flexibility to tailor what community users can see, modify, and engage with, thereby ensuring proper protection of sensitive information and data.
Log in to Salesforce and go to Setup. Search for the "Permission Sets" and select it from the list.
Look for "Valorx ExcelUI Admin", "Valorx ExcelUI Design Studio" or "Valorx ExcelUI Runtime + Express Mode" from the list of Permission Sets and click on "Clone" depending on which permission set needs to be assigned.
Provide a descriptive logical name and API name under "Enter Permission set information" for the cloned permission set, then click "Save."
Now open the permission set that you have created by cloning.
Click on "Object Settings" under Apps from the Permission Set Overview window.
Click on the "App" object and then click on the "Edit" button.
Uncheck the box next to "View All" in the Object Permissions section and click on "Save".
Open the "Access Control" object and repeat steps 6 and 7 to remove the "View All" access.
Go back to the Object Settings and look for any other objects with the "View All" permission.
For each object found with this permission, open it and follow Step 6 and 7 to remove the "View All" access.
In Salesforce setup, navigate to Users > Users and open the specific partner community user's profile.
Under "Permission Sets," click "Edit Permission Set Assignment."
Assign the desired cloned permission set and click Save.
Start by opening the App Launcher and search for “Valorx” in the search box.
Select the Valorx App and pick the app you want to share from the “App Name” list.
Navigate to the "Notes and Attachments" section and click on View All to see all the existing files.
Choose the first file click on down arrow and click on “Share” from the menu at the top right corner.
A Share window will pop up, where you can expand the “Who Can Access” section.
Turn on "Customer Access" for the App Name and click on Done.
Note: Repeat Steps 4-6 for each file in the “Notes and Attachments” section.
Access Salesforce "Setup" and look for "Sharing Settings"; click on it to open.
Under "Default Sharing Settings," click on Edit.
Find the "App" object and change its "Default External Access" to "Public Read Only" from the drop-down menu.
Save the changes made to the "Default Sharing Settings."
Valorx also provides an option to assign the licenses through Valorx Admin. Click to know how to provide the Licenses through Valorx Admins.
To provide access to an additional app, follow steps 2-7 under the "" section mentioned above.
