Configuring Pricing Console security in ClientSpace PEO
One of the common first steps for our PEO clients is to configure and use the pricing console in ClientSpace. While each PEO is unique in their processes, most have a designated workflow through which they would like Pricing to proceed. While this topic does not discuss pricing workflow, it provides a high-level overview of configuring pricing console security.
While security customization is driven by the individual business requirements of each of our clients, the method for configuring security in ClientSpace is standardized. Role security provides global administrators with the ability to configure dataform security down to the field level, specifying whether the User is allowed to View, Add, or Edit the document or field. The following table lists dataform security rights.
Dataform security rights
|
Description
|
View |
Users with only View rights are able to open a dataform and see the contents of any available fields but may not add a new or edit an existing document. Fields appear as read-only. Users with Add or Edit rights should also be given View rights. |
Add |
Users with only Add rights can add new dataforms of this type, but when the initial save occurs, they cannot edit the dataform they created. |
Edit |
Users with only Edit rights are not able to add new forms but can edit existing forms. |
To update Role security:
Update Role security to include appropriate rights to View/Add/Edit the forms using the following steps. Several security entities are used by the Pricing Console. The following table lists the most common.
Security entity
|
Description
|
Rights
|
CRM |
Creating and managing Organizations |
At least View rights |
biz_workflow_cm_create_batch |
Creating batches from the Client Master |
At least Add rights to create new batch |
PricingConsole |
Access to the pricing console |
At least View rights |
QuickEdit |
QuickEdit_subfields: For each field on the Quick Edit form there are available view/Add/Edit rights. These need to be set for each field (if editing of pricing rows is allowed). |
At least Add rights |
Dataform entities
|
If any of the dataforms are secured, the user needs to be in a role with appropriate rights for the dataform, such as Add or Edit rights.
|
At least View rights are also required for the related Dataform entities |
To administer role security:
|
1.
|
Go to System Admin > Security > Roles.
|
The Security Roles dashboard opens.
|
2.
|
You can filter roles Role Title, and Users that are associated with the role, or Entity Name of the associated Security Entities. |
|
3.
|
If a user needs to have access to a particular security entity, one of two things can be done: |
|
•
|
The user can be added to a role that already contains the required entity by filtering roles by desired entity. |
|
•
|
The security entity can be added to a role that user is already associated with by filtering roles. |
|
4.
|
Select a role and click Edit.
|
The Role form opens.
|
5.
|
In the Action Center, click Entities.
|
The Security Role Entities dashboard opens.
|
6.
|
Add the appropriate View, Add, Edit, Delete, and Admin rights for the role.
|
|
7.
|
To see if a user is already in a role with a specific entity, filter the Roles by user and Entity. |
|
8.
|
You can also use a wildcard when searching for roles. When setting search parameters, place a % symbol before your search string to make it a wildcard keyword search. Example: %Service Case |