Depending on whether you manage users as an admin or manage AEB accounts as a tenant admin, the information on the roles differs slightly. Therefore, first select the use case that suits you best. (Am I a tenant admin?)
- Roles that you can assign to users as an admin
- Roles that you can assign for AEB accounts as a tenant admin
Roles that you can assign to users as an admin
You can view, create, and assign roles to users in the User administration.
You can use predefined general roles in any AEB product. Additional product-specific roles are also available for selected products.
Product-specific roles
The links will take you to an overview of the roles that are only available in the respective product.
- Trade Compliance Management: Product-specific roles
- Carrier Connect: Product-specific roles
Predefined general roles
Here you can find an overview of roles with the associated rights.
- You cannot change predefined roles. All predefined roles begin with “I_” to make it easy to distinguish them from the roles you define.
Name | Properties |
---|---|
I_BUSINESSFACADE |
This role allows you in a host system to call APIs, which are external function calls to the application. It may only be assigned to a system-based user, such as a WSM user. This user type may not have any other roles apart from I_BUSINESSFACADE.
WSM users: AEB initially creates a user for the WebServiceManager (WSM) with this role when you use an AEB product via your host system. Please note: Using this role to edit a user name or password can corrupt the connection to a host system. Contact the person from your company with an I_CLIENTADMIN role. Only persons with this role can create additional system-based users analogous to the initial WSM user. |
I_CLIENTADMIN |
Users with this role are client administrators. They can create users for the respective client and can assign and remove user roles.
If no one in your company has this role yet, AEB Support can create it for you. (How do I become an admin for managing logins to web applications?) |
I_CLIENTGROUPADMIN |
If client groups have been set up in the system, this role grants rights that include configuring the display settings, managing user tips, or viewing the change history for these client groups. |
I_DDACCESSRIGHT |
This role allows the configuration of data-related access rights. |
I_DEFAULTPREF |
A user with this role defines default settings (e.g. column definitions for overviews). These apply to all users of the current client, as long as individual users do not overwrite them with private settings. |
I_EVERYONE |
This role assigns the rights of a normal user. This role is included in every other predefined role. Every user to whom you have not assigned any specific rights has all the rights of this role. This can later be extended by the addition of other roles or rights or restricted by the removal of rights. |
I_READONLY |
A user with this role may view various data, but is no allowed to make any changes. Therefore, combine this role with the desired views from other roles which will allow the necessary access but prohibit changes. This role makes sense for an auditor, for example. |
- All other predefined roles with explanations can be found in the office under User administration – Roles.
Roles that you can assign for AEB accounts as a tenant admin
As a tenant admin, you can use the access management to assign roles for your AEB products and test systems to yourself and others.
- The tenant admin role is a top-level role. (How do I create an additional tenant admin?) All other roles are system-specific and created by assigning system access rights. (How do I assign system access rights?)
You can use basic roles in any AEB product. Additional product-specific roles are also available for selected products.
Product-specific roles
The links will take you to an overview of the roles that are only available in the respective product.
- Trade Compliance Management: Product-specific roles
- Carrier Connect: Product-specific roles
Basic roles
Here you can find an overview of basic roles with the associated rights.
Name | Rights |
---|---|
I_CLIENTADMIN |
With the I_CLIENTADMIN role, you can create AEB accounts for other users within the selected system and assign and revoke roles. |
I_CLIENTGROUPADMIN |
If client groups have been set up in the system, this role grants rights that include configuring the display settings, managing user tips, or viewing the change history for these client groups. |
I_DDACCESSRIGHT |
This role allows the configuration of data-related access rights. |
I_DEFAULTPREF |
A user with this role defines default settings (column definitions for overviews, etc.). These apply to all AEB accounts in the system unless overwritten with personalized settings. |
I_EVERYONE |
This role assigns the rights for normal system usage. This role is included in every other predefined role. Everyone to whom you have not assigned any specific rights has all the rights of this role. This can later be expanded by the addition of other roles or rights or restricted by the removal of rights. |
I_READONLY |
Someone with this role may view various datasets but is not allowed to make any changes. For this reason, this role should be combined with the appropriate views from other roles so that the user has access but is blocked from making changes. This role makes sense for an auditor, for example. |
I_BUSINESSFACADE |
This role allows you in a host system to call APIs, which are external function calls to the application. It may only be assigned to a system-based user, such as a WSM user. This user type may not have any other roles apart from I_BUSINESSFACADE.
WSM users: AEB initially creates a user for the WebServiceManager (WSM) with this role when you use an AEB product via your host system. Please note: Using this role to edit a user name or password can corrupt the connection to a host system. Contact the person from your company with an I_CLIENTADMIN role. Only persons with this role can create additional system-based users analogous to the initial WSM user. |
Comments
Please sign in to leave a comment.