Skip to main content

Teams

Organize users into teams for collaboration and resource sharing.

Creating Teams

How to Create a Team

  1. Go to SettingsTeams
  2. Click Create Team
  3. Configure team settings:
    • Team Name: Unique identifier (e.g., "data-science", "frontend")
    • Display Name: Friendly name shown in UI
    • Description: Team purpose and responsibilities
    • Team Lead: Optional user with additional team permissions
  4. Click Create Team

Team Structure

Teams can represent:

  • Departments: Engineering, Data Science, Product
  • Projects: Project Alpha, Customer Portal
  • Functions: DevOps, QA, Security
  • Locations: US Team, EU Team, APAC Team

Team Members

Adding Members

During Team Creation:

  • Select users from existing user list
  • Assign all with same role initially

After Team Creation:

  1. Open team settings
  2. Click Add Members
  3. Select users to add
  4. Click Add

Removing Members

  1. Go to team settings
  2. Click Members tab
  3. Find user in list
  4. Click Remove
  5. Confirm removal

Member Roles

Team members can have different platform roles:

  • Admin: Full access to platform
  • Developer: Create and manage resources
  • Viewer: Read-only access
info

Team membership is separate from platform role. A user with Developer role in one team may have Viewer role in another.

Team Permissions

Resource Sharing

Share resources with entire team:

Applications:

  • Share app with team for view or edit access
  • All team members inherit permissions
  • Team access appears in app permissions

Projects:

  • Add team to project access control
  • All workspaces in project are accessible
  • Team members can create workspaces

Workflows:

  • Share workflow with team
  • Team can view execution logs
  • Edit permission allows workflow modification

Data Sources:

  • Share data source with team
  • Credentials remain encrypted
  • Team can query data source

Team-Owned Resources

Resources can be owned by team rather than individual:

  1. Create resource (app, workflow, etc.)
  2. Change owner to team
  3. All team members can access
  4. Resources persist if member leaves

Resource Quotas

Setting Team Quotas

Limit resources available to team:

  1. Open team settings
  2. Go to Resource Quotas tab
  3. Configure limits:
    • CPU: Total CPU cores across all team resources
    • Memory: Total RAM allocation
    • Storage: Total disk storage
    • Apps: Maximum number of applications
    • Workflows: Maximum number of workflows
    • Workspaces: Maximum number of workspaces
  4. Click Save Quotas

Quota Enforcement

  • New resources rejected if quota exceeded
  • Team lead and admins notified when approaching limit
  • Can request quota increase from admin
  • Usage shown in team dashboard

Team Dashboard

Team Overview

View team metrics and activity:

  • Active Members: Number of team members
  • Resource Count: Apps, workflows, workspaces owned by team
  • Resource Usage: CPU, memory, storage consumption
  • Recent Activity: Latest resource changes
  • Cost Allocation: Team's portion of infrastructure costs

Team Insights

Track team productivity:

  • Deployments: Number of app deployments
  • Workflow Executions: Workflow runs per day/week
  • Workspace Usage: Active workspace hours
  • Collaboration: Resources shared within team

Team Lead Privileges

Team leads have additional permissions:

Team Management

  • Add and remove team members
  • Update team description and settings
  • View team resource usage
  • Request quota increases

Team Resources

  • View all team-owned resources
  • Transfer resource ownership
  • Archive inactive resources
  • Monitor team costs

Restrictions

Team leads cannot:

  • Change other users' platform roles
  • Access admin-only features
  • Modify billing settings
  • Create governance policies

Cross-Team Collaboration

Sharing Between Teams

Share resources across team boundaries:

  1. Open resource (app, workflow, etc.)
  2. Click Share
  3. Select multiple teams
  4. Set permissions per team
  5. Click Save

Multi-Team Projects

Projects can have multiple teams:

  1. Create or open project
  2. Go to Access Control
  3. Add multiple teams
  4. Set permissions (View or Edit) per team
  5. Members from all teams can collaborate

Best Practices

Team Organization

  • Keep Teams Focused: Each team has clear purpose
  • Right Size: 5-15 members per team optimal
  • Clear Ownership: Assign team lead for accountability
  • Regular Reviews: Audit team membership quarterly

Resource Management

  • Team Ownership: Use team-owned resources for shared work
  • Individual Resources: Personal workspaces owned by individual
  • Naming Conventions: Prefix resources with team name
  • Cleanup: Archive or delete unused team resources

Collaboration

  • Shared Volumes: Use project volumes for team data
  • Documentation: Maintain team wiki/documentation
  • Communication: Use team Slack channel
  • Code Review: Review team members' work

Security

  • Least Privilege: Share resources only with necessary teams
  • Sensitive Data: Use private resources for sensitive work
  • Access Reviews: Review team access quarterly
  • Offboarding: Remove departing members immediately

Team Templates

Pre-Configured Teams

Create teams from templates:

Data Science Team:

  • Members: Data scientists, ML engineers
  • Resources: JupyterHub workspaces, model registry access
  • Quotas: High GPU allocation

Frontend Team:

  • Members: Frontend developers, designers
  • Resources: React/Vue app templates
  • Quotas: Standard CPU/memory

DevOps Team:

  • Members: DevOps engineers, SREs
  • Resources: Platform access, Kubernetes dashboard
  • Quotas: High infrastructure access
tip

Use teams to organize users, but use projects to organize work. A project may have multiple teams contributing.