To access and use the Wrangler app, users must have permissions Access to the Wrangler UI and Create sandbox. It is recommended to use the pre-configured user group called Wrangler, which already contains all the necessary permissions. See User groups for more information.

Wrangler workspace is a special type of sandbox used to store everything related to Wrangler.

Every Wrangler user has their own workspace automatically created when they log into the Wrangler app for the first time. This workspace is private for each Wrangler user and other users cannot get access to it via Wrangler app (but users who can login to the Server Console can see other Wrangler workspaces if they have Unlimited access to sandboxes permission).

The name of the sandbox which stores the automatically created private workspace for given user is wrangler_home__[username] (e.g., wrangler_home\__clover).

Additional workspace - called Shared workspace - is created automatically on the Server as well. This workspace can be accessed by Wrangler users who are either Wrangler workspace administrators or who have been given access to this workspace by Wrangler workspace administrator. This workspace is stored in sandbox called wrangler_shared_home.

Each Wrangler workspace contains the input files users uploaded into Wrangler app, all jobs, sources, targets, and all the output data of the executed Wrangler jobs.

Administrators can manage the Wrangler workspace content in the Sandboxes module in the Server Console.

The storage for Wrangler workspaces is by default the directory containing shared Server sandboxes, but the directory can be changed by using the workspaces.home server property. See workspaces.home for more information.

Permissions for Wrangler users are defined in two different places:

The jobs users create in Wrangler are called Wrangler jobs. They are saved in the Wrangler workspaces and can be executed by users.

All executed Wrangler jobs can be viewed similarly to other Server jobs via Execution history.

Every execution of a Wrangler job is backed by a generated subgraph which implements all sources, steps, and targets of the job. The jobs themselves do not have any tracking, but the underlying subgraphs track record numbers and other statistics like any other subgraphs.

The jobs are always executed on Worker, and they are queued in the Job queue when the load is high.

The number of available Wrangler seats is specified in the CloverDX Server license. The Server counts the number of used Wrangler seats as the number of currently existing private Wrangler workspaces. To see how many Wrangler seats your license allows and how many are currently used, see license detail.

If a new Wrangler user logs in for the first time and there are no available seats, the following warning will appear, and the user will not be able to create any Wrangler jobs.

If you are interested in purchasing Wrangler seats reach out to your Account Manager or email sales@cloverdx.com.

When the number of existing Wrangler workspaces exceeds the number of available Wrangler seats (e.g., when you load a new Server license with fewer seats, or your Wrangler license expires), a notification appears in the header of the Server Console. If you click on the message in the header, you will be redirected to the License section under Configuration > Setup, where you can see the number of available and used seats.

If there are more used seats than the license allows, users can still log in but no Wrangler jobs can be executed, and users in the Wrangler app cannot see data previews of their jobs.

To decrease the number of used seats to the number of available seats delete some of the existing Wrangler workspaces (i.e., sandboxes beginning with wrangler_home__). At the same time you should make sure to modify user permissions so only users who need access to Wrangler have it so that extra users do not create additional Wrangler workspaces when they login.

CloverDX Wrangler is an integral part of CloverDX Server and as such cannot be disabled. However, you can prevent users from logging in and taking up a seat by removing the Access to the Wrangler UI permission from some or all user groups. By default, this option is enabled only for the Administrator and Wrangler user groups.