Sharing resources

Projects and runners can be shared with specific groups or with everyone in your organization. This controls who can view, use, and manage your resources. To understand groups and how they work, see Manage groups.

​

Sharing Projects with Groups

Projects can be shared with specific groups or with everyone in your organization. This controls who can view and use your projects.

​

Share a Project

1. Navigate to your project’s details page
2. Click the Share button in the header
3. In the Share dialog, you’ll see two sections:
   • Groups with access: Specific groups that can access the project
   • General access: Organization-wide access settings

​

Add Groups to a Project

1. In the Share dialog, click Select a group to add
2. Select one or more groups from the list
3. Choose the appropriate permission level for each group:
   • User: Can view and use the project
   • Editor: Can view, use, update, and manage project settings
   • Admin: Full control including sharing and deletion

The groups you select will immediately have access to the project.

​

Change a Group’s Permission Level

1. In the Share dialog, find the group in the “Groups with access” section
2. Click the role dropdown next to the group name
3. Select a new permission level
4. The change takes effect immediately

​

Remove a Group’s Access

1. In the Share dialog, find the group in the “Groups with access” section
2. Click the role dropdown next to the group name
3. Select Remove access at the bottom of the menu
4. Confirm the removal

​

Share with Everyone in Your Organization

To make a project available to all organization members:

1. In the Share dialog, find the General access section
2. Click the dropdown
3. Select Everyone in [Your Organization Name]

All organization members will now have basic User access to the project. You can still grant elevated permissions to specific groups. To restrict access to specific groups only:

1. In the Share dialog, find the General access section
2. Click the dropdown
3. Select Only groups with access

Only members of explicitly granted groups will be able to access the project.

​

Sharing Runners with Groups

Runners can be shared with groups to control who can use them to create and manage environments.

​

Share a Runner

1. Navigate to Settings → Runners
2. Find the runner you want to share
3. Click the ⋯ (more actions) menu
4. Select Share runner
5. The Share dialog works the same way as for projects

​

Understanding Access Dependencies

Projects and runners work together to provide development environments. This creates important access dependencies you should understand when sharing resources.

​

How Dependencies Work

A project can be configured to use one or more runners (through environment classes). For a team member to successfully use a project, they need:

1. Access to the project (at any permission level)
2. Access to at least one runner that the project is configured to use

​

Warnings in the Share Dialog

The Share dialog will display warnings to help you avoid common access issues: When sharing a project:

“Users in these groups will not be able to use the project unless the underlying runner is also shared with them.”

This appears when you add groups to a project or change general access to “Everyone in organization.” When restricting runner access:

“Removing access to this runner may prevent users in these groups from using projects that depend on it.”

This appears when you remove a group’s access to a runner or change general access from “Everyone” to “Only groups with access.”

​

Example Scenarios

​

Organizing Teams with dedicated resources

Your organization has multiple teams working on different products. Each team needs their own projects and runners. The challenge: Control costs by ensuring teams only use their designated compute resources, and keep workspaces focused by showing only relevant projects. The solution: Create groups for each team and share resources accordingly:

• Create groups for each team
• Set up dedicated runners for different needs and share with your teams
• Share specific projects with the appropriate groups

The result: Each team sees only their projects and can only use their designated runners. Teams have autonomy within clear boundaries, costs are predictable and attributable, and workspaces stay focused.

​

Flexible Infrastructure for Different Needs

Your engineering team collaborates on the same application, but different members need different infrastructure based on location, compliance requirements, or specialized compute needs. The challenge: Everyone needs to work on the same codebase, but infrastructure requirements vary by location, role, and task. You don’t want developers manually selecting the right runner every time. The solution: Share one project with multiple specialized runners:

• Create one project: “Main Application”
• Set up multiple runners: “EU Runner”, “GPU Runner”, “AI Runner”
• Create groups: “Developers”, “ML Engineers”
• Share runners selectively
• Share the project with all groups

The result: Everyone works on the same codebase with the right infrastructure for their needs. Compliance requirements are met automatically, and developers don’t need to manually select runners.