Workspaces allow teams to separate, distinct V7 workspaces or "child" teams, all managed from a single "parent" team. In this guide, we'll walk through how to set up workspaces, and touch on the ways in which child and parent teams interact.
Workspaces are available on our Enterprise plan and is activated from our backend. Please contact us to upgrade to the Enterprise tier and enable Workspaces.
Parent Teams have all of the functionality of a regular V7 team, while also acting as a hub from which multiple child teams can be managed.
Users/Admins in parent teams can view all of the data in the parent team, as well as the data in its child teams. Child teams have no access to the data within the parent team or any of its other child teams. To create a child team, click Add a client and send an invitation to the user who should act as the team's owner.
When inviting a new client to create a child team, you'll see a the option to cover the team's usage of Neural Networks. If selected, this option will bill the parent team for any model training and model inference fees associated with the child team's usage of Neural Networks.
Parent teams can switch between their teams and the child teams they manage by opening the team dropdown in the top left of any page.
The parent team's available annotation credits and storage are consumed by their child teams on a first come first served basis, but limits for credits and storage can be set on a team level from the Plans page under Settings.
Once a team owner has accepted their invitation to create a child team, they will be prompted to follow the standard team setup steps to create their V7 team and invite team members.
Child team owners, and all child team users will only have access to the data available within their team.
To increase the annotation credits and storage available to the child team, the child team owner can request increased limits from an admin in the parent team, or take over billing from the Plans page under Settings.
Updated 4 days ago