# Managing RDE access

Access to Remote Dev Environments is granted per workspace member. Being a member of a workspace that has RDE isn't enough on its own: until someone grants you access, the **Remote Dev Environments** section doesn't open for you.

## RDE access overview

RDE is a **standalone product**. Unlike Bitrise CI and Release Management, its access isn't tied to projects: it's a single on-or-off setting that applies to the whole workspace. There's nothing to configure per project, and no role to choose.

- Granting access assigns the **RDE User** role on the workspace. That's the only RDE role.
- Admin access to projects doesn't include RDE. It has to be granted separately.
- Workspace owners always have access.

Everyone with the RDE User role can create and manage their own sessions, templates, and saved inputs.

:::important[Owners and managers only]

Only workspace owners and workspace managers can grant or revoke RDE access. For the full picture of workspace roles, see [Roles and permissions in workspaces](/bitrise-platform/workspaces/collaboration-and-permissions-in-workspaces/roles-and-permissions-in-workspaces).

:::

You can grant access in three places, all on the **Collaboration** page of the workspace settings:

- To an existing member: [Granting access to a member](#granting-access-to-a-member).
- To a whole [workspace group](/bitrise-platform/workspaces/collaboration-and-permissions-in-workspaces/workspace-groups): [Granting access to a group](#granting-access-to-a-group).
- To someone you're inviting: [Adding members to workspaces](/bitrise-platform/workspaces/collaboration-and-permissions-in-workspaces/workspace-collaboration#adding-members-to-workspaces).

If your workspace provisions users through an identity provider, you can assign the role automatically: [Managing RDE access with SCIM](#managing-rde-access-with-scim).

## Granting access to a member

1. 1. Log in to Bitrise and hover over the left navigation bar.
1. Make sure you have the right workspace selected in the **Workspace** menu.
1. Select **Settings**.
1. On the left, select **Collaboration**.
1. On the **Members** tab, find the member and click the options menu (⋮) next to their name, then select **View details**.
1. On the **Overview** tab, click **Manage access**.
1. Under **Standalone products**, turn on **Remote Dev Environments**.
1. Click **Save changes**.

The member gets the **RDE User** role and can open the **Remote Dev Environments** section right away.

:::note[All projects only]

The **Standalone products** section shows up when you manage access across all projects. It isn't part of the per-project **Change access** flow, because RDE access isn't project-specific.

:::

## Granting access to a group

Every member of the group inherits the access, including people you add to the group later.

**Existing group**

1. 1. Log in to Bitrise and hover over the left navigation bar.
1. Make sure you have the right workspace selected in the **Workspace** menu.
1. Select **Settings**.
1. On the left, select **Collaboration**.
1. Select the **Groups** tab and find the group you need.
1. Open the group's details and click **Manage access**.
1. Under **Standalone products**, turn on **Remote Dev Environments**.
1. Click **Save changes**.

**New group**

1. 1. Log in to Bitrise and hover over the left navigation bar.
1. Make sure you have the right workspace selected in the **Workspace** menu.
1. Select **Settings**.
1. On the left, select **Collaboration**.
1. Select the **Groups** tab and click **Create group**.
1. Enter a group name in the **Group name** field.
1. Under **Standalone products**, turn on **Remote Dev Environments**.
1. Click **Create group**.

## Checking who has access

The workspace settings show RDE access in a few places:

| Location | What you'll see |
|---|---|
| **Workspace settings** > **Collaboration** > **Members** tab | **Remote Dev Environments** listed in each member's **Product access** column. Members without any product access show `(no access)`. |
| **Workspace settings** > **Collaboration** > **Members** tab > options menu (⋮) > **View details** > **Overview** tab | A **Product access** table with a **Remote Dev Environments** row and the **RDE User** tag. |
| **Workspace settings** > **Collaboration** > **Groups** tab | The **RDE User** role on each group. Filter the list by that role to see every group with access. |

## Revoking access

Revoking access doesn't delete the person's sessions. Running sessions keep running until they auto-terminate, and terminated sessions keep their persistent disk until someone deletes them or the stack they were created from is removed. To reclaim the storage, delete the sessions explicitly.

:::note[Access from a group]

If a member still has RDE access after you revoke it directly, check their **Groups** tab: a group they belong to may grant it. Remove them from that group, or turn off RDE for the group.

:::

**Member**

1. 1. Log in to Bitrise and hover over the left navigation bar.
1. Make sure you have the right workspace selected in the **Workspace** menu.
1. Select **Settings**.
1. On the left, select **Collaboration**.
1. On the **Members** tab, find the member and click the options menu (⋮) next to their name, then select **View details**.
1. On the **Overview** tab, click **Manage access**.
1. Under **Standalone products**, turn off **Remote Dev Environments**.
1. Click **Save changes**.

**Group**

1. 1. Log in to Bitrise and hover over the left navigation bar.
1. Make sure you have the right workspace selected in the **Workspace** menu.
1. Select **Settings**.
1. On the left, select **Collaboration**.
1. Select the **Groups** tab and find the group you need.
1. Open the group's details and click **Manage access**.
1. Under **Standalone products**, turn off **Remote Dev Environments**.
1. Click **Save changes**.

## Managing RDE access with SCIM

If your workspace uses SCIM provisioning, your identity provider can assign the RDE User role with the standard `roles` attribute. The value is `rde:rde_admin`:

```json
{
  "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
  "userName": "user@example.com",
  "roles": [
    { "value": "workspace:workspace_contributor" },
    { "value": "rde:rde_admin" }
  ]
}
```

Sending a `roles` array without an `rde:` entry removes the user's RDE access. For the request formats each identity provider uses, see [Configuring SCIM](/bitrise-platform/accounts/saml-sso-in-bitrise/configuring-scim#managing-workspace-and-product-roles-via-scim).
