chore: naming inconsistency application (#11431)

This commit is contained in:
Wim Van Laer
2026-02-04 07:20:07 +00:00
committed by GitHub
parent 04c58c5b3f
commit 61d4060df3
96 changed files with 22550 additions and 22674 deletions
@@ -13,7 +13,7 @@ import AppType from "./_application-types.mdx";
## What is an application?
Applications are the entry point to your [Project Overview](/guides/manage/console/projects-overview)
. Users either login into one of your clients (Frontend) and interact with them directly, or use one of your APIs (Backend).
. Users either login into one of your applications (Frontend) and interact with them directly, or use one of your APIs (Backend).
All applications within a project share the same **Roles** and **Authorizations**. This means you define a role once (e.g., `admin`) on the Project level, and it applies across all your web, mobile, and API applications.
@@ -23,7 +23,6 @@ To access your applications, navigate to your Project in the Management Console
alt="Granted project"
src="/docs/img/guides/console/applications.png"
width="750px"
/>
## Create an Application
@@ -38,7 +37,7 @@ To add an application to your project, click on the **New** button and select yo
## Application Types
ZITADEL offers five client types to cover different architectural patterns:
ZITADEL offers five application types to cover different architectural patterns:
<AppType components={props.components} />
@@ -11,7 +11,7 @@ import AppType from "./_application-types.mdx";
## What is an application?
Applications are the entry point to your project.
Users either login into one of your clients and interact with them directly or use one of your APIs.
Users either login into one of your applications and interact with them directly or use one of your APIs.
All applications share the roles and authorizations of their project.
To access your applications, navigate to your project and select your application.
@@ -34,7 +34,7 @@ To add an application to your project, click on the add button and select your a
## Application Types
At the moment ZITADEL offers five client types:
At the moment ZITADEL offers five application types:
<AppType components={props.components} />
@@ -154,7 +154,7 @@ The Login Policy defines how the login process should look like and which authen
### Default Redirect URI
The Default Redirect URI will be used, if a user calls the login page directly.
More specifically, typically a client will initiate login with an auth request.
More specifically, typically an application will initiate login with an auth request.
The auth request contains a client-id and a redirect uri, that must match the configuration in ZITADEL.
If there is no [auth request](https://zitadel.com/playgrounds/oidc), users will be redirected to the Default Redirect URI, which is by default `https://${CUSTOM_DOMAIN}/ui/console/`
@@ -20,7 +20,7 @@ In a B2B use case, an organization typically represents a business partner who r
## Structure and Delegation
### 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 clients. You can set up multiple projects within a single organization.
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
ZITADEL allows you to give *other* organizations permission to manage certain aspects of a project within *your* organization.
@@ -12,7 +12,7 @@ import ProjectDescription from "../../../concepts/structure/_project_description
### Example
If you'd build a Point of Sales Platform, you would have one Project (maybe called `POS`) and all your applications (one Webapplication for administration, and your mobile applications for your users iOS and Android), would be part of it.
You would have to create roles for administration and your clients in this very project, and then create authorizations based on them.
You would have to create roles for administration and your applications in this very project, and then create authorizations based on them.
![](../../../../public/img/guides/console/posproject.png)
@@ -28,7 +28,7 @@ The **Group** is for making multiple roles selectable more easy.
<img src="/docs/img/guides/console/roles.png" width="750px" alt="Roles" />
> The role client is for an other application of the project `POS`, as all possible roles from your POS applications are defined in your project.
> The role client is for another application of the project `POS`, as all possible roles from your POS applications are defined in your project.
## Authorizations