Team and roles

Tracker users are created in the Team («Команда») section: click the Admin panel («Админ-панель») icon in the top right corner and choose Team. The section is visible to the owner and the admin.

Roles

There are six roles, and the list is fixed. The role is chosen when the user is created and can later be changed in the edit window.

The first owner is created in the first-run wizard.

What each role can do

Notes to the table:

• The team lead, buyer and designer also see campaigns that were shared with them — view-only, see Campaign access and “Share”.
• A buyer sees the offers and landing pages given to them: their own copies and shared records opened with the Access («Доступ») button — see Offers and Landing pages.
• The buyer and the designer choose domains for campaigns from the groups opened to them — see Domain groups and media buyer access.
• The PHP with network access («PHP с доступом в сеть») checkbox of an offer and the PHP code of such offers are changed by the owner, the admin and the designer — see PHP in hosted pages and network access.
• The license key, backups, updates and the IP2Proxy database are available only to the installation owner.

The team lead, buyer, designer and financier roles can be narrowed with the Permissions («Права») button in the user's row: close sections, leave view-only access, limit campaign groups and hide report metrics — see User permissions: sections, campaign groups and report fields.

Creating a user

1. Open Admin panel → Team («Админ-панель → Команда»).
2. Click + User («+ Пользователь»). On a phone, use the + button in the bottom right corner of the screen.
3. Fill in the fields of the “Create user” («Создать пользователя») window.
4. Click Create («Создать»).

The user appears in the table with the Login, Role, Team lead («Тимлид») and Actions («Действия») columns. Your own row is marked “(you)” («(вы)»), and the row of the installation owner with the words “installation owner” («владелец установки»). The tracker does not send the login and password to the employee — pass them on yourself. The employee can change the password in the My profile («Мой профиль») window — see My profile: password and time zone.

The selected team lead sees the employee's campaigns and statistics together with their own — see Team lead and their media buyers.

Editing a user and resetting a password

1. In the user's row, click Edit («Изменить»).
2. In the “User …” («Пользователь …») window, change the Login, Role or Team lead (whose data is merged).
3. To reset the password, enter a new one in the New password (leave empty to keep) («Новый пароль (пусто — не менять)») field. The password requirements are the same as on creation.
4. Click Save («Сохранить»).

Your own password cannot be changed in this window: instead of the field there is the line “Your own password is changed in ‘My profile’, with the current password.” («Свой пароль меняется в «Мой профиль», с текущим паролем.») The procedure is on the My profile: password and time zone page.

The row of the installation owner has no Edit button: their login, role and password are not changed in the Team section.

What happens after saving:

• Changing the login, role, team lead or password ends all sessions of this user. They need to log in again; after a login change, with the new login.
• If you change your own account, your current session continues, and your other sessions end.
• If the new role is neither Owner nor Admin, the API tokens created by the user are deleted.
• When the role changes to anything other than Buyer and Designer, the assignment to a team lead is removed.

You can see the panel through an employee's eyes with the Log in as ↗ («Войти как ↗») button — see Log in as a user.

Deleting a user

1. In the user's row, click ✕.
2. Confirm the prompt “Delete user …?” («Удалить пользователя …?»).

The user immediately loses access to the panel. Their campaigns, offers, landing pages and shared funnels are not deleted:

• if the user had a team lead, they pass to the team lead;
• if there was no team lead, they pass to whoever deleted the user.

API tokens created by the deleted user are deleted. What happens to the employees of a deleted team lead is described on the Team lead and their media buyers page.

Owner protection

• Only an owner can assign the Owner role.
• Only an owner can change an owner's account, reset their password, log in as them and delete them. An admin does not see the Edit, Log in as ↗ and ✕ buttons in owners' rows.
• Nobody changes or deletes the account of the installation owner in the Team section, including other owners and the installation owner themselves: its row has no Edit and ✕ buttons.
• Nobody sets their own password in the Team section: it is changed in the My profile window and only with the current password.
• If an owner has forgotten their password and there is nobody to reset it in the panel, root sets a new password on the server with the sudo micatorctl owner-password command — see New owner password. For the installation owner, a forgotten password can be set only with this command.
• The team always keeps at least one owner. The last owner cannot be deleted, and their role cannot be changed.
• You cannot delete yourself: your own row has no ✕ button.

There can be several owners.

Installation owner

The installation owner is the user with the Owner role and the login that was set for the owner when the tracker was installed. Only under this account can you enter the license key and work with backups, the backup encryption key, updates and the IP2Proxy database. Other owners do not get these rights — see How the license works.

This account is protected from changes in the Team section. Neither another owner nor the installation owner can do any of the following here:

• change its login or role;
• set it a new password;
• delete it.

In the table, its row is marked with the words “installation owner”, and hovering over them shows the hint “Backups, updates and the license are tied to this account. Its password is changed in ‘My profile’.” («К этой учётной записи привязаны резервные копии, обновления и лицензия. Её пароль меняется в «Мой профиль».») Nobody has the Edit and ✕ buttons in this row. Other owners still have the Log in as ↗ button — see What is unavailable in this mode. To such a request via the API, the tracker responds: “The installation owner's account is not changed here: backups, updates and the license are tied to it. The password is changed in ‘My profile’.” («Учётная запись владельца установки здесь не меняется: к ней привязаны резервные копии, обновления и лицензия. Пароль меняется в «Мой профиль».»)

The installation owner's password can be changed in two ways:

• in the My profile window, with the current password — see Changing the password;
• with the sudo micatorctl owner-password command on the server, if the password is forgotten — see New owner password.

Error messages

The error text is shown as a red line above the user table. On an error, the create or edit window stays open and covers this line: close the window to read the text. When reopened, the “Create user” window keeps the entered values; in the edit window, unsaved changes are reset.

Email and password (min. 8 characters) are required («email и пароль (мин. 8 символов) обязательны»)

On creation, the Login is empty or the password is shorter than 8 characters. Fill in both fields.

Password must be at least 8 characters («пароль — минимум 8 символов»)

The new password in the edit window is shorter than 8 characters. The login, role and team lead from this window have already been saved by this moment. Open the window again and enter a password of at least 8 characters.

cannot hash password

The password is longer than 72 bytes. Set a shorter password.

A user with this email already exists («пользователь с таким email уже есть»)

The login is already taken. The logins Buyer7 and buyer7 are considered the same. Choose another login. In the edit window, the same message reads: “A user with this login already exists” («пользователь с таким логином уже есть»).

Login cannot be empty («Логин не может быть пустым»)

The Login field was cleared in the edit window. Restore the login or enter a new one.

Cannot delete or demote the last owner («нельзя удалить/разжаловать последнего владельца»)

The only owner is changing their own role. First assign the Owner role to another user.

Only an owner can manage owner accounts («управлять учётками владельца может только владелец»)

An admin is changing or deleting an owner's account or resetting their password. These actions are performed by an owner.

The installation owner's account is not changed here: backups, updates and the license are tied to it. The password is changed in “My profile”. («Учётная запись владельца установки здесь не меняется: к ней привязаны резервные копии, обновления и лицензия. Пароль меняется в «Мой профиль».»)

The request changes the login, role or password of the installation owner or deletes their account. This is closed to everyone: their row in the Team section has no Edit and ✕ buttons, and a request via the API gets this response. The installation owner changes the password themselves in the My profile window.

Your own password is changed in “My profile”, with the current password («Свой пароль меняется в «Мой профиль», с текущим паролем»)

The request sets a new password for your own account through the Team section. The edit window has no such field; the message comes in response to a request via the Admin API. Change the password in the My profile window.

Errors of API requests are described on the Admin API: users page.