mirror of
https://github.com/andwati/zitadel.git
synced 2026-11-21 04:18:46 +00:00
chore: rename authorization to role assignment (#11588)
# Which Problems Are Solved As part of the naming consistency initiative, the terms Authorization, User grants, internal authorization and other similar terms that are used in the context of assigning project roles to users are replaced by Role Assignments in the UI, API docs, and documentation. # How the Problems Are Solved By replacing the following terms with Role Assignments in API docs, Console UI, and guides. - Authorization - internal authorization - external authorization - User Grant - Roles and Authorizations By adding a note in the API docs to make it clear that Authorization within the context of Authorization Service API refers to role assignments, not to OAuth authorization as it is still used in the APIs. By updating some screenshots in documentation / guides to show "Role Assignments" instead of "Authorizations" in the UI. # Additional Changes N/A # Additional Context - Closes https://github.com/zitadel/zitadel/issues/11289 --------- Co-authored-by: Copilot <[email protected]>
This commit is contained in:
co-authored by
Copilot
parent
fa5e76661a
commit
93a4ed8857
@@ -2,9 +2,9 @@ The idea of projects is to have a vessel for all components who are closely rela
|
||||
|
||||

|
||||
|
||||
All applications within a project share the same roles, grants, and authorizations:
|
||||
All applications within a project share the same roles, grants, and role assignments:
|
||||
|
||||
- **Applications** is your software that initiates the authorization flow. This could be a web app and a mobile app that share the same roles.
|
||||
- **Roles** are a means of managing user access rights for a project.
|
||||
- **Authorizations** define which users have which roles. Authorizations are also called “user grants”.
|
||||
- **Granted Organizations** can manage selected roles for your project on their own.
|
||||
- **Applications** initiate the authorization flow. They could be a web application and a mobile application that share the same roles.
|
||||
- **Roles** define the access rights of a project and can be assigned to users.
|
||||
- **Role Assignments** define the association between users and their roles within a project.
|
||||
- **Granted Organizations** are organizations that have been granted access to a project in a different organization, allowing them to manage user role assignments for that project.
|
||||
|
||||
@@ -7,7 +7,7 @@ sidebar_label: Granted Projects
|
||||
|
||||

|
||||
|
||||
With ZITADEL you can grant selected roles within your project to an organization. The receiving organization can then create authorizations for their users on their own (self-service).
|
||||
With ZITADEL you can grant selected roles within your project to an organization. The receiving organization can then create role assignments for their users on their own (self-service).
|
||||
|
||||
An example could be a service provider that offers a SaaS solution that has different permissions for employees working in Sales and Accounting. As soon as a new client purchases the service, the provider could grant the roles ‘sales’ and ‘accounting’ to that organization, allowing them to self-manage how they want to allocate the roles to their users.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user