Files
zitadel/apps/docs/content/concepts/structure/_project_description.mdx
T
93a4ed8857 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]>
2026-02-17 13:14:57 +01:00

11 lines
806 B
Plaintext

The idea of projects is to have a vessel for all components who are closely related to each other. Multiple projects can exist within an organization.
![Project Grant](../../../public/img/concepts/objects/project_grants.png)
All applications within a project share the same roles, grants, and role assignments:
- **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.