The Admin Account View

The Admin Account view displays the general account settings and usage limits, and lists the account admins and their details. The details in the General and Limits sections appear for informative purposes, and can only be changed by Applitools account managers. Managing the team usage limits and the users that appear in the Admins section is the responsibility of the company's account administrator.

Page Layout

You can access the Account view by clicking the Account tile on the Admin panel.

The Account view groups the details of the account in three panels: General, Limits and Admins. Each of these panels is described in the sections that follow.

General Account Details

The information in this section is informative and cannot be changed by the user.

Name
The name associated with the account. This is typically the name of the organization or company, or a department within a company.

ID
An internal identifier of the account. You may be asked for the ID when receiving support from Applitools.

Plan
The type of account. Specific information on the types of plan and their feature sets is available on the Applitools website's pricing page. For more information see Applitools Pricing. Upgrade button
Click this button to request a change in plan. See Upgrading an account below.

Plan started
The date that the plan started.

Plan expires
The date that the plan ends. You must renew your plan on or before this date to continue using the Applitools service.

Upgrading an Account

An account admin can request to upgrade an account in order to acquire additional product features and usage.

To upgrade an Applitools Eyes account:

1. Go to the Account view.
2. Click Upgrade in the General panel.
3. Click the tile for the plan that you are interested in and then click Request upgrade.

Account Usage Limits

Your Eyes license agreement specifies various usage limits that govern how much Eyes testing you can do.

Some of these limits differentiate between page verifications and component verifications:

• Page verification: Verifications performed by SDKs that aim to test complete application pages. For example, Selenium, Espresso, XCUI, Cypress and Playwright SDKs.
• Component verification: Verifications performed by SDKs that aim to test UI components in component galleries such as Storybook.

The distinction is significant, since the resource usage of these two approaches can be very different. Images captured for pages can be very large, and are more complex to process. Component checkpoints are only generated by some SDKs, and, by definition, are small (with a captured image size less than 1024x768), but many more images are typically captured and verified.

Limit Metrics

The Limits panel displays the values of the various limits defined by your license. The values you see depend on the details of the account license:

Monthly checkpoints, Monthly component checkpoints
The maximum number of checkpoint executions allowed each month by the license, broken down by pages and components. This is the limit for a license based on executed checkpoints, and is comparable to the number of test steps you see in your test result in the Test Manager.

Number of pages, Number of components
The maximal number of pages and components that can be tested each month. This is the limit for a license based on the number of pages/components verified, and it is comparable to the number of calls there are to the check() methods in your test code, regardless of how many times they are tested during that month.

Test concurrency
The maximum number of tests with page checkpoints that can run simultaneously.

Component test concurrency
The maximum number of tests with component checkpoints that can run simultaneously.

Users
The maximum number of users that can be added to the account. A user is a team member that has full rights to accept and reject steps, to annotate steps, and to update baselines.

Viewers
The maximum number of viewers that may be added to the account. A viewer is a team member that can only view the test results but and is not allowed to make any changes. For more details see Setting users access rights.

Assigning Team Usage Limits

The limits described above apply to the entire account, irrespective of which team runs the tests. This is the default way to apply the limits. Eyes gives the account admin the option to distribute one or more of the account limits between the teams in the account.

For example, if the account is limited to 1000 checkpoints and there is a QA team and two development teams, the account admin may decide to provide each team with a "budget" - the main QA team are allowed to run 600 checkpoints and each development team is allowed to run up to 200 checkpoints.

Setting the Team Limits

Only an account admin can set the team usage limits. Navigate to the Admin page using the page navigator, and then select the Account tile. At the bottom of the Account Limits section, you can the see Limits per team table. The screenshot below shows the team limits setting with the default values where all limits are applied at the account level.

To distribute one or more limits between the teams, do as follows:

1. Click the Allocate button.

2. A dialog opens that shows the four limits that can be divided amongst the teams. By default, the toggle to the left of each limit type will be disabled, meaning that the limit is applied at the account level. To the right of the limit name you can see the value of the account limit. If you have a verified pages/components based license you will see the Monthly page/component checkpoints limits as shown in the screenshot below. If you have a executed checkpoints based license then you will see the Number of pages/components limits.

   

3. To distribute a limit between the teams, enable its toggle button, and click the limit label to show a list of the teams in the account. Initially, zero units of that limit will be allocated to each team:

   

4. In the text box for each team, enter how many of the available account limit units (e.g. checkpoints) should be allocated to that team. As you enter values for each team, the account limit display is updated to show how many units have been allocated relative to the total account limit.

   

5. At then end of this process, the sum of the values assigned to all the teams must equal the account limit. For example, in the screenshot below you can see how the maximum 1000 monthly component checkpoints have been fully distributed between the teams:

   

6. Repeat this process with all of the limits that you want to distribute amongst the teams.

7. Click the Apply button to accept. If any team has zero units allocated, Eyes will display a dialog asking you to confirm that this is your intention.

Viewing and Updating Team Limits

Any person with admin rights, either at the account or the team level, can view the current team limits settings by clicking on the Allocate button. Clicking on any limit heading will expand that limit to show the current unit distribution amongst the teams. If you click a different heading, then the currently visible limit will close and the clicked limit will expand to show the distribution for that limit.

If you have account admin rights and you want to change the distribution, you can do so, but you should ensure that all of the account limit units have been fully distributed between the teams. When you are done, click Apply to save the settings.

Canceling team limits

If you have distributed a limit between the teams, and you want to revert it to an account limit, enter the team limit dialog by clicking on the Allocate button, disable the toggle next to the limit you want to revert, and click Apply to close the dialog.

Redistributing team limits

If you make any changes to the active teams in the account (i.e. a team is added, deleted, enabled or disabled), and at least one limit has been distributed to that team, then the Test Manager will display a dialog indicating that you need to adjust the team usage.

Admins List

The Admins panel lists the account administrators. Account administrators can create and remove teams, designate account and team admins, add or remove users, manage team memberships, and access the test results of all teams that belong to the account. The panel lists the User name and Full name of each user that can function as an account administrator.

Making a User an Account Admin

To add a user as an account admin:

• Navigate to the Admin Account page.
• Click in the User to add text box and select the user you want to add. You can start typing the name and the list will be filtered to include only nmes that include the text you type.
• Click the Add button.
• Repeat steps 1-3 to add more users.