Anchor | ||||
---|---|---|---|---|
|
Excerpt | ||
---|---|---|
| ||
Learn to work with Security Management |
...
Security management is the center from which an organization controls access to system modules and features and ensures the implementation of its business rules.
Note |
---|
Access to customer data is handled through Network Management. |
...
- Sections on the Left menu
- 'New' subscriptions button in the Data Entry page
- Accounts receivable report
- Option to create WEB APIs.
Security profile fields
...
Main Information | |
---|---|
Name Alternative Code Number of Active Users that use the specific profile (read-only). | |
Inherited Security Profiles | |
Security profiles can inherit existing configurations to speed up the setup process. Inherited profiles are ideal for setting additional restrictions, as their configuration overrides those of a new profile. E.g.: The security profile of management team leaders restricts access to module configuration. If the finance team leaders inherit their profile from the management, access to module configuration will be restricted despite being granted in the finance team leaders profile definition. | |
Menu Access Select menu options (left-hand side checkbox) and use 'Allow' or 'Deny' access | |
Main Menu: If access to a 'Parent' menu option is denied (e.g., Billing > Additive Discounts), the restriction is also applied the 'Child' menu options (e.g., Billing > Additive Discounts > Manage Ad Hoc Discounts). The child menu option will not be available. Shortcuts Menu | |
Module Access | |
Define the features from each module that should be restricted to each security profile. |
...
- Control the modification of shared records (e.g., create Group Collaboration Profiles to share data between the London and Manchester group, but only let Manchester users modify records created by London users).
- Control the visibility of private records (e.g., setup Conditional Security Restrictions and restrict the visibility of high privacy contact addresses and telephones to call center agents).
- Assign new records to particular users or departments according to the privacy level of each record (e.g., setup Automatic Collaboration Rules and assign new high privacy level activities to the manager).
Privacy level and privacy level group fields
...
Privacy Level Assignment Rules (PLARs) are used to automatically apply privacy levels when creating or modifying a record, based on a set of conditions set in the PLAR. PLARs can also be applied to Web API calls.
Privacy level assignment rule fields
...
Note |
---|
The automatic assignment of ACRS can be based on the geographical area of the contact or as defined by the setup rule. |
Automatic collaboration rule fields
...
Restrictions | |||
---|---|---|---|
Type | Visible Entity will be visible | Editable | Mandatory Entity cannot be saved if not defined |
Fields | |||
Processes | |||
Printouts |
Conditional security restriction fields
...
Refer to Viewing Audit Trail for information on how audit trail settings are applied and displayed in updated records.
Audit trail fields
...
Secret keys are registered to specific URL endpoints and are used by Webhooks to generate a code that will be used by third-party systems to authenticate received data.
Secret keys fields
...
Security profiles are assigned to users through the manage users Data Entry page. The security profile is created and added to a user to define their security level.
Anchor | ||||
---|---|---|---|---|
|
...
- Navigate to the Data Entry page of an audit trail enabled record.
- Click on the AUDIT LOG button located at the top-right corner of the page.
The Audit Log modal will open providing information on the modified fields and their changes.
Anchor | ||||
---|---|---|---|---|
|
...
Panel | ||||
---|---|---|---|---|
| ||||
Scenario 3 Company ZX wants to monitor all address changes. Solution Configuration Audit Trail Create an 'Active' audit trail record with the following settings:
|
Note | ||
---|---|---|
| ||
|
...