The AdvoLogix Spend Management package has a built-in set of permissions and permission sets that can be assigned to your users to grant functioning capabilities within the application.
What permission sets are available?
AdvoLogix ships with multiple pre-defined permission sets that allow your users to perform those activities within the integration. Below is a list of custom permission sets provided within the Spend Management package.
The permission sets are shipped with the Spend Management application and are not editable. AdvoLogix advises users to generate a Permission Set Group and add the AdvoLogix shipped permission set within that permission set group to customize permissions for your users. You can further mute any custom permissions that AdvoLogix provides below to disable it for your users.
The advantage of using permission set groups is that you will automatically receive updates to any of the AdvoLogix shipped permission sets on future upgrades to the package without affecting any muted permissions by your administrator.
How do I control a user's ability to perform operations within Spend Management?
AdvoLogix ships with some custom permissions that can grant or restrict your users' ability to perform those activities within the application. Below is a list of custom permissions provided.
| Permission Name |
Description |
|---|---|
| Allow Invoice Upload | Assign this permission to users who can upload the invoices. |
Permission Set Groups offer useful functionality for muting permissions available through all the permission sets within the group. Administrators can:
- use and generate a permission set group for users with the AdvoLogix controller permission set included in the group and
- mute some permissions that AdvoLogix has, by default, enabled in the included permission set.
This offers the advantage of getting all the updates that AdvoLogix offers via the packaged permission set, and an administrator can still control which features you want to enable or disable for your users without worry.
Step 1: The following steps assume that there are no previous permission set groups set up in the organization.
- From Setup, enter
Permission Set Groupsin the Quick Find box. - Select Permission Set Groups.
- Select the New Permission Set Group button and create the new permission set group.
Step 2: Open the Permission Set Group detail page by selecting the API Name link.
Step 3: Select the Permission Sets in Group link under the Permission Sets section.
Step 4: Select the Add Permission Set button and choose which permission sets you want and click Save.
Did you know? You can add up to 100 permission sets to a permission set group.
Step 5: Select the permission sets that you want to add to the group and click Add.
Step 6: Select Done and click on the Back to: Permission Set Group link. When the update is complete the permission set group status will change to Updated. You may have to refresh your browser page.
[Optional] Step 7: Select the Muting Permission Set in Group link under the Permission Sets section.
[Optional] Step 8: Select New if no muting permission set exists on this screen.
[Optional] Step 9: Select Save.
Did you know? Only one muting permission set is allowed per group.
[Optional] Step 10: Click on the Muting Permission Set Label name link.
[Optional] Step 11: As an administrator, you have full control and can now enable/disable any permission within the AdvoLogix packaged permission set that is locked for editing. There are two different places to do this: Object Settings and Custom Permissions. From here, you can get as granule as you want with your users' permissions in Spend Management.
You are now ready to assign this permission set group to your users. Good job!
Muting only impacts members within the permission set group. Users outside of the group who are assigned to individual permission sets remain unaffected.
As a best practice, if a permission set group includes a permission set, then users requiring access from the permission set must be removed from the permission set and added back to the permission set group instead.