EM Client Configuration
Entity Management (EM) is configurable to meet the client organization needs. The table below lists each functional area within EM and indicates who can perform the configurations. Contact your Kingland Services team with any questions.
Functional Area/Feature | Client Configuration | Kingland Configuration | May require Kingland Support | Additional Comments |
|---|---|---|---|---|
Branding | | | | All Branding is Kingland Configurable. |
Data Model | | | | |
| | | | Configured by Global Administrator via language administration. |
| | | | |
| | | | |
Reference Data | | | | |
| | | | |
| | | | Configured by a Global Administrator. |
User Roles | | | | |
| | | | Configured by a Global Administrator. |
| | | | |
| | | | Some visibility permissions are Kingland Configurable; Kingland needs to make adjustments to these permissions, if desired. |
| | | | Some visibility permissions are Kingland Configurable; Kingland needs to make adjustments to these permissions, if desired. |
| | | | Configured by a Global Administrator. |
| | | | |
| | | | |
| | | | Client can add/update/remove partner roles via reference data by a Global Administrator. |
| | | | Client can add new roles with permissions via Role Management by a Global Administrator. |
Notifications | | | | |
| | | | |
| | | | Recipients are configured as part of the notification definition for each notification type. |
| | | | Configured by a Global Administrator via language administration. |
| | | | |
Workflow Configuration | | | | |
| | | | Configured by a Global Administrator. |
| | | | |
| | | | The rules that are run on each transition are configurable by a Global Administrator. However, rulesets have been set up to run rules on specific transitions in specific order, so Kingland should assist with rule configurations. |
| | | | These are typically the push back reasons and can be configured by a Global Administrator for each transition as desired. |
| | | | A Global Administrator can create an entirely new workflow definition. This is an area where Kingland would typically support client to ensure it is created correctly and can be utilized effectively. |
Validation Rules | | | | |
| | | | Configured by a Global Administrator. |
| | | | Configured by a Global Administrator. |
| | | | Configured by a Global Administrator. |
| | | | While some rules do allow the a Global Administrator to configure the logic, it is advised to involve Kingland to ensure the rule logic is updated properly. |
| | | | The system allows a Global Administrator to add new rules using an existing rule as a base. It is advised to involve Kingland to ensure the rule is created properly and added to the proper ruleset. Some rules require Kingland to add/update and cannot be added by client. |
Import & Export | | | | |
| | | | For example, if client organization wants to update the Primary Auditor field to My Client, the import/export file template will be updated by Kingland. |
| | | | A Global Administrator can assign permissions to various user roles to allow them to import or export. |
| | | | |
User Provisioning | | | | |
| | | | Client controls the fields they provide to EM via SCIM, but may need Kingland support. |
| | | | Configured by Global Administrator. |
Entity Search | | | | |
| | | | |
| | | | Configured by Global Administrator via language administration. |
| | | | |
Dashboard | | | | |
| | | | The global default dashboard is configured at a system level by Kingland, but each user can create their own saved dashboards. |
My Tasks | | | | |
| | | | The global default fields are configured at a system level by Kingland, but each user can create their own saved searches. |
Site Text | | | | Nearly all site text is configurable via language administration. |