User Permissions

Permissions vary slightly between repositories, which extend the settings from GitHub, and Sandboxes and Devboxes, which solely exist in CodeSandbox.

Devboxes and Sandboxes

Private

Private Devboxes and Sandboxes can only be accessed by workspace members who own the Sandbox or Devbox.

Unlisted

Unlisted Sandboxes and Devboxes are accessible by workspace members and non-workspace members with the URL.

Public

Public Sandboxes and Devboxes are visible to everyone. Public Sandboxes are a great option for sharing content with people outside the workspace. Non-workspace members are able to open and run public Sandboxes and Devboxes. In order to edit, however, they will need to fork the Sandbox or Devbox to their own workspace.

If you want to share a Devbox publicly, consider turning it into a template. That way, the runtime of the VMs used to run the code and/or the preview won't be charged to your workspace.

Default privacy settings for Devboxes and Sandboxes can be set in the workspace portal in the permissions tab (opens in a new tab)

Repositories

Users with write access

Users with write access to a repository can enjoy the full feature set available on CodeSandbox Repositories.

Users with read-only access

Users with read-only access to the repository can browse the content of the repository, check the previews and execute a few tasks. To introduce changes, they need to create a contribution branch or fork the repository. For more information, visit the open source collaboration page.

Anonymous users

Users without a CodeSandbox account can only browse the content of the project and interact with the previews.

Feature comparative guide

The following table outlines the features available according to each permission.