9f0638fac9
* test spell check * fix indenting * test * add something to test * test spellcheck * spelling improvements * improve spelling and ignore list * Update site/docs/start/00-quick-start.de.md
2.4 KiB
| title |
|---|
| Roles |
What are Roles
With roles ZITADEL lets projects define there role based access control.
Roles can be consumed by the clients which exist within a specific project.
For more information about how roles can be consumed, have a look the protocol specific information.
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 |
Granting Roles
To give someone (or somewhat) access to a projects resources and services ZITADEL provides to processes. Roles can be either granted to users org to organisations.
Grant Roles to Organisations
The possibility to grant roles to an organisation is intended as "delegation" so that a org can on their own grant access to users.
For example a service provider could grant the roles user, and manager to an org as soon as they purchases his service. This can be automated by utilising a service user in the service providers business process.
Screenshot here
Grant Roles to Users
By granting roles to users, be it humans or machines, this user receives the authorization to access resources from a service.
Screenshot here