Security Management - Configuration Requirements

Owned by p_demou (Deactivated)
Last updated: Jul 17, 2017 by Former user (Deleted)
2 min read

Back to Security Management Main Page 

Learn to set up Security Management related business processes and rules. 

 Mandatory Configuration: Links to manuals of Security Management configuration modules that are required for the module to work correctly.

 Optional Configuration: Links to manuals of Security Management configuration modules that offer additional functionality but are not required for the module to work correctly.

Mandatory Configuration

The following modules must be configured in order to use the System:

Module NameManualDescription
Security ProfilesManaging Security Profiles

Create Security Profiles to allow or deny access to features, for each one of the following areas:

  • Menu Options
  • Common Processes
  • Additional Processes
  • Custom Processes
  • Web API
  • Reports
  • Printouts
  • Interfaces
  • Dashboards

Optional Configuration

The following entities are available and can be configured under Security Management.  A working CRM.COM model can exist without them being configured.

Module NameManualDescription
Conditional Security Restrictions (CSR)
Setting up Conditional Security Restrictions (CSR)Define a set of conditions that restrict System features which can be applied on specific Organisational Units.
Privacy Levels Assignment Rules (PLAR)
Setting up Privacy Level Assignment Rules (PLARs)Define a set of conditions in order to automatically apply the Privacy Levels on entity records.
Automatic Collaboration Rules (ACR)
Setting up Automatic Collaboration Rules (ACR)Define a set of conditions in order to automatically assign Assignable Entity records to specific Units and Users.
Privacy Levels and Privacy Level GroupsSetting up Privacy Level Groups & Privacy Levels

Privacy Levels and Privacy Level Groups provide the ability to control the access to data and to define how it can be shared between Organisational Units. Organisational Units with access to records of a specific Privacy Level can access any record of that Level or lower. Each Privacy Level falls within a Group which is used to categorise the Privacy Levels.

Audit Trail 

Setting and Using Audit Trail

Define a set of entities and fields that should be monitored by the Audit Trail for changes. Only one 'Active' instance of Audit Trail Settings per Entity can be configured in the System.

Secret KeysManaging Secret KeysUsed to generate Secret Keys that are registered to specific URL endpoints. Secret Keys are used by Webhooks in order generate a code that will be used by Third Party Systems to authenticate received data. 

Related Areas

Filter by label

There are no items with the selected labels at this time.