> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/infrastructure-as-code-management/3.0/platform/workspaces/workspace-rbac.md).

# Workspace Permissions

You can control who has different types of access to the Workspace in a project. Create/edit a Role, and select the "Infrastructure as Code Management" section

![Resources](/files/5rhLgJZvtxki4gSsusU5)

For each Role, you can define the following set of permissions:

1. **View** - Permitting users to view the Workspaces in the project
2. **Create/Edit** - Permitting users to create and edit Workspaces in the project
3. **Delete** - Permitting users to delete Workspaces in the project
4. **Edit Variables** - Permitting users to create and edit Environment and Terraform variables
5. **Delete Variables** - Permitting users to delete Environment and Terraform variables
6. **Approve** - Permitting users to approve the Infrastructure Stage (using the approval step)
7. **Access State** - Permitting users to view the state (including historical revisions)

### Using Resource Groups <a href="#using-resource-groups" id="using-resource-groups"></a>

You can utilize Resource Groups functionality to specify which users can access a specific Workspace. For this, create a resource group, add the specific (or all) Workspaces, and bind it to a specific user or user group.

![Resources](/files/MZTMy3A1dJ4fV8lvk3r2)

To learn more about Resource Groups, go to [this documentation](/harness-ai/use-harness-platform/platform-access-control/manage-resource-groups.md)