Give a group access to a child workspace
Last updated: October 11, 2026
Assign a group from your studio's parent workspace to one of its child workspaces, so the team's members get access there with the group's role and usage limit, while you keep managing the group in one place.
Before you start
- Your studio needs parent and child workspaces, and groups are part of the Enterprise plan. See Parent and child workspaces.
- You need Manage billing in the parent workspace, and Manage workspace settings in the child you assign to. A child where you lack it does not appear in the list.
- Create the group in the parent first, with its members, role and any usage limit. See Set a usage limit for a group.
Steps
In the parent workspace, open the workspace menu, choose Workspace Settings, then Groups & Roles, and select the team's group.
Under Assigned workspace, open the list and choose the workspace the team works in. It lists every workspace below this one, not only direct children.
Select Save.
Result
Layer confirms with Group assigned. Every member of the group joins the child workspace with the group's role, and the group's usage limit caps what they spend there. In the parent, the group no longer grants its role, and each card on the group's page says where it applies, for example Members of this group hold its role in the child, not here.
The group keeps living in the parent and stays in sync with the child:
- Adding or removing a member in the parent adds or removes them in the child.
- Changing the group's role or usage limit in the parent changes it in the child.
- Members who go over the limit are listed on the child's Groups & Roles page, where the spending happens.
- The group itself is not in the child's list of groups, and the child's admins cannot edit it.
Production tips
- One group per team, one workspace per game. Keep every team's group in the parent and assign each to the workspace for the game it works on. Moving a team to another game is then one change of Assigned workspace.
- Give the group a role defined in the parent. A custom role created in the parent works in every child, so the same role means the same thing across the studio.
- Fund the child before the team arrives. The group's limit caps spending but does not bring Creative Units with it. Transfer units to the child so the team can start straight away.
- Let your identity provider manage the members. A group provisioned by SCIM can be assigned like any other, and its membership keeps following your directory.
- Unassign to bring a team back. Choose This workspace (not assigned) and select Save. The role and limit apply in the parent again, and members who had access to the child only through this group lose it.
If something goes wrong
- "No workspace below this one is available to assign to." The workspace has no children, or you lack Manage workspace settings in them. Ask an admin of the child workspace for access.
- A child's admin cannot change the group. Assigned groups are managed from the parent. Edit the group there.
- Switching the group to another child failed. A switch removes the old assignment before adding the new one, so the group may now be unassigned. Check Assigned workspace and save again.
- Deleting the group. Delete Group on an assigned group also removes its members' access to the child; the confirmation says so.