Two aspects of Administrator access
In this chapter we'll explain the two aspects of Administrator privileges in CurrencyXchanger. Just like every other User, Admin needs to be logged into the CurrencyXchanger to be able to access modules. There are several levels of Admin access, and each individual Administrator can be assigned wth more or less privileges than other, which we will cover later on. First let's get familiar with types of access and the Modules available to Admins.
If you had a chance to get an overview of User Manual for Tellers, you'll be able to remember how some Modules can be completely accessible to viewing and editing, and some limited to viewing only. It's the same with Administrator access. We can say that there are two aspects to Admin's access:
- The visibility scope, and what Admin is able to View in Module
- The profile level, or the scope in which Admin is able to Modify certain Module
Modules Admins can View
Asside from all Modules Tellers as regullar users can view, Admins have additional access to:
- Admnistration
- Accounting
- Configuration
- Translation
- Debug
The visbility of certain Modules and Data within can be set to three levels
- normal scope, in which Admin has access to all data on a branch level
- enterprise scope, in which Admin has access to all data on enterprise level (all data related to the same company, ex. SBB)
- whole view, in which Admin has access to all data
Types of Admin levels
There are three main Admin levels with different types of access:
- Master Admin: this access is limited to Ergonomics designated personnel only, and Master Admin has the complete access to all Modules, including development.
- SBB Admin: this administrator level can has the largest scope of access in enterprise structure, and the primary purpose of this manual is to explain which Modules can be Viewed and Modified specifically with this access level.
- Auditor (IKS profile): This access level is assigned to AML Officers with a sole purpose to allow them complete insight into AML complience, specifically reviewing all transactions that were marked by any AML rule and are listed in Journal Audit Module. Auditors with their logins can, unlike tellers, access Journal Audit submodule. They can view complete data for each transaction listed there and after reviewing all entered information, they are able to perform only two actions: mark the transaction with YES or NO to clear it. Auditor has no access to other Admin Modules.