Overview
The Admon is an important user in your development environment. The following article explains the Admon user's characteristics. It is important to keep in mind that this user is not available in production environments, so you need to define an end-user with the administration role, so he has access to the admin menu in production environments.
The default user
Bizagi creates by default the domain\admon user in every environment. When you create a new project from Bizagi Studio, the Admon user is already created as the only user.
This user cannot be deleted because Bizagi executes tasks and jobs on behalf of this user. See Jobs and tasks executed by the admon user. Additionally, this user is created by default with the Skip assignments on cases created by me property, so you can test easily a process when you created cases with him in the development or test environment.
With Admon user as the only user, the security is not active in the Work Portal of the development environment, so no credentials are requested to log in. When you create a new user the security is activated in the Work Portal and other users must log in with user credentials. See Log in to the Work Portal for further information.
If you do not change the authentication type, the Admon user has an Administrator Log In button. This log in does not require inputting the password because the Admon user is created with no password by default. The user just needs to click the Log In button:
|
We recommend setting a password to the Admon user and define an authentication type in early development stages. |
Accessing the first time with the Admon user in production environments
The first time that you deploy to the production environment, whether you use One Click or Advanced deployment, users are not considered in the deployment package because they are not considered metadata. So, the first time you access the Production environment, the admon user is able to log in without inputting credentials because is the only available user in the environment.
|
It is very important that after your first deployment to the production environment, you create a new user with either the position Administrator or a user that has permissions to access the admin menu. See security for Work Portal menus.
|
When the Bizagi authentication type is used In the production environment, only creating new users manually, by synchronization, or importing them, is when the authentication is activated. Also, the Administration Log in button is not displayed. See authentication types.
After you create a new user, the admon is automatically deactivated for security reasons. If you try to log in with the admon user, Bizagi displays a warning message.
Default Assignation User and Group
When no user meets the allocation conditions, Bizagi has default assignation users and groups. If there are no users in the default group, the task will be performed by the Administrator user (admon). As mentioned previously, the admon user is not available in the Production environment, therefore, you need to define your administrator users using the position Administrator.
If there are multiple users with the Administrator position, cases that are reassigned because there are no users in the default group, are assigned to all these users, so all of them will see the cases in their inbox. The first one to access the case is considered as the owner of the pending task.
Jobs and programmed tasks executed by the admon user
The domain\admon is the system user employed internally by Bizagi to perform automatic tasks such as timers, scheduled jobs, or any task that is executed by the system, like service tasks or bot tasks. Therefore, you may not delete this user since it is needed for this purpose. We recommend that you create a user with the permissions to manage the Work Portal rights to access administration options.