...
Configure a SCIM Role Group in LogiSense Billing (Optional)
When people Okta groups are assigned to the Application in Okta pushed to LogiSense Billing they will be pushed ( created ) in LogiSense Billing as users. If the person in Okta has no group set on it then the user will be created using the role group setup as the ‘SCIM Default’ in LogiSense Billing.
...
The preconfigured SCIM Default role group as SCIM Role Groups. The permissions that the newly created SCIM Role group have by default will depend on what role group in LogiSense Billing is configured as the ‘SCIM Default’ role group.
...
By default the SCIM Default role group set in LogiSense Billing is the ‘ReadOnly’ role group (shown in the image above). This is a core role group that grants the user read only access to all menus and screens but no rights to modify anything.
If you wish to grant Okta users without groups different permissions in LogiSense billing (e.g. more limited access such as read only access to the home screen) you can To define different default role group permissions for the role groups created when groups are pushed from Okta you can simply create a new role group in LogiSense Billing with the SCIM Default option set. The new role group will then be the new default role group for all Okta people pushed to LogiSense Billing going forward.Groups setup in Okta and pushed will create SCIM role groups in LogiSense Billing, so there is no need to setup additional role groups in LogiSense Billing. Instructions on how to push groups from Okta to LogiSense Billing are covered below in this guide. the desired permissions and enable the ‘SCIM Default’ setting on the new group. For instance, you may wish the default permissions for groups pushed from Okta to be limited to read-only access to the home and account menus only.
After the Okta groups are pushed to LogiSense Billing and the SCIM Role groups are automatically created you can then access LogiSense Billing and modify the particular SCIM Role Group’s permissions as needed (i.e. grant additional permissions beyond what the SCIM Default role group has provided).
Configure Application Permissions in Okta
...
On the Application page click on Assignments
On the Assignments page click the Assign button
You will be presented with two options, Assign to People and Assign to Groups. Select Assign People
Click Assign next to the person
On the Assign pop-up that appears leave the values as is and select Save and Go Back
Assign additional people as needed, when finished click the Done button
The users you added should be listed in LogiSense Billing
You can verify that the user/group was created in LogiSense Billing on the Setup / Users & Accounts / Users screen and Role Groups screen
If the person in Okta has no group set on it then the user will be created using the ReadOnly role group. To grant a user additional permissions they will need to first be assigned to a group in Okta and then their group must be pushed to LogiSense Billing. See the steps below for instructions.
...
On the LogiSense Application page in the Okta Portal click on Push Groups
Click the Push Groups button and then select an option to find a group
After an Okta group has been selected click Save
The Role Group will now be created in LogiSense Billing
In the Okta portal if you assign people setup under the LogiSense Application to a group that has been pushed to LogiSense Billing then the corresponding user’s role in LogiSense Billing will be updated to show a SCIM role (i.e. the user will have the permissions setup for the role groups that are attached to that role)
Repeat the steps above to push more groups to LogiSense Billing.
Note: the auto-generated ‘Name’ values as shown in the image above can be changed to something more user friendly (i.e. Sales, Accounting, Support, etc.)You can now configure the permissions for the role groups that you have pushed to LogiSense Billing in order to define what Okta users in those groups can do in LogiSense Billing
...
Configure a SCIM Role Group in LogiSense Billing (Optional)
When users Azure groups are provisioned to the Application in Azure AD pushed to LogiSense Billing they will be pushed ( created ) in LogiSense Billing as users. If the user in Azure has no group set on it then the user will be created using the role group setup as the ‘SCIM Default’ in LogiSense Billing.
...
The preconfigured SCIM Default role group as SCIM Role Groups. The permissions that the newly created SCIM Role group have by default will depend on what role group in LogiSense Billing is configured as the ‘SCIM Default’ role group.
...
By default the SCIM Default role group set in LogiSense Billing is the ‘ReadOnly’ role group (shown in the image above). This is a core role group that grants the user read only access to all menus and screens but no rights to modify anything.
If you wish to grant Azure users without groups different permissions in LogiSense billing (e.g. more limited access such as read only access to the home screen) you can To define different default role group permissions for the role groups created when groups are pushed from Azure you can simply create a new role group in LogiSense Billing with the SCIM Default option set. The new role group will then be the new default role group for all Azure users pushed to LogiSense Billing going forward.Groups setup in Azure AD and pushed will create SCIM role groups in LogiSense Billing, so there is no need to setup additional role groups in LogiSense Billing. Instructions on how to push groups from Azure to LogiSense Billing are covered below in this guidethe desired permissions and enable the ‘SCIM Default’ setting on the new group. For instance, you may wish the default permissions for groups pushed from Azure to be limited to read-only access to the home and account menus only.
After the Azure groups are pushed to LogiSense Billing and the SCIM Role groups are automatically created you can then access LogiSense Billing and modify the particular SCIM Role Group’s permissions as needed (i.e. grant additional permissions beyond what the SCIM Default role group has provided).
Configure SCIM Provisioning in Azure AD
...