Go to My Account > Add Team Members to add a new sub-account.
You can choose to either:
Invite Someone: create a new account with email/password combination.
We'll send an activation link to this person's email address so he/she can immediately log in with the newly created sub-account.
Add existing TestingBot User: in case the person you'd like to add to your group already has an account on TestingBot,
then simply fill in the e-mail address they use on TestingBot. They'll receive an invite to join your group account as a sub-account.
To remove or edit a sub account, go to My Account > Team Members.
Disconnecting a sub-account
From there, you can disconnect a sub-account (clicking the red cross icon).
This disconnects the sub-account from your group.
The account will not be removed from our system, but it will no longer be associated with your account or other sub-accounts.
Making a sub-account Read-Only means the account can only view tests, not modify or remove any results from the team account.
You can choose to make a sub-account have USER permissions or ADMIN permissions.
- USER: the sub-account does not have any rights to add/remove other team members to the team account.
- ADMIN: the sub-account can add/remove other users to the team account. The only difference with the parent account is that the parent account can access/modify billing related settings, which an admin can not do.
The Concurrency Limit indicates how many tests a user can run simultaneously. The more tests you run concurrently, the faster you can process all your tests.
By default, a sub-account will have the same amount of concurrency like the parent account (which depends on the pricing plan that the parent account is subscribed to).
It is possible to change the concurrency limit per user. This way, you can for example divide the amount of concurrency you have across various team members.
For example: you have an Enterprise plan with 30 parallel tests: You can assign 10 parallel tests to team member A, 15 to team member B and 5 to team member C. A user can not run more tests concurrently than the maximum amount assigned. If the user tries to run more tests, the tests will be queued in our system, waiting for a slot to free up.
If you do not change this setting for any of the sub-accounts, then all sub-accounts will have access to the maximum amount of concurrency. Whenever this threshold is reached, extra tests for any sub-account will be queued until a slot frees up.
Tests Overview for Sub-Accounts
To see a list of tests created by a sub-account, click the "Tests ran by this user".
The list contains tests ran by this sub-account (with their own key/secret).