| Excerpt | ||
|---|---|---|
| ||
Learn to work with Security Management |
...
| Main Information | |
|---|---|
Name Alternative Code Number of Active Users: A read-only value that provides the number of 'Active' users that use the specific Security Profile. | |
| Inherited Security Profiles | |
Security profiles may inherit configuration of existing security profiles to speed up the setup process. The configuration of inherited security profiles overrides that of newly created profiles. For example, if a security profile for team leaders does not allow access to module configuration, then the security profile for team members (inherited from the team leaders' security profile) will also not allow access to module configuration, even if access was allowed in the definition of the team members' profile. Therefore, inherited security profiles are useful when you wish to add additional restrictions to those of an existing profile. | |
| Menu Access | |
| Main Menu | Allow or deny access to main menu options by selecting them (left hand side checkbox) and click on Allow Access or Deny Access links respectively. |
| Shortcuts Menu | Allow or deny access to main menu options by selecting them (left hand side checkbox) and click on Allow Access or Deny Access links respectively. |
| Module Access | |
Define the features from each module which should be restricted for this security profile Modules can be filtered by application area by using the list filter. ' '. Select a module to load the security settings and select to grant or restrict its access by using 'Allow Access' and 'Deny Access'respectively.
| |
| Common Processes | 'Deny' or 'Allow' access to each module's Common Processes, which include:
|
| Additional Processes | 'Deny' or 'Allow' access to each module's Additional Processes, which include actions available in the Actions Menu of the 'Manage Module' page and Common Processes and actions of all Configuration Modules of the specific entity. |
| Custom Processes | 'Deny' or 'Allow' access to each module's Custom Processes, which include any processes that are not included as standard with the software release but have been explicitly implemented for an organisation. |
| Web API Methods | 'Deny' or 'Allow' access to WEB APIs available for each module. |
| Reports | 'Deny' or 'Allow' access to Reports available for each module. |
| Printouts | 'Deny' or 'Allow' access to Printouts available for each module. |
| Interfaces | 'Deny' or 'Allow' access to Interfaces available for each module, which are not included as standard with the software release (like Custom Processes). Such interfaces are available only if requested by an organisation and can be found under Pentaho Exports or Pentaho Imports of the Utilities module. |
| Dashboards | 'Deny' or 'Allow' access to the Dashboards available for each module. |
...
| Main Information | |
|---|---|
Entity: The entity that the Audit Trail will be applied on. The entities which can be monitored by the Audit Trail mechanism are listed in the Audit Trailed Entities. State: The state of the audit trail settings instance, which can be 'Active' or 'Inactive'. | |
| Monitored Fields | |
A list of all fields related to the selected entity that can be monitored, with the option to set them as active or not. Either activate or deactivate specific fields by using the respective checkbox or 'Activate All' and 'Deactivate All' by using respective links. |
...
| Panel | ||||
|---|---|---|---|---|
| ||||
Scenario 3 Company ZX would like to monitor every change of address. Solution Configuration Audit Trail Create an 'Active' Audit Trail record with the following settings:
|
| Note | ||
|---|---|---|
| ||
|
...