Documentation
Hierarchy
Organize large teams with parent and child workspaces
For larger organizations, workspaces can be organized in a hierarchy - a parent workspace with child workspaces underneath. This mirrors your org structure: company → departments → teams.
How it works
- check_circleCreate child workspaces from a parent workspace
- check_circleEach child workspace has its own members, roadmaps, and settings
- check_circleCredits can flow from parent to child workspaces
- check_circleParent workspace owners can view credit usage across all children
- check_circleAnalytics can include or exclude child workspace data
- check_circleChild workspaces can be detached from the parent if needed
Credit sharing in a hierarchy
When credits flow from a parent workspace, you can set per-member limits in child workspaces. The parent workspace owner sees a unified view of spending across the entire hierarchy - broken down by child workspace and by member.
When to use hierarchy
Multi-department programs
Each department gets its own workspace with tailored roadmaps, while the company has central credit purchasing and analytics.
Regional teams
Create child workspaces per region with localized content, while maintaining company-wide visibility.
Training cohorts
Each cohort gets its own workspace under a master program workspace. Run them independently with shared resources.