# Expanded User and Resource roles


We now offer more granular user access controls across the RudderStack web app. We have created two roles: **Org Admin**, and **Org Member**. Org Member roles can be further customized with resource roles, e.g. **Transformations Admin** to provide granular access policies.

### What changed?

Prior to this release, our user roles consisted of Admin, Read-write, and Read-only, and gave broad access across all features throughout the RudderStack app. With this release, you can define granular access roles for teams that require more specific access policies.

### Use case

For example, a user might be responsible for writing JavaScript transformations, but should not have access to controlling data pipelines. This user can be given the **Transformations Admin** role, but will not be able to create, edit, or delete a source or destination.

### How does it work?

Users are invited at the organization level and access policies are set during the invite process. Individual access policies can then be managed in **Organization Settings** in the RudderStack dashboard under the **Members** tab.

{{< image src="images/dashboard-guides/user-management/invite-user.webp" alt="Invite member" >}}

### How do I get started?

Start by navigating to the **Members** tab in **Organization Settings**. This will give you a view of all the users in the organization, their roles, and their granular access policies.

See the [User Management]({{< ref "archive/dashboard-guides/user-management.md" >}}) guide to get started.