2020-10-16 14:13:02 +02:00
---
title: Roles
---
### What are Roles
2020-12-01 16:56:33 +01:00
**ZITADEL** lets [projects ](administrate#projects ) define their **role based access control** .
2020-10-16 14:13:02 +02:00
2020-10-26 13:54:29 +01:00
**Roles** can be consumed by the [clients ](administrate#clients ) which exist within a specific [project ](administrate#projects ).
2020-10-16 14:13:02 +02:00
2020-10-26 13:54:29 +01:00
For more information about how **roles** can be consumed, have a look the protocol specific information.
2020-10-16 14:13:02 +02:00
feat: docs rehaul, fix missing context in console, quickstarts (#1212)
* onboarding components, routing, steps
* onboarding component, toc
* fix onboarding mixin
* header
* refactor docs
* fix layout
* cleanup routing
* docs routing
* fix conventions
* de en routing
* docs, guide contents, nav
* rem i18n support
* fix routing from docs
* rollup onwarn changes, preload
* update svelte plugin, update rollup config
* move docs
* revert img style, remove code table
* rem de completely
* rollup optim, template
* angular quickstart, quickstart overview page, update deps
* fix link
* pack, slug
* prefetch binding, hidden links
* export log
* guards route ch
* fix homepage
* angular docs
* docs
* resolve fsh
* overview
* docs
* docs
* packages fix race condition
* nav, home link
* add vue, aspnet
* doc optimizations
* embed status pal
* angular guide
* angular guide
* dotnet, angular guide
* viewbox
* typo
* block onboarding route for non iam writers
* set links from component data
* fix: fetch org context in guard, more main cnt (#1192)
* change get started guide, fix code blockquotes, typos
* flutter guide
* h2 spacing
* highlight strong
* plus
* rm start sublinks
* add proxy quickstart
* regex
* prevent outside click, fix project grant write
Co-authored-by: Florian Forster <florian@caos.ch>
Co-authored-by: Livio Amstutz <livio.a@gmail.com>
2021-02-16 16:59:18 +01:00
- [OpenID Connect / OAuth ](quickstarts#How_to_consume_authorizations_in_your_application_or_service )
2020-10-16 14:13:02 +02:00
### Manage Roles
Each **role** consist of three fields.
| Field | Description | Example |
|:-------------|:-----------------------------------------------------------------------------|--------------------------------------------------|
| Key | This is the **Roles** actual name which can be used to verify the users roles. | User |
| Display Name | A descriptive text for the purpose of the **Role** | User is the default role provided to each person |
| Group | The group field allows to group certain roles who belong in the same context | User and Admin in the group **default** |
2020-10-26 13:54:29 +01:00
### Granting Roles
2020-10-16 14:13:02 +02:00
2020-12-01 16:56:33 +01:00
To give someone (or somewhat) access to a [project's ](administrate#projects ) resources and services **ZITADEL** provides two processes: **Roles** can either be granted to [users ](administrate#Users ) or to [organisations ](administrate#Organisations ).
2020-10-16 14:13:02 +02:00
#### Grant Roles to Organisations
2020-12-01 16:56:33 +01:00
The possibility to grant **roles** to an [organisation ](administrate#Organisations ) is intended as "delegation" so that a [organisation ](administrate#Organisations ) can on their own grant access to [users ](administrate#Users ).
2020-10-16 14:13:02 +02:00
2020-12-01 16:56:33 +01:00
For example a **service provider** could grant the **roles** `user` , and `manager` to an [organisation ](administrate#Organisations ) as soon as they purchases his service. This can be automated by utilising a [service user ](administrate#Manage_Service_Users ) in the **service providers** business process.
2020-10-16 14:13:02 +02:00
> Screenshot here
#### Grant Roles to Users
2020-12-01 16:56:33 +01:00
By granting **roles** to [users ](administrate#Users ), be it [humans or machines ](administrate#Human_vs_Service_Users ), this [user ](administrate#Users ) receives the authorization to access a project's resources.
2020-10-16 14:13:02 +02:00
> Screenshot here
