​
Policies

Policies allow you to manage and configure functionality across your Gitpod organization.

​
Manage a Policy

To update an Organizational policy:
  1. Ensure you are a member with the “owner” role.
  2. Navigate to the Gitpod dashboard.
  3. Ensure you are in the context of the Organization you want to set the policy for.
  4. Navigate to the settings page.
  5. Update the relevant policy.

​
Workspace Sharing

Workspace sharing is enabled by default. Through this policy, Organization Owners can prevent Members from sharing workspaces that have been started within an Organization.
  • Prevents workspaces within an Organization from sharing access to a running workspace.
  • Members can stop sharing a workspace at any time, regardless of the Organizational Policy.
  • Any currently shared workspaces will not have sharing access removed.

​
Workspace timeouts

On the organization policy settings page, you can do the following to manage workspace timeouts:
  • Set the default workspace timeout for all workspaces in the organization. If users have defined their own workspace timeout in their preferences, it will be used instead.
  • Enable or disable users’ ability to set their own workspace timeout. If disabled, the organization default timeout will be used for all workspaces, and users will not be able to use their own custom timeout or change it ad-hoc.

​
Limit the Amount of Concurrently Running Workspaces per User

Depending on your installation and billing tier, users in your organization will be limited to opening 16 workspaces concurrently, which can be adjusted in the organization policy settings. Attempting to open workspaces past the limit will result in an error message, both for creating new workspaces and starting existing ones.

​
For Enterprise Users

For Gitpod Enterprise users, the default limit is 16 concurrent workspaces per user. The limit on the Policies page can be set to any non-negative integer value. If the limit is set to 0, the installation-wide default limit of 16 will be used.

​
For Pay-As-You-Go Users

For Gitpod Cloud users, the default limit is 4 concurrent workspaces per user for free organizations and 16 for paid ones. The limit on the Policies page can be set to any non-negative integer value, but it cannot exceed your billing tier’s limit. If the limit is set to 0, your billing tier’s limit will be used.

​
Restrict Workspace Classes

Restricting workspace classes can be useful to avoid unexpected costs or to remove classes that are unnecessary for an organization. An organization owner can restrict the available workspace classes via the Organization Settings. Members of the organization will then only see the selected workspace class options in the various Gitpod interfaces. This organization-level setting takes precedence over other settings, such as repository-level workspace class defaults.

​
Limit available Workspace Editors

Limiting available workspace editors can be useful to maintain a consistent user interface for all members and prevent the use of unsupported or unauthorized editors within an organization.