chore: naming inconsistency project grants (#11488)

# Which Problems Are Solved

As part of the consistent naming effort, this PR focuses on "Project
Grants".

# How the Problems Are Solved

All terms referring to a project being granted to another organization
for self-management were changed to "Project Grant" or "project grant".

# Additional Changes

None

# Additional Context

- closes #11287
This commit is contained in:
Livio Spring
2026-02-06 09:29:05 +00:00
committed by GitHub
parent 944765f89c
commit 21723df541
53 changed files with 155 additions and 155 deletions
@@ -33,7 +33,7 @@ The <span className="text-yellow-500">Custom Domain</span> to your ZITADEL insta
<p>
<span className="text-green-500">Client ID</span> is the resource id of an
application. It's the application where you want your users to login. You can
find the resource id in the Console. When using organization grants, use the
find the resource id in the Console. When using project grants, use the
client id from the origin organization.
</p>
@@ -24,7 +24,7 @@ You can create an external user grant, that allows the inviting organization to
## Project Grants vs. User Grants
Project grants are used to delegate access management of an entire project (or specific roles of the project) to another organization.
Project Grants are used to delegate access management of an entire project (or specific roles of the project) to another organization.
User grants provide a more granular approach, allowing specific users from external organizations to access your projects.
@@ -12,6 +12,6 @@ You can use projects within your organization to manage the security context of
ZITADEL allows you to give other organizations permission to manage certain aspects of a project within your organization on their own. This means you could set up a project with roles that should exist within your service/software, but allow another organization to allocate the roles to users within their own organization. As a service provider, you will find this feature useful, as it allows you to establish a self-service culture for your business customers.
![](../../../public/img/concepts/objects/organization_grants.png)
![Project Grant](../../../public/img/concepts/objects/project_grants.png)
Each organization has its own pool of usernames, which includes human and service users, for its domain (`{username}@{OrganizationDomain}.$CUSTOM_DOMAIN`). A username is unique within your organization. You can configure ZITADEL to use your own domain, and simplify user experience (`{loginname}@{yourdomain.tld}`).
@@ -1,6 +1,6 @@
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.
![](../../../public/img/concepts/objects/organization_grants.png)
![Project Grant](../../../public/img/concepts/objects/project_grants.png)
All applications within a project share the same roles, grants, and authorizations:
@@ -5,10 +5,10 @@ sidebar_label: Granted Projects
# Granted Project
![](../../../public/img/concepts/objects/organization_grants.png)
![Project Grant](../../../public/img/concepts/objects/project_grants.png)
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).
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.
To learn more about how to setup Project grants, read this guide [here](../../guides/manage/console/projects-overview#granted-projects-b2b)
To learn more about how to set up Project Grants, read this guide [here](../../guides/manage/console/projects-overview#granted-projects-b2b)
@@ -149,9 +149,9 @@ Login with your user on the customer organization to validate the setup.
## Create a project grant
### Organization Grant
### Project Grant
Switch to the `Demo-Vendor` organization, select Projects in the navigation, and click on `Portal` and then `Grants`.
Switch to the `Demo-Vendor` organization, select Projects in the navigation, and click on `Portal` and then `Project Grants`.
[Grant all roles of the Project](/guides/manage/console/projects-overview#granted-projects-b2b) to the organization `demo-customer.$CUSTOM_DOMAIN.zitadel.cloud`.
### Authorization
@@ -22,12 +22,12 @@ In a B2B use case, an organization typically represents a business partner who r
### Projects within Organizations
You can use **Projects** within your organization to manage the security context of closely related components, such as roles, grants, and authorizations for multiple applications. You can set up multiple projects within a single organization.
### Organization Grants
### Project Grants
ZITADEL allows you to give *other* organizations permission to manage certain aspects of a project within *your* organization.
For example, you could set up a project with roles that define access to your software, but allow a partner organization to allocate those roles to their own users independently. As a service provider, this allows you to establish a self-service culture for your business customers.
![Organization Grant](../../../../public/img/concepts/objects/organization_grants.png)
![Project Grant](../../../../public/img/concepts/objects/project_grants.png)
## Managing Organizations
@@ -23,7 +23,7 @@ Please also consult our guide on [Solution Scenarios](/guides/solution-scenarios
Some solutions, that offer multi-tenancy, require you to copy applications and settings to each tenant and manage changes individually.
ZITADEL works differently by using [Granted Projects](/concepts/structure/granted_projects).
Projects can be granted to [Organization](/guides/manage/console/organizations-overview#organization-grants) or even to individual users.
Projects can be granted to [Organization](/guides/manage/console/organizations-overview#project-grants) or even to individual users.
You can think of it as a logical link to a Project, which can be used by the receiving Organization or User as if it was their own project, except privileges to modify the Project itself.
Delegated access management is a great way of keeping the management overhead low and enabling [self-service](/concepts/features/selfservice#managers-in-delegation) for Organizations to manage their own Settings and Authorizations.
@@ -101,7 +101,7 @@ You do have two possibilities.
### Give the needed permission to the organization
1. Go to the organization, who owns the project, where the user tries to authenticate.
2. Navigate to the grants page of the needed project
2. Navigate to the Project Grants page of the needed project
3. Click on the "New" button
4. Search for the organization to which you want to grant the project (e.g Organization B)
5. Select the roles you want to grant

Before

Width:  |  Height:  |  Size: 324 KiB

After

Width:  |  Height:  |  Size: 324 KiB