To use the Frisbii application, a user must have a licence, as well as the permission sets linked to their licence type. This article deals solely with considerations relating to permission sets. For more information on the licences assignment, please refer to the following article Licence assignment.
In general, a user involved in a process linked to several objects must have permissions for each of these objects. In other words, packaged permission sets (delivered in the application) must be adapted to each business context so that the user has the rights required to read/create/modify/delete each of the objects involved in the process.
This principle applies to all objects in the process, including those impacted in a cascade, whether the user sees the changes at the record level or the consequences of their actions are “silent” to them.
Note: if you use profiles, you must modify these profiles by granting the same access permissions to objects as those in the permission sets associated with the license type (read-only, Sales, Finance, Admin). You must also verify that access to Frisbii fields on Salesforce objects (Opportunity, Account, Contact, Product) is also granted for the profile. Otherwise, users will not be able to use Frisbii in accordance with CRUD.
Therefore, for a Sales profile, please look at all the objects and fields concerned and their permission level (CRUD) and replicate this in the relevant profile.
Important: must be done before assigning permission sets.
Before assigning permission sets, it is essential to create a specific permission set to grant the following access:
1) To essential objects
If your version is later than 4.12:
As an administrator, you must generate a “Frisbii Objects” permission set from the Frisbii administration panel > System settings by clicking on the Create “Frisbii Objects” permission set button. This “Frisbii Objects” permission set must be assigned to all Frisbii administrators and users.
» Screenshot!
If your version is earlier than 4.12:
You must create a specific permission set to explicitly grant access to these objects and fields:
Opportunity Product: Discount Field
Invoice
Invoice Line
PDF Invoice
Periodic Distribution
Payment
These objects are in a master-detail relationship with the Account object, so we cannot include them in packaged permission sets. You must add them to a separate set.
Please note: other Frisbii objects may be essential to the proper functioning of the application in your business context. They are not listed above because they are not in a principal-detail relationship with the Account object (e.g., Corporate Name).
2) Other Frisbii items relevant to your needs.
Depending on your usage, you can add permissions to certain important objects.
Example: For Subledger Entries, here are all the objects involved:
3) to your custom fields, custom objects, etc.
For more information on setting up permission sets, we recommend the Salesforce Trailhead module Controlling Access to Objects.
Assign Frisbii permission sets
From version 4.12
Here are the permission sets to assign to control access to Frisbii fields and objects, depending on the role:
For Frisbii administrators: Frisbii Admin + Frisbii Objects
For all Frisbii users, regardless of their license type: Frisbii User + Frisbii Objects
Note: When updating Frisbii to a version later than 4.12, your administrator can assign the above Frisbii permission set and delete all old packaged permission sets (see below).
Prior to version 4.12
For versions prior to 4.12, here are the permission sets that must be assigned to users to control access to Frisbii fields and objects, depending on the license type:
For an Administrateur Frisbii licence:
Administrateur Frisbii (ADMIN)
Utilisateur Frisbii (FULL)
For a Finance licence:
Frisbii Finance (Fields)
Frisbii Finance (Objects)
Frisbii Finance - add-on Fall 20
For a Sales licence:
Frisbii Sales (Fields)
Frisbii Sales (Objects)
Frisbii Sales - add-on Fall 20
For a Read-only licence:
Collaborateur Frisbii (READ ONLY)
These permission sets are maintained by us and modified with each new version of the application in order to preserve rights to the latest features and/or fields in the application.
Note: these permission sets are obsolete and should no longer be assigned:
Frisbii FLS* READ-ONLY: Reading Frisbii fields (READ ONLY license)
Frisbii FLS* WRITE: Modifying Frisbii fields (FULL license)
Setup procedure
Explicit control of CRUD* rights on all Frisbii objects and fields is performed natively within the application. As a result, it is essential to assign permission sets to each user with a Frisbii license. Otherwise, certain processes will not work or will not trigger the application's automations (provided in the package or customized by you).
* Create/ Read/ Update/ Delete
Steps for assigning a permset
- From Setup, enter Permission in the Quick Find box.
- Click on Permission Sets.
- Click on the permission set you would like to attribute, for example Frisbii Admin for Linda.
- Click on Manage Assignments.
- Select the concerned users and click on Add Assignments.
- Select user and then click on Add Assignments to attribute the permission set to the user.
- Click on Done to finalize this step.
There you are!