Master data and access rights for users are managed in different locations.
Adding permissions can cause costs!
(see Permissions subject to charges)
Where can I see and manage my user?
You can find the Scope user administration under Settings > Users and Groups.
Scope is distributed as a named user license model. Each of your employees receives a personal account. This ensures that there is a clear assignment of clerks to processes in Scope.
If your organization does not yet use Entra ID to log in to Scope (https://service.riege.com/en/knowledge/how-do-i-set-up-microsoft-365-login-for-scope), each user receives a login ID and password. This is no longer necessary when using SSO via Entra ID.
Each user has a name, an e-mail address and a telephone number in Scope. The user's data is printed on documents in Scope and used for sending e-mails. This data is not maintained in Scope, but in the connected directory service. Either the Scope Directory Service or your Entra ID Directory.
How are permissions managed in Scope?
While the user's master data comes from a directory, the permissions are managed in Scope. Scope has various concepts for this.
Role
In Scope, the role mainly controls which user has access to the “Users and groups” application. This is reserved for the “Administrator” role, all other users have the “User” role. The management of master data in Scope for customers or your own organization does not require the “Administrator” role, but is solved via “Permissions” and can be set very finely.
Main Branch
For administrative purposes, each user must be assigned a main branch. The main branch does not otherwise restrict user access.
Branches
If your organization has more than one branch in Scope, access to the branch can be set for the user. This allows the user to work flexibly in several branches or help out.
How can I change the selected branch?
Groups
Groups are a way of clearly organizing your user administration. Groups are a set of individual authorizations that you can assign to a user. Riege Software already provides you with groups and fully preconfigured users with your Scope installation, depending on your scope of use. The groups usually represent authorizations for the use of a module (user) or for the maintenance of master data (super user).
You manage the users in the upper part of the application (Settings > Users and Groups) and the groups in the lower part.
This allows you to quickly and easily configure the access rights for your users. New groups should be created with caution, as maintainability and clarity decrease as the number of groups increases.
Permissions
Adding permissions can cause costs!
(see Permissions subject to charges)
You can assign permissions to a user individually or combine permissions in groups. You should avoid assigning permissions directly to the user. In the long term, groups will make it much easier for you to maintain an overview. It is better to adjust the permissions in your groups.
Permissions are assigned to a group or user in the same way. The permissions in Scope are described as clearly as possible. You can restrict the display of permissions via a menu by category and even more precisely via a search field.
Permissions subject to charges
The following table lists all permissions that are used to determine whether a module is subject to a charge and is therefore charged automatically.
|
New Area |
Area |
Technical name |
Description |
|---|---|---|---|
|
Forwarding |
AE |
Air Export: AIR_EXPORT_APP(“airexport.LAUNCH_NEW“) |
Air: Application Export Shipments, Departure Control, Master Data Flight Schedule, Console flight schedule, TACT-Rates |
|
Forwarding |
AI |
Air Import: AIR_IMPORT_APP(“airimport.LAUNCH“) |
Air: Application Import Shipments |
|
Forwarding |
SE |
Sea Export: SEA_EXPORT_APP(“seaExport.core.LAUNCH_APP“) |
Ocean: Application Export Shipments |
|
Forwarding |
SI |
Sea Import: SEA_IMPORT_APP(“seaimport.LAUNCH“) |
Ocean: Application Import Shipments |
|
n/a |
Handling |
Scope Handling: HANDLING_AGENT_ORDER_APP("warehouse.HA_ORDER_LAUNCH“) |
Handling: Application Shipments |
|
n/a |
Tour |
Truck |
Forwarding: Application Tours / Truck Disposition |
|
Customs |
Customs DE |
ATLAS Import: CUSTOMS_DE_EINFUHR_APP("customs-de.einfuhr.LAUNCH_EINFUHR_APP“) |
ATLAS Application Einfuhr |
|
Customs |
Customs DE |
ATLAS SumA: CUSTOMS_DE_SUMA_APP("customs-de.suma.LAUNCH_SUMA_APP“) |
ATLAS Application Summarische Anmeldung |
|
Customs |
Customs DE |
AES Export: CUSTOMS_DE_AES_APP("customs-de.aes.LAUNCH_AES“) |
ATLAS Application Ausfuhr |
|
Customs |
Customs DE |
ATLAS NCTS: CUSTOMS_DE_NCTS_APP("customs-de.ncts.LAUNCH_NCTS_APP“) |
ATLAS Application NCTS |
|
Customs |
Customs DE |
ATLAS EAS: CUSTOMS_DE_EAS_APP("customs-de.eas.LAUNCH_EAS_APP") |
ATLAS Application ESumA |
|
Customs |
Customs DE |
ATLAS EGZ: CUSTOMS_DE_EGZ_APP("customs-de.egz.LAUNCH_EGZ_APP") |
ATLAS Application EGZ |
|
Customs |
Customs DE |
ATLAS Zolllager: CUSTOMS_DE_ZOLLLAGER_APP("customs-de.zolllager.LAUNCH_ZOLLLAGER_APP") |
ATLAS Application Zolllager |
|
Customs |
Customs DE |
ATLAS AV/UV: CUSTOMS_DE_AVUV_APP("customs-de.avuv.LAUNCH_AVUV_APP") |
ATLAS Application AV/UV |
|
Customs |
Customs US |
US AES: US_CUSTOMS_APP("customs-us.LAUNCH") |
US Customs: Application US Customs |
|
Customs |
Customs NL |
Sagitta Import: NL_CUSTOMS_SAGITTA_IMPORT_APP("customs-nl.LAUNCH_SAGITTA_IM") |
NL Customs: Application Sagitta IM |
|
Customs |
Customs NL |
Sagitta Export: NL_CUSTOMS_SAGITTA_EXPORT_APP("customs-nl.LAUNCH_SAGITTA_EX") |
NL Customs: Application Sagitta EX |
|
Customs |
Customs NL |
Sagitta NCTS: NL_CUSTOMS_NCTS_APP("customs-nl.LAUNCH_NL_NCTS") |
NL Customs: Application NCTS |
|
Customs |
Customs NL |
NL Customs PD: NL_CUSTOMS_PD_APP("customs-nl.LAUNCH_NL_PD") |
NL Customs: Application CLIENT PD |
|
Customs |
Customs NL |
NL Customs VWA: NL_CUSTOMS_VWA_APP("customs-nl.LAUNCH_NL_VWA") |
NL Customs: Application CLIENT VWA |
|
Customs |
Customs NL |
NL Customs C-Sum: NL_CUSTOMS_CSUM_INVENTORY_APP("customs-nl.LAUNCH_CSUM_INVENTORY") |
NL Customs: Application C-Sum Inventory |
|
Customs |
Customs CH |
Edec Import: CH_CUSTOMS_EDEC_IMPORT_APP("chcustoms.import.LAUNCH_EDEC_IMPORT_APP") |
EDec: Application EDec Import |
|
Customs |
Customs CH |
Edec Export: CH_CUSTOMS_EDEC_EXPORT_APP("chcustoms.export.LAUNCH_EDEC_EXPORT_APP") |
EDec: Application EDec Export |
|
Customs |
Customs CH |
Edec Transit: CH_CUSTOMS_NCTS_EXPORT_APP("chcustoms.ncts.LAUNCH_NCTS_EXPORT_APP") |
EDec: Application NCTS Export |
|
Customs |
Customs CH |
CH_CUSTOMS_NCTS_IMPORT_APP("chcustoms.ncts.LAUNCH_NCTS_IMPORT_APP") |
EDec: Application NCTS Import |
|
n/a |
Dakosy |
Dakosy -dakosy.core.LAUNCH_DAKOSY_APP |
Ocean: Application Dakosy |
|
n/a |
BHT |
BH: bht.LAUNCH_BHT_APP |
Ocean: Application dbh |
|
Customs |
Customs US |
US ISF: US_CUSTOMS_ISF_APP("customs-us.LAUNCH_ISF") |
US Customs: Application ISF |
|
Customs |
Customs US |
US AMS: US_CUSTOMS_AMS_APP("customs-us.LAUNCH_AMS") |
US Customs: Application AMS |
You can find more answers on the topic of “Users and groups” in the FAQ article:
https://service.riege.com/en/knowledge/faq-for-users-and-groups