# Manage SOC roles

Supported in:

> [!NOTE]
> **Note:** SOAR SOC roles will continue to exist after [migrating SOAR to Google Cloud](https://docs.cloud.google.com/chronicle/docs/soar/admin-tasks/advanced/migrate-to-gcp). They are independent of IAM roles.

Roles in Google Security Operations let administrators streamline workflows by creating custom access levels and automating task assignments. This document explains how to create SOAR SOC roles to control permissions and manage SOC team workloads effectively.

## Role permissions and customization

You can customize roles to fit the needs of your SOC. This lets you control permissions, manage team workloads, and route tasks more effectively, with these details in mind:

- An administrator can add up to 20 customized roles.
- Predefined SOC roles (such as `Tier 1` or `Collaborator`) can also be modified.
- New roles can be created for various purposes, such as to:
  - Route tasks to specific SOC teams
  - Manage SOC teams' daily workloads
  - Control view permissions
  - Manage cases access permissions

## Create a new role

To create a new role, follow these steps:

1. Go to **Settings \> Access Management \> SOC Roles**.
2. On the **Roles** page, click **Add**.
3. In the **Add Role** dialog, enter a name for the new role, and select which additional roles it should have access to. Doing this affects which cases users can see in the Google SecOps platform.  
4. Click **Add**. The role is added to the table.

> [!NOTE]
> **Note:** Click **Edit** to set a role as the default. All new cases are automatically assigned to the default role, and it can't be deleted while it's a default role.

For more information on roles, see [Learn how to control access to the platform](https://docs.cloud.google.com/chronicle/docs/soar/admin-tasks/advanced/control-access-to-platform).

**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/)