Many Sauce Labs customer act in turgid development teams, with dozens of engineers who write and run tests. We recently added new features to make life good for whoever terminate up managing these teams of Sauce users.

For a while Sauce accountholders get been capable to create subaccounts so their teams can all run tests under one charge report. This flat structure got a bit unwieldy, so we lately redesign the subaccounts page to allow for more complex squad designing, including the ability to designate certain account as admin chronicle which can add or delete other subaccounts, and move them about to organise pretty much any arbitrary team structure.

In case you & # x27; ve ne'er visitedyour subaccounts page, the screenshot to the right should help you voyage to it. The rest of this article will be a bit of a tutorial on how to use the new features I just mentioned.

The bad change is the ability to create a tree-like hierarchy for your squad. Let & # x27; s imagine that Sauron was the head of a QA section. His subaccounts page might now look like this:

The first thing to note is that there are two types of subaccounts: admins and regular users. Both can have subaccounts of their own, but admins can manage subaccounts for their parent. In this example, Saruman could add new subaccounts for Sauron, or, say, update Gollum & # x27; s e-mail address. This is a convenient way to paw off responsibility for squad management to people you believe (though if I were Sauron, I wouldn & # x27; t trust Saruman that much). The way to view all these subaccounts is too much improved; you can navigate through multiple levels of a tree construction:

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

There is besides a new way to get usage data from this structure: rollup modality. Rollup mode takes each chronicle with subaccounts and, rather of showing you usage for that account itself, present you the full utilization for itself and all its descendant. This is a commodious way of comparing usage for different subsection of your team.

Setting up a hierarchy is easy. Simply click & quot; Add & quot; on the subaccounts page, or edit an existing user. You & # x27; ll now be capable to say which report should own it.

If you & # x27; re the main account, you can also designate which subaccounts should be admins by checking the & quot; Admin? & quot; box in the form:

Then, when your admins log in, they & # x27; ll be able to see the whole team and manage your other subaccounts for you (and they & # x27; ll get a little notice to let them know why they & # x27; re seeing all these accounts):

We hope you bask these new features and that it makes managing your testing team a more aerodynamic experience! Please sense complimentary to give us feedback and let us know what else would be useful to you.