chore: naming inconsistency application (#11431)

2026-10-18 05:52:51 +00:00 · 2026-02-04 07:20:07 +00:00
parent 04c58c5b3f
commit 61d4060df3
96 changed files with 22550 additions and 22674 deletions
@@ -104,4 +104,4 @@ Will be established as soon as the goal described above is reached.

 This chapter provides a table linking to the detailed test results.

-<DocCardList />
+<DocCardList/>
@@ -111,7 +111,7 @@ API Reference:

 ### Management

-The management API is as the name states the interface where systems can mutate IAM objects like, organizations, projects, clients, users and so on if they have the necessary access rights.
+The management API is as the name states the interface where systems can mutate IAM objects like, organizations, projects, applications, users and so on if they have the necessary access rights.
 To identify the current organization you can send a header `x-zitadel-orgid` or if no header is set, the organization of the authenticated user is set.

 </div>
@@ -49,7 +49,7 @@ This section details the migrated resources, including any breaking changes and
 ### General Changes

 #### Sunsetting OpenAPI/REST Support in Favor of Connect RPC
-While our v1 API already offered gRPC, it also provided a parallel REST/OpenAPI interface for clients who preferred making traditional HTTP calls.
+While our v1 API already offered gRPC, it also provided a parallel REST/OpenAPI interface for applications who preferred making traditional HTTP calls.

 In our v2 API, we are consolidating our efforts to provide a more streamlined and efficient development experience.
 The primary change is the removal of the OpenAPI/REST interface.
@@ -62,10 +62,10 @@ For teams already using gRPC, your transition will be minimal.
 For teams who were using the v1 REST API, migrating to v2 will involve adopting one of the following methods:

 - Native gRPC: For the highest performance and to leverage features like bi-directional streaming.
- Connect RPC: For making CRUD-like (Create, Read, Update, Delete) calls over HTTP. This is the recommended path for most clients migrating from our v1 REST API.
+- Connect RPC: For making CRUD-like (Create, Read, Update, Delete) calls over HTTP. This is the recommended path for most applications migrating from our v1 REST API.

 A significant advantage of this new architecture remains the automatic generation of client libraries.
-Based on our .proto service definitions, you can generate type-safe clients for your specific programming language, whether you use native gRPC or Connect RPC.
+Based on our .proto service definitions, you can generate type-safe applications for your specific programming language, whether you use native gRPC or Connect RPC.
 This eliminates the need to write boilerplate code for handling HTTP requests and parsing responses, leading to a more streamlined and less error-prone development process.

 #### Contextual Information in the Request Body
@@ -3,7 +3,7 @@ title: Claims in ZITADEL
 sidebar_label: Claims
 ---

-ZITADEL asserts claims on different places according to the corresponding specifications or project and clients settings.
+ZITADEL asserts claims on different places according to the corresponding specifications or project and applications settings.
 Please check below the matrix for an overview where which scope is asserted.

 | Claims                                            | Userinfo       | Introspection                           | ID Token                                        | Access Token                                         |
@@ -63,7 +63,7 @@ Please check below the matrix for an overview where which scope is asserted.
 | given_name         | `Road`                                                         | First name of the subject                                                                                                                                                  |
 | given_name         | `Road`                                                         | First name of the subject                                                                                                                                                  |
 | iat                | `1311280970`                                                   | Time of the token was issued at (as unix time)                                                                                                                             |
-| iss                | `${CUSTOM_DOMAIN}`                                               | Issuing domain of a token                                                                                                                                                  |
+| iss                | `${CUSTOM_DOMAIN}`                                             | Issuing domain of a token                                                                                                                                                  |
 | jti                | `69234237813329048`                                            | Unique id of the token                                                                                                                                                     |
 | locale             | `en`                                                           | Language from the subject                                                                                                                                                  |
 | name               | `Road Runner`                                                  | The subjects full name                                                                                                                                                     |
@@ -110,9 +110,9 @@ ZITADEL reserves some claims to assert certain data. Please check out the [reser
 |:--------------------------------------------------|:---------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | urn:zitadel:iam:action:\{actionname}:log          | `{"urn:zitadel:iam:action:appendCustomClaims:log": ["test log", "another test log"]}`                    | This claim is set during Actions as a log, e.g. if two custom claims with the same keys are set.                                                                                                                                         |
 | urn:zitadel:iam:org:domain:primary:\{domainname}  | `{"urn:zitadel:iam:org:domain:primary": "acme.ch"}`                                                      | This claim represents the primary domain of the organization the user belongs to.                                                                                                                                                        |
-| urn:zitadel:iam:org:project:roles                 | `{"urn:zitadel:iam:org:project:roles": [ {"user": {"id1": "acme.zitade.ch", "id2": "caos.ch"} } ] }`     | When roles are asserted, ZITADEL does this by providing the `id` and `primaryDomain` below the role. This gives you the option to check in which organization a user has the role on the current project (where your client belongs to). |
+| urn:zitadel:iam:org:project:roles                 | `{"urn:zitadel:iam:org:project:roles": [ {"user": {"id1": "acme.zitade.ch", "id2": "caos.ch"} } ] }`     | When roles are asserted, ZITADEL does this by providing the `id` and `primaryDomain` below the role. This gives you the option to check in which organization a user has the role on the current project (where your application belongs to). |
 | urn:zitadel:iam:org:project:\{projectid}:roles    | `{"urn:zitadel:iam:org:project:id3:roles": [ {"user": {"id1": "acme.zitade.ch", "id2": "caos.ch"} } ] }` | When roles are asserted, ZITADEL does this by providing the `id` and `primaryDomain` below the role. This gives you the option to check in which organization a user has the role on a specific project.                                 |
 | urn:zitadel:iam:user:metadata                     | `{"urn:zitadel:iam:user:metadata": [ {"key": "VmFsdWU=" } ] }`                                           | The metadata claim will include all metadata of a user. The values are base64 encoded.                                                                                                                                                   |
-| urn:zitadel:iam:user:resourceowner:id             | `{"urn:zitadel:iam:user:resourceowner:id": "orgid"}`                                                     | This claim represents the user's organization ID.                                                                                                                                                             |
-| urn:zitadel:iam:user:resourceowner:name           | `{"urn:zitadel:iam:user:resourceowner:name": "ACME"}`                                                    | This claim represents the user's organization's name.                                                                                                                                                           |
-| urn:zitadel:iam:user:resourceowner:primary_domain | `{"urn:zitadel:iam:user:resourceowner:primary_domain": "acme.ch"}`                                       | This claim represents the user's organization's primary domain.                                                                                                                                                 |
+| urn:zitadel:iam:user:resourceowner:id             | `{"urn:zitadel:iam:user:resourceowner:id": "orgid"}`                                                     | This claim represents the user's organization ID.                                                                                                                                                                                        |
+| urn:zitadel:iam:user:resourceowner:name           | `{"urn:zitadel:iam:user:resourceowner:name": "ACME"}`                                                    | This claim represents the user's organization's name.                                                                                                                                                                                    |
+| urn:zitadel:iam:user:resourceowner:primary_domain | `{"urn:zitadel:iam:user:resourceowner:primary_domain": "acme.ch"}`                                       | This claim represents the user's organization's primary domain.                                                                                                                                                                          |
@@ -44,7 +44,7 @@ authenticate the user in exchange for an authorization_code (authorization code
 ### Required request parameters

 | Parameter     | Description                                                                                                                                       |
-| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
 | client_id     | The id of your client as shown in Console.                                                                                                        |
 | redirect_uri  | Callback uri of the authorization request where the code or tokens will be sent to. Must match exactly one of the preregistered in Console.       |
 | response_type | Determines whether a `code`, `id_token token` or just `id_token` will be returned. Most use cases will need `code`. See flow guide for more info. |
@@ -94,7 +94,7 @@ no additional parameters required
 ### Additional parameters

 | Parameter     | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | id_token_hint | Valid `id_token` (of an existing session) used to identity the subject. **SHOULD** be provided when using prompt `none`.                                                                                                                                                                                                                                                                                                                                                                       |
 | login_hint    | A valid logon name of a user. Will be used for username inputs or preselecting a user on `select_account`. Be sure to encode the hint correctly using url encoding (especially when using `+` or alike in the loginname)                                                                                                                                                                                                                                                                       |
 | max_age       | Seconds since the last active successful authentication of the user                                                                                                                                                                                                                                                                                                                                                                                                                            |
@@ -124,7 +124,7 @@ As per [OpenID Connect Core 1.0, Section 3.1.2.1](https://openid.net/specs/openi
 When your `response_type` was `code` and no error occurred, the following response will be returned:

 | Property | Description                                                                   |
-| -------- | ----------------------------------------------------------------------------- |
+|----------|-------------------------------------------------------------------------------|
 | code     | Opaque string which will be necessary to request tokens on the token endpoint |
 | state    | Unmodified `state` parameter from the request                                 |

@@ -133,7 +133,7 @@ When your `response_type` was `code` and no error occurred, the following respon
 When your `response_type` was either `id_token` or `id_token token` and no error occurred, the following response will be returned:

 | Property     | Description                                                                           |
-| ------------ | ------------------------------------------------------------------------------------- |
+|--------------|---------------------------------------------------------------------------------------|
 | access_token | Only returned if `response_type` included `token`                                     |
 | expires_in   | Number of second until the expiration of the `access_token`                           |
 | id_token     | An `id_token` of the authorized user                                                  |
@@ -265,6 +265,7 @@ curl --request POST \
 ```

 #### Successful JWT profile response
+
 | Property     | Description                                                                           |
 | ------------ | ------------------------------------------------------------------------------------- |
 | access_token | An `access_token` as JWT or opaque token                                              |
@@ -331,6 +332,7 @@ Send a `client_assertion` as JWT for us to validate the signature against the re
 </Tabs>

 #### Successful refresh token response
+
 | Property      | Description                                                                           |
 | ------------- | ------------------------------------------------------------------------------------- |
 | access_token  | An `access_token` as JWT or opaque token                                              |
@@ -379,6 +381,7 @@ curl --request POST \
 ```

 #### Successful client credentials response
+
 | Property     | Description                                                                           |
 | ------------ | ------------------------------------------------------------------------------------- |
 | access_token | An `access_token` as JWT or opaque token                                              |
@@ -440,6 +443,7 @@ Send a `client_assertion` as JWT for us to validate the signature against the re
 </Tabs>

 #### Successful token exchange response
+
 <TokenExchangeResponse components={props.components}  />

 #### Token types
@@ -537,6 +541,7 @@ Additionally and depending on the granted scopes, information about the authoriz
 Check the [Claims](./claims) page if a specific claims might be returned and for detailed description.

 ### Error response
+
 If the authorization fails, an HTTP 401 with `invalid_client` will be returned.

 ## userinfo_endpoint
@@ -554,6 +559,7 @@ curl --request GET \
 ```

 ### Successful userinfo response
+
 If the `access_token` is valid, the information about the user depending on the granted scopes is returned.
 Check the [Claims](./claims) page if a specific claims might be returned and for detailed description.

@@ -3,17 +3,17 @@ title: GRPC Status Codes in ZITADEL
 sidebar_label: GRPC Status Codes
 ---

-| GRPC Number    | GRPC Code                 | HTTP Status Code | HTTP Status Text             |Description                                                                                                                           |
-| :---------| :------------------- | ------------------ | ------------- | -------------------------------------------------------------------------------------------------------------------------- |
-| 0         | OK                   | 200 |OK              | Not an error; returned on success.                              |
-| 2         | UNKNOWN              | 500 |Internal        | Unknown error, this is sent if the error could not be identified as one of the errors described below |
-| 3         | INVALID_ARGUMENT     | 400 |Bad Request     | The client specified an invalid argument. Note that this differs from FAILED_PRECONDITION. INVALID_ARGUMENT indicates arguments that are problematic regardless of the state of the system (e.g., a malformed file name).                                                              |
-| 4         | DEADLINE_EXCEEDED    | 504 |Gateway Timeout | The deadline expired before the operation could complete.                                                               |
-| 5         | NOT_FOUND            | 404 |Not found       | Some requested entity (e.g. user or project) was not found.                                                            |
-| 6         | ALREADY_EXISTS       | 409 |Conflict        | The entity that a client attempted to create (e.g. user or project) already exists.                                                             |
-| 7         | PERMISSION_DENIED    | 403 |Forbidden       |The caller does not have permission to execute the specified operation.                                                              |
-| 9         | FAILED_PRECONDITION  | 400 |Bad Request     | The operation was rejected because the system is not in a state required for the operation's execution. e.g a project that is already deactivated, should be deactivated |
-| 12        | UNIMPLEMENTED        | 501 |Not Implemented |The operation is not implemented or is not supported/enabled in this service.                                                              |
-| 13        | INTERNAL             | 500 |Internal        |Internal errors. This means that some invariants expected by the underlying system have been broken. This error code is reserved for serious errors. |
-| 14        | UNAVAILABLE          | 503 |Service Unavailable | The service is currently unavailable.                                                              |
-| 16        | UNAUTHENTICATED      | 401 |Unauthorized    |The request does not have valid authentication credentials for the operation.      |
+| GRPC Number | GRPC Code           | HTTP Status Code | HTTP Status Text    | Description                                                                                                                                                                                                               |
+|:------------|:--------------------|------------------|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0           | OK                  | 200              | OK                  | Not an error; returned on success.                                                                                                                                                                                        |
+| 2           | UNKNOWN             | 500              | Internal            | Unknown error, this is sent if the error could not be identified as one of the errors described below                                                                                                                     |
+| 3           | INVALID_ARGUMENT    | 400              | Bad Request         | The client specified an invalid argument. Note that this differs from FAILED_PRECONDITION. INVALID_ARGUMENT indicates arguments that are problematic regardless of the state of the system (e.g., a malformed file name). |
+| 4           | DEADLINE_EXCEEDED   | 504              | Gateway Timeout     | The deadline expired before the operation could complete.                                                                                                                                                                 |
+| 5           | NOT_FOUND           | 404              | Not found           | Some requested entity (e.g. user or project) was not found.                                                                                                                                                               |
+| 6           | ALREADY_EXISTS      | 409              | Conflict            | The entity that a client attempted to create (e.g. user or project) already exists.                                                                                                                                       |
+| 7           | PERMISSION_DENIED   | 403              | Forbidden           | The caller does not have permission to execute the specified operation.                                                                                                                                                   |
+| 9           | FAILED_PRECONDITION | 400              | Bad Request         | The operation was rejected because the system is not in a state required for the operation's execution. e.g a project that is already deactivated, should be deactivated                                                  |
+| 12          | UNIMPLEMENTED       | 501              | Not Implemented     | The operation is not implemented or is not supported/enabled in this service.                                                                                                                                             |
+| 13          | INTERNAL            | 500              | Internal            | Internal errors. This means that some invariants expected by the underlying system have been broken. This error code is reserved for serious errors.                                                                      |
+| 14          | UNAVAILABLE         | 503              | Service Unavailable | The service is currently unavailable.                                                                                                                                                                                     |
+| 16          | UNAUTHENTICATED     | 401              | Unauthorized        | The request does not have valid authentication credentials for the operation.                                                                                                                                             |
@@ -25,7 +25,7 @@ ZITADEL uses the following principles when handling Secrets across their lifecyc

 ## Secrets Storage

-By default ZITADEL stores secrets from its users, clients as well as its generated secrets like signing keys in the database.
+By default ZITADEL stores secrets from its users, applications as well as its generated secrets like signing keys in the database.
 To protect the secrets against extraction from database as well as database dumps they are encrypted with AES256.

 <Callout>
@@ -73,7 +73,7 @@ Read more about [Service Users](/guides/integrate/service-users/authenticate-ser
 ## Logout

 Users can terminate the session for all their users (logout).
-A client can also implement this by calling the [specific endpoint](/apis/openidoauth/endpoints#end-session-endpoint).
+An application can also implement this by calling the [specific endpoint](/apis/openidoauth/endpoints#end-session-endpoint).

 ## Profile

@@ -8,7 +8,7 @@ ZITADEL is organized around the idea that:

 Organizations in ZITADEL are therefore comparable to tenants of a system or organizational units of a directory based system.

-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 your 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 your organization.

 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.

@@ -6,12 +6,12 @@ sidebar_label: Applications
 import AppType from "../../guides/manage/console/_application-types.mdx";

 Applications are the entry point to your project.
-[Users](./users) either login into one of your clients and interact with them directly or use one of your APIs.
+[Users](./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](./projects).

 ## Supported application types

-ZITADEL supports the following client types:
+ZITADEL supports the following application types:

 <AppType components={props.components} />

@@ -30,11 +30,11 @@ Continue and create the application.

 ### Client ID

-After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID, as you will need it to configure your Angular client.
+After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID, as you will need it to configure your Angular application.

 ## Angular setup

-Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Angular client.
+Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Angular application.

 ### Install Angular dependencies

@@ -40,13 +40,13 @@ Continue and create the application.

 ### Client ID

-After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID, as you will need it to configure your Go client.
+After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID, as you will need it to configure your Go application.

 ![Create app in management console - copy client_id](../../../public/img/go/app-create-clientid.png)

 ## Go setup

-Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Go client.
+Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Go application.

 ### Install ZITADEL Go SDK

@@ -40,13 +40,13 @@ Continue and create the application.

 ### Client ID

-After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID, as you will need it to configure your Java client.
+After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID, as you will need it to configure your Java application.

 ![Create app in management console - copy client_id](../../../public/img/java-spring/app-create-clientid.png)

 ## Spring setup

-Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Spring client.
+Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Spring application.
 This guide will reference the [example repository](https://github.com/zitadel/zitadel-java) and explain the necessary steps taken in there.
 If your starting from scratch, you can use the Spring Initializer with the [following setup](https://start.spring.io/#!type=maven-project&language=java&platformVersion=3.2.1&packaging=jar&jvmVersion=17&dependencies=web,thymeleaf,security,oauth2-client,lombok) as a base.

@@ -94,7 +94,7 @@ Replace the values as follows

 `NEXTAUTH_URL`: Base url of this demo app (B2B portal); runs per default on [http://localhost:3000](http://localhost:3000)

-`NEXT_PUBLIC_ZITADEL_ISSUER`: The url to your zitadel instance. When using zitadel.cloud for this demo you can find the domain of your ZITADEL instance in the customer portal. You can also find this information by going to your application `portal-web` and click 'URLs' in the navigation. The variable is prefixed with `NEXT_PUBLIC_` such that it can be accessed from the client.
+`NEXT_PUBLIC_ZITADEL_ISSUER`: The url to your zitadel instance. When using zitadel.cloud for this demo you can find the domain of your ZITADEL instance in the customer portal. You can also find this information by going to your application `portal-web` and click 'URLs' in the navigation. The variable is prefixed with `NEXT_PUBLIC_` such that it can be accessed from the application.

 `ZITADEL_API`: URL of the Management API. Typically the same as `ZITADEL_ISSUER`.

@@ -56,7 +56,7 @@ Now that you have your web application configured on the ZITADEL side, you can g

 ### Configuration

-NextAuth.js exposes a REST API which is used by your client.
+NextAuth.js exposes a REST API which is used by your application.
 To setup your configuration, create a file called `src/lib/auth.ts`.
 You can directly import the ZITADEL provider from [next-auth](https://next-auth.js.org/providers/zitadel).

@@ -38,11 +38,11 @@ Continue and create the application.

 ### Copy Client ID

-After successful creation of the app, make sure copy the client ID, as you will need it to configure your React client.
+After successful creation of the app, make sure copy the client ID, as you will need it to configure your React application.

 ## Create a project role "admin" and assign it to your user

-Also note the projects resource ID, as you will need it to configure your React client.
+Also note the projects resource ID, as you will need it to configure your React application.

 ![](../../../public/img/react/project-role.png)

@@ -52,7 +52,7 @@ If you want to read your users roles from user info endpoint, make sure to enabl

 ## React setup

-Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your React client.
+Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your React application.

 ### Install React dependencies

@@ -71,7 +71,7 @@ The secret will not be displayed again, but you can regenerate one if you loose

 ## Setup new Symfony application

-Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Symfony client.
+Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Symfony application.
 The example is build on a [generated Symfony web app](https://symfony.com/doc/current/setup.html#creating-symfony-applications), using the following command:

 <Callout>
@@ -39,13 +39,13 @@ Continue and create the application.
 ### Refresh Token and Client ID

 After successful creation of the app, make sure you tick the checkbox to enable refresh tokens.
-Also copy the client ID, as you will need it to configure your Vue client.
+Also copy the client ID, as you will need it to configure your Vue application.

 ![](../../../public/img/vue/tick-refresh-token.png)

 ## Create a project role "admin" and assign it to your user

-Also note the projects resource ID, as you will need it to configure your Vue client.
+Also note the projects resource ID, as you will need it to configure your Vue application.

 ![](../../../public/img/vue/project-role.png)

@@ -53,7 +53,7 @@ Also note the projects resource ID, as you will need it to configure your Vue cl

 ## Vue setup

-Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Vue client.
+Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Vue application.

 ### Install Vue dependencies

@@ -52,7 +52,7 @@ And make sure to download it, as you won't be able to retrieve it again.

 ![](../../../public/img/go/api-download_key.png)

-Now we need to create a *Personal Access Token* to authenticate the client requests.
+Now we need to create a *Personal Access Token* to authenticate the application requests.

 On the user view, switch to *Service Users* and create a new one.

@@ -25,13 +25,13 @@ Select Basic Auth for authenticating at the Introspection Endpoint.

 ![Create app in management console](../../../public/img/java-spring/api-create-auth.png)

-After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID and secret, as you will need it to configure your Java client.
+After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID and secret, as you will need it to configure your Java application.

 ![Create api key in management console](../../../public/img/java-spring/api-create-clientid-secret.png)

 ## Spring Setup

-Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Spring client.
+Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Spring application.
 This guide will reference the [example repository](https://github.com/zitadel/zitadel-java) and explain the necessary steps taken in there.
 If your starting from scratch, you can use the Spring Initializer with the [following setup](https://start.spring.io/#!type=maven-project&language=java&platformVersion=3.2.1&packaging=jar&jvmVersion=17&dependencies=web,lombok,oauth2-resource-server) as a base.

@@ -294,5 +294,5 @@ the [Sent information Response](./usage#sent-information-response) payload descr
 ## Conclusion

 You have successfully set up a target and execution to manipulate API responses in your ZITADEL instance.
-This feature can now be used to add necessary information for clients including the new login UI.
+This feature can now be used to add necessary information for applications including the new login UI.
 Find more information about the actions feature in the [API documentation](/concepts/features/actions_v2).
@@ -4,7 +4,7 @@ sidebar_label: Back-Channel Logout
 ---

 The Back-Channel Logout implements [OpenID Connect Back-Channel Logout 1.0](https://openid.net/specs/openid-connect-backchannel-1_0.html)
-and can be used to notify clients about session termination at the OpenID Provider. This guide will explain how
+and can be used to notify applications about session termination at the OpenID Provider. This guide will explain how
 back-channel logout is implemented inside ZITADEL and gives some usage examples.

 <Callout type="info">
@@ -24,8 +24,8 @@ understanding on the following topics before starting with this guide:
 ## Concept

 ZITADEL provides the possibility for OpenID Connect clients to be notified about the session termination, for example
-if a user signs out from another client using the same SSO session.
-This allows the client to also invalidate the user's session without the need for an active browser session.
+if a user signs out from another application using the same SSO session.
+This allows the application to also invalidate the user's session without the need for an active browser session.

 ![](../../../public/img/guides/back-channel-logout/back-channel-logout-flow.png)

@@ -57,7 +57,7 @@ provides the possibility to match the exact SSO session, which was terminated.

 ### Client

-To enable the back-channel logout on a client, they simply need to register a `backchannel_logout_uri` as part of their
+To enable the back-channel logout on an application, they simply need to register a `backchannel_logout_uri` as part of their
 configuration, e.g. [creating an OIDC application](https://zitadel.com/docs/reference/api/management/management-service-add-oidc-app).

 As soon as the URI is set, every new authorization request will register a back-channel notification to be sent once
@@ -66,7 +66,7 @@ the session is terminated by a user sign out.
 ## Back-Channel Request

 When the session is terminated, ZITADEL will send back-channel logout requests asynchronously to every registered
-client of the corresponding session.
+application of the corresponding session.
 The request is an `application/x-www-form-urlencoded` POST request to the registered URI including a `logout_token`
 parameter in the body.

@@ -25,7 +25,7 @@ You will have to paste it in the Entra ID Client later.

 You need to have access to an Entra ID Tenant. If you do not yet have one follow [this guide from Microsoft](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-create-new-tenant) to create one for free.

-### Register a new client
+### Register a new application

 1. Browse to the [App registration menus create dialog](https://portal.azure.com/#view/Microsoft_AAD_RegisteredApps/CreateApplicationBlade/quickStartType~/null/isMSAApp~/false) to create a new app.
 2. Give the application a name and choose who should be able to login (Single-Tenant, Multi-Tenant, Personal Accounts, etc.) This setting will also have an impact on how to configure the provider later on in ZITADEL.
@@ -29,7 +29,7 @@ You will have to paste this URL in your external OIDC provider's application con

 1. Log in to your external OIDC Provider's dashboard or management console.
 2. Navigate to the applications, clients, or integrations section (name may vary depending on your provider).
-3. Create a new application or client and select "OIDC" or "OpenID Connect" as the type.
+3. Create a new application and select "OIDC" or "OpenID Connect" as the type.
 4. Set a name for the application.
 5. [Paste the ZITADEL Callback URL you copied before](#open-the-generic-oidc-provider-template) into the "redirect URIs" or "sign-in redirect URIs" field.
 6. Save or copy the generated **Client ID** and **Client Secret**.
@@ -26,7 +26,7 @@ You will have to paste it in the Google Cloud Platform later.

 ## Google Configuration

-### Register a new client
+### Register a new application

 1. Go to the Google Cloud Platform and choose your project: [https://console.cloud.google.com/apis/credentials](https://console.cloud.google.com/apis/credentials)
 2. Click on "+ CREATE CREDENTIALS" and choose "OAuth client ID"
@@ -130,7 +130,7 @@ Example Response POST-binding:
 }
 ```

-Which expects your client to do a POST call to the URL `https://myapp.example.com/acs` with the payload containing the following attributes:
+Which expects your application to do a POST call to the URL `https://myapp.example.com/acs` with the payload containing the following attributes:

 ```
 RelayState: "CncN92gdF6is7bak63thXOsn0MmJn7CLQeGKWaXZo2L8nJN0sPEHbb4I",
@@ -154,7 +154,7 @@ Example Response Redirect-binding:
 }
 ```

-Which expects your client to redirect to the url 'https://myapp.example.com/acs?RelayState=...&SAMLResponse=...' with all information as URL parameters.
+Which expects your application to redirect to the url 'https://myapp.example.com/acs?RelayState=...&SAMLResponse=...' with all information as URL parameters.

 ### SAML Endpoints

@@ -225,7 +225,7 @@ This strategy aims to fulfill the following requirements:
 2. Applications have enough time to see the next activated web key on the [JWKS](#json-web-key-set) endpoint.
 3. Web keys are kept long enough to cover the access and ID token validity of 24 hours.
 4. Web keys are kept long enough to to allow usage of the `id_token_hint` for at least 3 months.
-  Users that haven't logged in / refreshed tokens with the client app for that period,
+  Users that haven't logged in / refreshed tokens with the client application for that period,
  will need to re-enter their username.

 When the instance was created, resp. the feature was rolled out, the instance got two keys with the first one activated. When this feature becomes generally available, instance creation will setup the first two keys in the same way. So the initial state always looks like this:
@@ -40,7 +40,7 @@ In order to access role information via the token you must include the right aud

 An important concept in OpenID Connect (OIDC) is the 'audience' (`aud`) claim, which is part of the token payload. The `aud` claim identifies who or what this token is intended for. If the recipient (e.g., a resource server) does not identify itself with a value in the `aud` claim when this claim is present, then the token must be rejected.

-The audience is essential in multi-tier systems, where you may authenticate with one client (in one project) but access resources from another client (in a different project) or when you are accessing ZITADEL’s management APIs. Without the correct audience in your token, you will run into errors, such as the ‘Invalid audience’ error in ZITADEL.
+The audience is essential in multi-tier systems, where you may authenticate with one application (in one project) but access resources from another application (in a different project) or when you are accessing ZITADEL’s management APIs. Without the correct audience in your token, you will run into errors, such as the ‘Invalid audience’ error in ZITADEL.

 You can determine the audience in two ways:

@@ -51,7 +51,7 @@ ZITADEL supports two primary authentication methods for service users:
 * ZITADEL validates the signature using the service user's public key.
 * JWTs can include expiration dates and scopes to control access.

-Follow our guide on using [private key JWT client authentication](./private-key-jwt) to get started authenticating service users and clients.
+Follow our guide on using [private key JWT client authentication](./private-key-jwt) to get started authenticating service users and applications.

 #### Benefits of private key JWT authentication

@@ -74,7 +74,7 @@ Follow our guide on using [private key JWT client authentication](./private-key-
 * Presents a client ID and client secret associated with the service user.
 * Simpler than the JWT profile in specific scenarios.

-Follow our guide on using [client credentials grant](./client-credentials) to get started authenticating service users and clients.
+Follow our guide on using [client credentials grant](./client-credentials) to get started authenticating service users and applications.

 This method is still available in ZITADEL but is generally considered less secure than JWT due to:

@@ -86,7 +86,7 @@ This method is still available in ZITADEL but is generally considered less secur
 * **Ready-to-use tokens:** Generated for specific service users and can be directly included in the authorization header of API requests.
 * **Currently available only for machine users** (service users) and not regular human users.

-Follow our guide on using [personal access tokens](./personal-access-token) to get started authenticating service users and clients.
+Follow our guide on using [personal access tokens](./personal-access-token) to get started authenticating service users and applications.

 PAT offer some benefits, such as:

@@ -12,7 +12,7 @@ Prerequisites:
 - Existing ZITADEL instance, organization, and project. Follow our [get started](/guides/start/quickstart) guide to get started. If not present follow [this guide](/guides/start/quickstart)
 - Existing Cloudflare account and [team domain](https://developers.cloudflare.com/cloudflare-one/glossary/#team-domain)

-## Create the client in ZITADEL
+## Create the application in ZITADEL

 <CreateApp components={props.components}  appType="web" authType="code" appName="Cloudflare" redirectURI="https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/callback"/>

@@ -23,7 +23,7 @@ Make sure to enable "User Info inside ID Token" on your application settings.
 ![](../../../../public/img/guides/integrate/services/user-info-inside-id-token.png)

 <Callout>
-Cloudflare will return an error "User email was not returned. API permissions are likely incorrect". Enable to send the user information inside the token on your client settings.
+Cloudflare will return an error "User email was not returned. API permissions are likely incorrect". Enable to send the user information inside the token on your application settings.
 </Callout>

 ## Configure Cloudflare Zero Trust Authentication
@@ -1,17 +1,17 @@
 Upon successful introspection, regardless of the token type or introspection method, a response with the boolean `active` is returned, indicating if the provided token is active and if the requesting client is part of the token audience. If `active` is true, further information will be provided:

-| **Property** | **Description** |
-| --- | --- |
-| `aud` | The audience of the token |
-| `client_id` | The client_id of the application the token was issued to |
-| `exp` | Time the token expires (as unix time) |
-| `iat` | Time the token was issued at (as unix time) |
-| `iss` | Issuer of the token |
-| `jti` | Unique id of the token |
-| `nbf` | Time the token must not be used before (as unix time) |
-| `scope` | Space delimited list of scopes granted to the token |
-| `token_type` | Type of the inspected token. Value is always Bearer |
-| `username` | ZITADEL's login name of the user. Consists of username@primarydomain |
+| **Property** | **Description**                                                      |
+|--------------|----------------------------------------------------------------------|
+| `aud`        | The audience of the token                                            |
+| `client_id`  | The client_id of the application the token was issued to             |
+| `exp`        | Time the token expires (as unix time)                                |
+| `iat`        | Time the token was issued at (as unix time)                          |
+| `iss`        | Issuer of the token                                                  |
+| `jti`        | Unique id of the token                                               |
+| `nbf`        | Time the token must not be used before (as unix time)                |
+| `scope`      | Space delimited list of scopes granted to the token                  |
+| `token_type` | Type of the inspected token. Value is always Bearer                  |
+| `username`   | ZITADEL's login name of the user. Consists of username@primarydomain |

 Depending on the granted scopes, additional information about the authorized user is provided.

@@ -40,9 +40,9 @@ Install the package via nuget
 dotnet add package Zitadel.Api
 ```

-### Create example client
+### Create example application

-Change the program.cs file to the content below. This will create a client for the management api and call its `GetMyUsers` function.
+Change the program.cs file to the content below. This will create a application for the management api and call its `GetMyUsers` function.
 The SDK will make sure you will have access to the API by retrieving a Bearer Token using JWT Profile with the provided scopes (`openid` and `urn:zitadel:iam:org:project:id:zitadel:aud`).

 Make sure to fill the const `apiUrl`, and `personalAccessToken` with your own instance data. The used vars below are from a test instance, to show you how it should look.
@@ -86,7 +86,7 @@ result = await client.GetMyUserAsync(new());
 Console.WriteLine($"User: {result.User}");
 ```

-### Test client
+### Test application

 After you have configured everything correctly, you can simply start the example by:

@@ -35,9 +35,9 @@ You need to add the SDK into Go Modules by:
 go get -u github.com/zitadel/zitadel-go/v3
 ```

-### Create example client
+### Create example application

-Create a new go file with the content below. This will create a client and call its `GetMyOrg` function on the ManagementService.
+Create a new go file with the content below. This will create a application and call its `GetMyOrg` function on the ManagementService.
 The SDK will make sure you will have access to the API by retrieving a Bearer Token using JWT Profile with the provided scopes (`openid` and `urn:zitadel:iam:org:project:id:zitadel:aud`).

 ```go reference
@@ -82,5 +82,5 @@ Now you can proceed implementing our APIs by adding more calls or using a differ
 api.SessionService().CreateSession(ctx, &session.CreateSessionRequest{})
 ```
 Checkout more [examples from the SDK](https://github.com/zitadel/zitadel-go/blob/next/example),
-like how you can integrate the [client in your own API](https://github.com/zitadel/zitadel-go/blob/next/example/api/client/main.go)
+like how you can integrate the [application in your own API](https://github.com/zitadel/zitadel-go/blob/next/example/api/client/main.go)
 or refer to our [API Docs](/apis/introduction).
@@ -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

@@ -21,7 +21,7 @@ You can do so by using [Console](../console/users) or [setting user metadata](/r

 Most of the methods below require you to login with the correct user while setting some scopes.
 Make sure you pick the right user when logging into the test application.
-Use the [OIDC authentication request playground](https://zitadel.com/playgrounds/oidc) or the configuration of an [example client](/sdk-examples/introduction) to set the required scopes and receive a valid access token.
+Use the [OIDC authentication request playground](https://zitadel.com/playgrounds/oidc) or the configuration of an [example application](/sdk-examples/introduction) to set the required scopes and receive a valid access token.

 <Callout title="Getting a token">
 In case you want to test out different settings configure an application with code flow (PKCE).
@@ -149,7 +149,7 @@ You can use the authentication service to request and search for the user's meta
 The introspection endpoint and the token endpoint in the examples above do not require a special scope to access.
 Yet when accessing the authentication service, you need to pass the [reserved scope](/apis/openidoauth/scopes#reserved-scopes) `urn:zitadel:iam:org:project:id:zitadel:aud` along with the authentication request.
 This scope allows the user to access ZITADEL's APIs, specifically the authentication API that we need for this method.
-Use the [OIDC authentication request playground](https://zitadel.com/playgrounds/oidc) or the configuration of an [example client](/sdk-examples/introduction) to set the required scopes and receive a valid access token.
+Use the [OIDC authentication request playground](https://zitadel.com/playgrounds/oidc) or the configuration of an [example application](/sdk-examples/introduction) to set the required scopes and receive a valid access token.

 <Callout title="Invalid audience">
 If you get the error "invalid audience (APP-Zxfako)", then you need to add the reserved scope `urn:zitadel:iam:org:project:id:zitadel:aud` to your authentication request.
@@ -86,7 +86,7 @@ We'd appreciate if you could contribute to our repo with translations of your la
 ### Projects and applications

 As our Hosted Login is a separate authentication screen, you have to determine how you are directing your users from your applications.
-ZITADEL's Applications live under ZITADEL's Projects. You may add multiple applications for your different client-types (Native, Web, User Agent, or API). When setting up your applications consider reading our guide about [Authentication Flows](../integrate/login/oidc/login-users).
+ZITADEL's Applications live under ZITADEL's Projects. You may add multiple applications for your different application-types (Native, Web, User Agent, or API). When setting up your applications consider reading our guide about [Authentication Flows](../integrate/login/oidc/login-users).

 ### Access Control

@@ -13,9 +13,11 @@ This sample app implements the [OIDC PKCE](/guides/integrate/login/oidc/login-us
 - Login: Exchanges a code challenge for an access token via ZITADEL.
 - Authorize: Uses the token to retrieve profile data from the userinfo endpoint.
 - Logout: Clears the local session and revokes the token.
+
 ## Get Started with ZITADEL Cloud

 Set up your ZITADEL account and organization to begin managing identities for your applications.
+
 ### 1. Create your Account and Organization

 You first need access to the ZITADEL Cloud Customer Portal.
@@ -32,6 +34,7 @@ This is the administrative hub for managing your billing, teams, and instances.

 Complete the brief onboarding questions.
 This data helps us prioritize the development of new features, SDKs, and integrations that matter most to our community.
+
 ![](../../../public/img/guides/quickstart/onboarding_questions.png)

 ### 3. Create your ZITADEL instance
@@ -48,10 +51,12 @@ Follow these steps to deploy your first instance:
 5. **Deploy**: Review your configuration and click Create Instance.

 ![Create Instance](../../../public/img/guides/quickstart/cloud_create_instance.png)
+
 ### 4. Create your Project and Application

 In ZITADEL, [**Applications**](/guides/manage/console/applications-overview) are grouped into [**Projects**](/guides/manage/console/projects-overview).
-This allows multiple apps (like a React frontend and a Go backend) to share the same roles and authorizations.
+This allows multiple applications (like a React frontend and a Go backend) to share the same roles and authorizations.
+
 #### Launch the Management Console

 Click **Create your app**. This opens the Management Console for your instance in a new tab.
@@ -62,6 +67,7 @@ Log in using the Admin credentials you just created.
 - **Name**: Enter a name (e.g., Project1).
 - **Framework**: Select React (or choose Other if your stack isn't listed).
 - **Continue**: Click the Continue button.
+
 ![](../../../public/img/guides/quickstart/create_project_react.png)

 #### Step 2: Review Default Configuration
@@ -74,6 +80,7 @@ ZITADEL automatically configures the best security settings for your selected fr
 ![](../../../public/img/guides/quickstart/project_config_overview_react.png)

 ### 5. Collect your Integration Keys
+
 To connect your React application to ZITADEL, you need two primary configuration values.
 These are typically stored as environment variables in your project.

@@ -85,7 +92,9 @@ These are typically stored as environment variables in your project.
 ![Get URLs](../../../public/img/guides/quickstart/project_urls.png)

 ## Integrate ZITADEL into your React App
+
 ### How the Authentication Flow Works
+
 ZITADEL handles the complexity of the OIDC handshake so your app stays secure without manual token management.
 1. **Login**: App redirects the user to ZITADEL with a PKCE challenge.
 2. **Auth**: User authenticates on the ZITADEL hosted login page.
@@ -94,6 +103,7 @@ ZITADEL handles the complexity of the OIDC handshake so your app stays secure wi
 5. **Logout**: The app clears local tokens and terminates the ZITADEL session.

 ### 1. Prerequisites
+
 - [Node.js](https://nodejs.org/): v16 or later.
 - Code Editor: [VS Code](https://code.visualstudio.com/) or similar
 - [Yarn](https://yarnpkg.com/): This project uses Yarn for dependency management.
@@ -103,7 +113,8 @@ ZITADEL handles the complexity of the OIDC handshake so your app stays secure wi
 Clone the repository and move into the project directory:
 ```bash
 git clone https://github.com/zitadel/zitadel-react.git
-cd zitadel-react```
+cd zitadel-react
+```

 ### 3. Build and Install

@@ -113,7 +124,8 @@ Since this repo contains the SDK source, you need to build the library before ru
 cd lib && yarn install && yarn build

 # Install example app dependencies
-cd .. && yarn install```
+cd .. && yarn install
+```

 ### 4. Configure your Credentials

@@ -162,7 +162,7 @@ Necessary cookies provide basic functionality such as:

 We use cookies for website analytics purposes in order to operate, maintain, and improve the Services for you.
 We use third-party providers, mentioned in our [List of Subprocessors](https://trust.zitadel.com/subprocessors), that collect and process certain analytics data on our behalf.
-These third-party providers helps us understand how you engage with the Services and may also collect information about your use of other websites, apps, and online resources.
+These third-party providers helps us understand how you engage with the Services and may also collect information about your use of other websites, applications, and online resources.

 You can opt out by managing your cookie consent through our Services or a third-party tool of your choice.

@@ -25,7 +25,7 @@ services:
      ZITADEL_DATABASE_POSTGRES_USER_PASSWORD: zitadel
      ZITADEL_DATABASE_POSTGRES_USER_SSL_MODE: disable
      
-      # By configuring a login client, the setup job creates a user of type machine with the role IAM_LOGIN_CLIENT.
+      # By configuring a login application, the setup job creates a user of type machine with the role IAM_LOGIN_CLIENT.
      # It writes a PAT to the path specified in ZITADEL_FIRSTINSTANCE_LOGINCLIENTPATPATH.
      # The PAT is passed to the login container via the environment variable ZITADEL_SERVICE_USER_TOKEN_FILE.
      ZITADEL_FIRSTINSTANCE_LOGINCLIENTPATPATH: /current-dir/login-client.pat
@@ -6,7 +6,7 @@ sidebar_label: HTTP/2 Support
 ZITADEL follows a strict API first approach and makes heavy use of the modern API framework called [gRPC](https://grpc.io/).
 Besides gRPC all APIs are also available in an openapi Rest fashion as well as in gRPC-web for compatibility towards browser integrations.

-To make use of gRPC it is vital to allow your clients to communicate with ZITADEL with [HTTP/2](https://en.wikipedia.org/wiki/HTTP/2).
+To make use of gRPC it is vital to allow your applications to communicate with ZITADEL with [HTTP/2](https://en.wikipedia.org/wiki/HTTP/2).

 Sometimes you need to configure explicitly that you want to use HTTP/2 if you run ZITADEL behind a reverse proxy and below you should find examples for different vendors and projects.

@@ -38,7 +38,7 @@ This error message refers to the audience claim (`aud`) of your token.
 This claim identifies the audience, i.e. the resource server, that this token is intended for.
 If a resource server does not identify itself with a value in the "aud" claim when this claim is present, then the must be rejected (see [RFC7519](https://www.rfc-editor.org/rfc/rfc7519#section-4.1.3) for more details).

-You might encounter this error message from ZITADEL, typically when you authenticated with a client in one project and trying to access an application in another project.
+You might encounter this error message from ZITADEL, typically when you authenticated with an application in one project and trying to access an application in another project.
 You need add a specific [reserved scope](/apis/openidoauth/scopes#reserved-scopes) to add the projectID to the audience of the access token.

 The two scenarios should help you troubleshoot this issue:
@@ -186,7 +186,7 @@ export default function LoginPage() {
      <div className="w-full">
        <LoginForm />
      </div>
-    </DynamicTheme>
+    </DynamicTheme-
  );
 }
 ```
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "مفاتيح الويب النشطة والمستقبلية",
          "DESCRIPTION": "مفاتيح الويب النشطة والقادمة. سيؤدي تفعيل مفتاح جديد إلى إلغاء تنشيط المفتاح الحالي.",
-          "NOTE": "ملاحظة: نقطة نهاية JWKs OIDC تعيد استجابة قابلة للتخزين المؤقت (افتراضياً 5 دقائق). تجنب تفعيل مفتاح قريباً جداً، حيث قد لا يكون متاحاً للتخزين المؤقت والعملاء بعد.",
+          "NOTE": "ملاحظة: نقطة نهاية JWKs OIDC تعيد استجابة قابلة للتخزين المؤقت (افتراضياً 5 دقائق). تجنب تفعيل مفتاح قريباً جداً، حيث قد لا يكون متاحاً للتخزين المؤقت والتطبيقات بعد.",
          "ACTIVATE": "تفعيل مفتاح الويب التالي",
          "ACTIVE": "نشط حالياً",
          "NEXT": "التالي في قائمة الانتظار",
@@ -530,7 +530,6 @@
    "DOWNLOAD": "تنزيل",
    "APPLY": "تطبيق"
  },
-
  "ACTIONSTWO": {
    "BETA_NOTE": "أنت تستخدم حالياً الإصدار الثاني الجديد من الإجراءات (Actions V2)، وهو في مرحلة تجريبية. لا يزال الإصدار 1 السابق متاحاً ولكن سيتم إيقافه في المستقبل. يرجى الإبلاغ عن أي مشاكل أو ملاحظات.",
    "EXECUTION": {
@@ -650,7 +649,7 @@
    "IAM_USER_MANAGER": "لديه إذن لإنشاء وإدارة المستخدمين",
    "IAM_ADMIN_IMPERSONATOR": "لديه إذن لانتحال شخصية المشرفين والمستخدمين النهائيين من جميع المنظمات",
    "IAM_END_USER_IMPERSONATOR": "لديه إذن لانتحال شخصية المستخدمين النهائيين من جميع المنظمات",
-    "IAM_LOGIN_CLIENT": "لديه إذن لإدارة عملاء تسجيل الدخول",
+    "IAM_LOGIN_CLIENT": "لديه إذن لإدارة تطبيقات تسجيل الدخول",
    "ORG_OWNER": "لديه إذن على المنظمة بالكامل",
    "ORG_USER_MANAGER": "لديه إذن لإنشاء وإدارة مستخدمي المنظمة",
    "ORG_OWNER_VIEWER": "لديه إذن لمراجعة المنظمة بالكامل",
@@ -1640,7 +1639,7 @@
      "DEBUGOIDCPARENTERROR": "تصحيح خطأ OIDC Parent",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "إذا تم تمكين العلامة، سيتم تسجيل خطأ OIDC parent في وحدة التحكم.",
      "ENABLEBACKCHANNELLOGOUT": "تمكين تسجيل الخروج عبر القناة الخلفية (Backchannel Logout)",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "ينفذ تسجيل الخروج عبر القناة الخلفية OpenID Connect Back-Channel Logout 1.0 ويمكن استخدامه لإخطار العملاء بإنهاء الجلسة في مزود OpenID.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "ينفذ تسجيل الخروج عبر القناة الخلفية OpenID Connect Back-Channel Logout 1.0 ويمكن استخدامه لإخطار التطبيقات بإنهاء الجلسة في مزود OpenID.",
      "PERMISSIONCHECKV2": "فحص الأذونات V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "إذا تم تمكين العلامة، فستتمكن من استخدام API الجديد وميزاته.",
      "STATES": {
@@ -1925,7 +1924,6 @@
      "UPLOADFAILED": "فشل التحميل!"
    }
  },
-
  "ORG_DETAIL": {
    "TITLE": "المنظمة",
    "DESCRIPTION": "هنا يمكنك تحرير تكوين منظمتك وإدارة الأعضاء.",
@@ -2654,8 +2652,8 @@
      "IDTOKENROLEASSERTION": "أدوار المستخدم داخل رمز ID",
      "IDTOKENROLEASSERTION_DESCRIPTION": "عند تمكين هذا الخيار، سيتم إضافة الأدوار المعينة للمستخدم الموثق مباشرة إلى رمز ID الخاص به. تأكد من تمكين إعداد المشروع 'تعيين أدوار المستخدم أثناء المصادقة' أو الطلب عبر نطاق مخصص.",
      "IDTOKENUSERINFOASSERTION": "تضمين أدوار المستخدم في رمز ID",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "يمكن العملاء من استرجاع مطالبات الملف الشخصي والبريد الإلكتروني والهاتف والعنوان من رمز ID.",
-      "CLOCKSKEW": "يمكن العملاء من التعامل مع انحراف الساعة بين OP والعميل. ستتم إضافة المدة (0-5 ثوانٍ) إلى مطالبة exp وطرحها من iats و auth_time و nbf.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "يمكن التطبيقات من استرجاع مطالبات الملف الشخصي والبريد الإلكتروني والهاتف والعنوان من رمز ID.",
+      "CLOCKSKEW": "يمكن التطبيقات من التعامل مع انحراف الساعة بين OP والتطبيق. ستتم إضافة المدة (0-5 ثوانٍ) إلى مطالبة exp وطرحها من iats و auth_time و nbf.",
      "RECOMMENDED": "موصى به",
      "NOTRECOMMENDED": "غير موصى به",
      "SELECTION": {
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Активни и бъдещи уеб ключове",
          "DESCRIPTION": "Вашите активни и предстоящи уеб ключове. Активирането на нов ключ ще деактивира текущия.",
-          "NOTE": "Забележка: Крайна точка JWKs OIDC връща кешируем отговор (по подразбиране 5 минути). Избягвайте активирането на ключ твърде рано, тъй като той може да не е наличен в кеша и клиентите.",
+          "NOTE": "Забележка: Крайна точка JWKs OIDC връща кешируем отговор (по подразбиране 5 минути). Избягвайте активирането на ключ твърде рано, тъй като той може да не е наличен в кеша и приложенията.",
          "ACTIVATE": "Активирайте следващия уеб ключ",
          "ACTIVE": "В момента активен",
          "NEXT": "Следващ в опашката",
@@ -655,7 +655,7 @@
    "IAM_USER_MANAGER": "Има разрешение за създаване и управление на потребители",
    "IAM_ADMIN_IMPERSONATOR": "Има разрешение да се представя за администратор и крайни потребители от всички организации",
    "IAM_END_USER_IMPERSONATOR": "Има разрешение да се представя за крайни потребители от всички организации",
-    "IAM_LOGIN_CLIENT": "Има разрешение за управление на клиенти за вход",
+    "IAM_LOGIN_CLIENT": "Има разрешение за управление на приложения за вход",
    "ORG_OWNER": "Има разрешение за цялата организация",
    "ORG_USER_MANAGER": "Има разрешение да създава и управлява потребители на организацията",
    "ORG_OWNER_VIEWER": "Има разрешение за преглед на цялата организация",
@@ -1646,7 +1646,7 @@
      "DEBUGOIDCPARENTERROR": "Отстраняване на грешки на OIDC родителя",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Ако флагът е активиран, грешката на OIDC родителя ще бъде записана в конзолата.",
      "ENABLEBACKCHANNELLOGOUT": "Активиране на Backchannel Logout",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Back-Channel Logout имплементира OpenID Connect Back-Channel Logout 1.0 и може да се използва за уведомяване на клиентите за прекратяване на сесията при OpenID доставчика.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Back-Channel Logout имплементира OpenID Connect Back-Channel Logout 1.0 и може да се използва за уведомяване на приложенията за прекратяване на сесията при OpenID доставчика.",
      "PERMISSIONCHECKV2": "Проверка на разрешения V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Ако флагът е активиран, ще можете да използвате новия API и неговите функции.",
      "STATES": {
@@ -2659,8 +2659,8 @@
      "IDTOKENROLEASSERTION": "Потребителски роли в ID Token",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Ако е избрано, заявените роли на удостоверения потребител се добавят към ID токена.",
      "IDTOKENUSERINFOASSERTION": "Потребителска информация в ID Token",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Позволява на клиентите да извличат претенции за профил, имейл, телефон и адрес от ID токена.",
-      "CLOCKSKEW": "Позволява на клиентите да се справят с изкривяването на часовника на OP и клиента. ",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Позволява на приложенията да извличат претенции за профил, имейл, телефон и адрес от ID токена.",
+      "CLOCKSKEW": "Позволява на приложенията да се справят с изкривяването на часовника на OP и приложението. ",
      "RECOMMENDED": "препоръчително",
      "NOTRECOMMENDED": "не се препоръчва",
      "SELECTION": {
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Aktivní a budoucí webové klíče",
          "DESCRIPTION": "Vaše aktivní a nadcházející webové klíče. Aktivací nového klíče dojde k deaktivaci aktuálního.",
-          "NOTE": "Poznámka: Koncový bod JWKs OIDC vrací odpověď uložitelnou do mezipaměti (výchozí 5 minut). Vyhněte se příliš brzké aktivaci klíče, protože nemusí být dostupný v mezipaměti a klientům.",
+          "NOTE": "Poznámka: Koncový bod JWKs OIDC vrací odpověď uložitelnou do mezipaměti (výchozí 5 minut). Vyhněte se příliš brzké aktivaci klíče, protože nemusí být dostupný v mezipaměti a aplikacím.",
          "ACTIVATE": "Aktivovat další webový klíč",
          "ACTIVE": "Aktuálně aktivní",
          "NEXT": "Další v řadě",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "Má oprávnění vytvářet a spravovat uživatele",
    "IAM_ADMIN_IMPERSONATOR": "Má oprávnění vydávat se za správce a koncové uživatele ze všech organizací",
    "IAM_END_USER_IMPERSONATOR": "Má oprávnění vydávat se za koncové uživatele ze všech organizací",
-    "IAM_LOGIN_CLIENT": "Má oprávnění spravovat přihlašovací klienty",
+    "IAM_LOGIN_CLIENT": "Má oprávnění spravovat přihlašovací aplikace",
    "ORG_OWNER": "Má oprávnění nad celou organizací",
    "ORG_USER_MANAGER": "Má oprávnění vytvářet a spravovat uživatele organizace",
    "ORG_OWNER_VIEWER": "Má oprávnění prohlížet celou organizaci",
@@ -1644,7 +1644,7 @@
      "DEBUGOIDCPARENTERROR": "Debugování chyby rodiče OIDC",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Pokud je příznak povolen, chyba rodiče OIDC bude zaznamenána v konzoli.",
      "ENABLEBACKCHANNELLOGOUT": "Povolit Backchannel Logout",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Back-Channel Logout implementuje OpenID Connect Back-Channel Logout 1.0 a může být použit k informování klientů o ukončení relace u poskytovatele OpenID.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Back-Channel Logout implementuje OpenID Connect Back-Channel Logout 1.0 a může být použit k informování aplikací o ukončení relace u poskytovatele OpenID.",
      "PERMISSIONCHECKV2": "Kontrola oprávnění V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Pokud je příznak povolen, budete moci používat nový API a jeho funkce.",
      "STATES": {
@@ -2641,8 +2641,8 @@
      "IDTOKENROLEASSERTION": "Role uživatele uvnitř ID tokenu",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Pokud je vybráno, požadované role ověřeného uživatele jsou přidány do ID tokenu.",
      "IDTOKENUSERINFOASSERTION": "Informace o uživateli uvnitř ID tokenu",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Umožňuje klientům získávat nároky (claims) na profil, email, telefon a adresu z ID tokenu.",
-      "CLOCKSKEW": "Umožňuje klientům zvládnout rozdíl času mezi OP a klientem. Doba trvání (0-5s) bude přidána k nároku exp a odečtena od iats, auth_time a nbf.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Umožňuje aplikacím získávat nároky (claims) na profil, email, telefon a adresu z ID tokenu.",
+      "CLOCKSKEW": "Umožňuje aplikacím zvládnout rozdíl času mezi OP a aplikací. Doba trvání (0-5s) bude přidána k nároku exp a odečtena od iats, auth_time a nbf.",
      "RECOMMENDED": "doporučeno",
      "NOTRECOMMENDED": "nedoporučeno",
      "SELECTION": {
@@ -34,7 +34,7 @@
    },
    "PROJECTS": {
      "TITLE": "Projekte",
-      "DESCRIPTION": "Ein Projekt enthält eine oder mehrere Anwendungen, die du nutzen kannst, um deine Benutzer zu authentifizieren. Zum Beispiel könntest du ein einziges Projekt mit 3 Anwendungen haben; eine für dein Web-Frontend, eine für deine mobile App und eine für dein Backend. Außerdem kannst du deine Benutzer mit Projekten autorisieren. Um Benutzern aus anderen Organisationen das Einloggen in deine Anwendungen zu erlauben, gewähre ihnen Zugriff auf dein Projekt.<br/><br/>Wenn du ein Projekt nicht finden kannst, kontaktiere den Projekteigentümer oder jemanden mit den entsprechenden Rechten, um Zugang zu erhalten.",
+      "DESCRIPTION": "Ein Projekt enthält eine oder mehrere Anwendungen, die du nutzen kannst, um deine Benutzer zu authentifizieren. Zum Beispiel könntest du ein einziges Projekt mit 3 Anwendungen haben; eine für dein Web-Frontend, eine für deine mobile Anwendung, und eine für dein Backend. Außerdem kannst du deine Benutzer mit Projekten autorisieren. Um Benutzern aus anderen Organisationen das Einloggen in deine Anwendungen zu erlauben, gewähre ihnen Zugriff auf dein Projekt.<br/><br/>Wenn du ein Projekt nicht finden kannst, kontaktiere den Projekteigentümer oder jemanden mit den entsprechenden Rechten, um Zugang zu erhalten.",
      "OWNED": {
        "TITLE": "Eigene Projekte",
        "DESCRIPTION": "Dies sind die Projekte, die du besitzt. Du kannst die Einstellungen, Berechtigungen und Anwendungen dieser Projekte verwalten."
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Aktive und zukünftige Web Keys",
          "DESCRIPTION": "Deine aktiven und kommenden Web Keys. Das Aktivieren eines neuen Schlüssels deaktiviert den aktuellen.",
-          "NOTE": "Hinweis: Der JWKs OIDC-Endpunkt gibt eine zwischenspeicherbare Antwort zurück (Standard: 5 Min.). Vermeide es, einen Schlüssel zu früh zu aktivieren, da er möglicherweise noch nicht in Caches und Clients verfügbar ist.",
+          "NOTE": "Hinweis: Der JWKs OIDC-Endpunkt gibt eine zwischenspeicherbare Antwort zurück (Standard: 5 Min.). Vermeide es, einen Schlüssel zu früh zu aktivieren, da er möglicherweise noch nicht in Caches und Anwendungen verfügbar ist.",
          "ACTIVATE": "Nächsten Web Key aktivieren",
          "ACTIVE": "Derzeit aktiv",
          "NEXT": "Als Nächstes in der Warteschlange",
@@ -386,12 +386,12 @@
        "action": "Projekt erstellen"
      },
      "APPLICATION_CREATED": {
-        "title": "Registriere deine App",
+        "title": "Registriere deine Anwendung",
        "description": "Registriere deine erste Web-, Nativ-, API- oder SAML-Applikation und konfiguriere den Authentification-Flow.",
-        "action": "App registrieren"
+        "action": "Anwendung registrieren"
      },
      "AUTHENTICATION_SUCCEEDED_ON_APPLICATION": {
-        "title": "Logge dich in deine App ein",
+        "title": "Logge dich in deine Anwendung ein",
        "description": "Integriere deine Applikation mit Zitadel für die Authentifizierung und teste es, indem du dich mit deinem Admin-Benutzer einloggst.",
        "action": "Einloggen"
      },
@@ -453,7 +453,7 @@
    "DEVMODEWARN": "Der Dev-Modus ist standardmäßig aktiviert. Sie können Werte für die Produktion später aktualisieren.",
    "GUIDE": "Guide",
    "BROWSEEXAMPLES": "Beispiele durchsuchen",
-    "DUPLICATEAPPRENAME": "Es gibt bereits eine App mit gleichem Namen. Bitte wähle einen anderen Namen.",
+    "DUPLICATEAPPRENAME": "Es gibt bereits eine Anwendung mit gleichem Namen. Bitte wähle einen anderen Namen.",
    "DIALOG": {
      "CHANGE": {
        "TITLE": "Framework ändern",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "Hat die Berechtigung zum Erstellen und Verwalten von Benutzern",
    "IAM_ADMIN_IMPERSONATOR": "Hat die Berechtigung, sich als Administrator und Endbenutzer aller Organisationen auszugeben",
    "IAM_END_USER_IMPERSONATOR": "Hat die Berechtigung, sich als Endbenutzer aller Organisationen auszugeben",
-    "IAM_LOGIN_CLIENT": "Hat die Berechtigung, Anmeldeclients zu verwalten",
+    "IAM_LOGIN_CLIENT": "Hat die Berechtigung, Anmeldeanwendungen zu verwalten",
    "ORG_OWNER": "Hat die Berechtigung für die gesamte Organisation",
    "ORG_USER_MANAGER": "Hat die Berechtigung, Benutzer der Organisation zu erstellen und zu verwalten",
    "ORG_OWNER_VIEWER": "Hat die Leseberechtigung, die gesamte Organisation zu überprüfen",
@@ -884,9 +884,9 @@
      "DESCRIPTION": "Füge einen zusätzlichen Faktor hinzu, um Dein Konto optimal zu schützen.",
      "MANAGE_DESCRIPTION": "Verwalte die Multifaktor-Merkmale Deiner Benutzer.",
      "ADD": "Faktor hinzufügen",
-      "OTP": "Authentikator App für TOTP (Time-based One-Time Password)",
+      "OTP": "Authentikator Anwendung für TOTP (Time-based One-Time Password)",
      "OTP_DIALOG_TITLE": "OTP hinzufügen",
-      "OTP_DIALOG_DESCRIPTION": "Scanne den QR-Code mit einer Authenticator App und verifiziere den erhaltenen Code, um OTP zu aktivieren.",
+      "OTP_DIALOG_DESCRIPTION": "Scanne den QR-Code mit einer Authenticator Anwendung und verifiziere den erhaltenen Code, um OTP zu aktivieren.",
      "U2F": "Passkey",
      "U2F_DIALOG_TITLE": "Faktor hinzufügen",
      "U2F_DIALOG_DESCRIPTION": "Gib einen Namen für den von dir verwendeten Authentikator an.",
@@ -1611,7 +1611,7 @@
        "3": "Telefonnummer Verifikationscode",
        "4": "Passwort Zurücksetzen Code",
        "5": "Passkey Initialisierungscode",
-        "6": "Applicationssecret",
+        "6": "Anwendungsgeheimnis",
        "7": "One Time Password (OTP) - SMS",
        "8": "One Time Password (OTP) - Email"
      },
@@ -1644,7 +1644,7 @@
      "DEBUGOIDCPARENTERROR": "Debug OIDC Parent error",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Wenn die Flagge aktiviert ist, wird der OIDC-Elternfehler in der Konsole protokolliert.",
      "ENABLEBACKCHANNELLOGOUT": "Backchannel-Logout aktivieren",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Der Back-Channel-Logout implementiert OpenID Connect Back-Channel Logout 1.0 und kann verwendet werden, um Clients über die Beendigung der Sitzung beim OpenID-Provider zu benachrichtigen.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Der Back-Channel-Logout implementiert OpenID Connect Back-Channel Logout 1.0 und kann verwendet werden, um Anwendungen über die Beendigung der Sitzung beim OpenID-Provider zu benachrichtigen.",
      "PERMISSIONCHECKV2": "Berechtigungsprüfung V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Wenn die Flagge aktiviert ist, können Sie die neue API und ihre Funktionen verwenden.",
      "STATES": {
@@ -2408,7 +2408,7 @@
    },
    "SECONDFACTORTYPES": {
      "0": "Unknown",
-      "1": "One Time Password per Authenticator App (TOTP)",
+      "1": "One Time Password per Authenticator Anwendung (TOTP)",
      "2": "Passkey",
      "3": "One Time Password per Email (Email OTP)",
      "4": "One Time Password per SMS (SMS OTP)",
@@ -2632,8 +2632,8 @@
      "IDTOKENROLEASSERTION": "Benutzerrollen im ID Token",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Bei Auswahl werden dem ID Token die angeforderten Rollen des authentifizierten Benutzers hinzugefügt.",
      "IDTOKENUSERINFOASSERTION": "User Info im ID Token",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Ermöglich OIDC clients claims von profile, email, phone und address direkt vom ID Token zu beziehen.",
-      "CLOCKSKEW": "ermöglicht Clients, den Taktversatz von OP und Client zu verarbeiten. Die Dauer (0-5s) wird der exp addiert und von iats, auth_time und nbf abgezogen.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Ermöglich OIDC Anwendungen claims von profile, email, phone und address direkt vom ID Token zu beziehen.",
+      "CLOCKSKEW": "ermöglicht Anwendungen, den Taktversatz von OP und Anwendung zu verarbeiten. Die Dauer (0-5s) wird der exp addiert und von iats, auth_time und nbf abgezogen.",
      "RECOMMENDED": "Empfohlen",
      "NOTRECOMMENDED": "nicht empfohlen",
      "SELECTION": {
@@ -34,7 +34,7 @@
    },
    "PROJECTS": {
      "TITLE": "Projects",
-      "DESCRIPTION": "A project hosts one or more applications that you can use to authenticate your users. For example, you might have a single project with 3 applications: one each for your web frontend, your mobile app, and your backend services. Also you can authorize your users with projects. To allow users from other organizations to log in to your applications, grant them access to your project.<br/><br/>If you can't find a project, contact the project's owner or someone with the corresponding rights to gain access.",
+      "DESCRIPTION": "A project hosts one or more applications that you can use to authenticate your users. For example, you might have a single project with 3 applications: one each for your web frontend, your mobile application, and your backend services. Also you can authorize your users with projects. To allow users from other organizations to log in to your applications, grant them access to your project.<br/><br/>If you can't find a project, contact the project's owner or someone with the corresponding rights to gain access.",
      "OWNED": {
        "TITLE": "Owned Projects",
        "DESCRIPTION": "These are the projects you own. You can manage these project settings, authorizations and applications."
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Active and Future Web Keys",
          "DESCRIPTION": "Your active and upcoming web keys. Activating a new key will deactivate the current one.",
-          "NOTE": "Note: The JWKs OIDC endpoint returns a cacheable response (default 5 min). Avoid activating a key too soon, as it may not be available to caches and clients yet.",
+          "NOTE": "Note: The JWKs OIDC endpoint returns a cacheable response (default 5 min). Avoid activating a key too soon, as it may not be available to caches and applications yet.",
          "ACTIVATE": "Activate next Web Key",
          "ACTIVE": "Currently active",
          "NEXT": "Next in queue",
@@ -386,12 +386,12 @@
        "action": "Create project"
      },
      "APPLICATION_CREATED": {
-        "title": "Register your app",
+        "title": "Register your application",
        "description": "Register your web, native, api or saml application and setup an authentication flow.",
-        "action": "Register app"
+        "action": "Register application"
      },
      "AUTHENTICATION_SUCCEEDED_ON_APPLICATION": {
-        "title": "Log in to your app",
+        "title": "Log in to your application",
        "description": "Integrate your application with Zitadel for authentication and test it by logging in with your admin user.",
        "action": "Log in"
      },
@@ -454,7 +454,7 @@
    "DEVMODEWARN": "Dev Mode is enabled by default. You can update values for production later.",
    "GUIDE": "Guide",
    "BROWSEEXAMPLES": "Browse Examples and SDKs",
-    "DUPLICATEAPPRENAME": "An app with the same name exists already. Please choose a different name.",
+    "DUPLICATEAPPRENAME": "An application with the same name exists already. Please choose a different name.",
    "DIALOG": {
      "CHANGE": {
        "TITLE": "Change Framework",
@@ -657,7 +657,7 @@
    "IAM_USER_MANAGER": "Has permission to create and manage users",
    "IAM_ADMIN_IMPERSONATOR": "Has permission to impersonate admin and end users from all organizations",
    "IAM_END_USER_IMPERSONATOR": "Has permission to impersonate end users from all organizations",
-    "IAM_LOGIN_CLIENT": "Has permission to manage login clients",
+    "IAM_LOGIN_CLIENT": "Has permission to manage login applications",
    "ORG_OWNER": "Has permission over the whole organization",
    "ORG_USER_MANAGER": "Has permission to create and manage users of the organization",
    "ORG_OWNER_VIEWER": "Has permission to review the whole organization",
@@ -885,9 +885,9 @@
      "DESCRIPTION": "Add a second factor to ensure optimal security for your account.",
      "MANAGE_DESCRIPTION": "Manage the second factor methods of your users.",
      "ADD": "Add Factor",
-      "OTP": "Authenticator App for TOTP (Time-based One-Time Password)",
+      "OTP": "Authenticator Application for TOTP (Time-based One-Time Password)",
      "OTP_DIALOG_TITLE": "Add OTP",
-      "OTP_DIALOG_DESCRIPTION": "Scan the QR code with an authenticator app and enter the code below to verify and activate the OTP method.",
+      "OTP_DIALOG_DESCRIPTION": "Scan the QR code with an authenticator application and enter the code below to verify and activate the OTP method.",
      "U2F": "Passkey",
      "U2F_DIALOG_TITLE": "Verify Factor",
      "U2F_DIALOG_DESCRIPTION": "Enter a name for your used universal Multifactor.",
@@ -1615,7 +1615,7 @@
        "3": "Phone verification",
        "4": "Password Reset",
        "5": "Passkey Initialization",
-        "6": "App Secret",
+        "6": "Application Secret",
        "7": "One Time Password (OTP) - SMS",
        "8": "One Time Password (OTP) - Email"
      },
@@ -1648,7 +1648,7 @@
      "DEBUGOIDCPARENTERROR": "Debug OIDC Parent Error",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "If the flag is enabled, the OIDC parent error will be logged in the console.",
      "ENABLEBACKCHANNELLOGOUT": "Enable Backchannel Logout",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "The Back-Channel Logout implements OpenID Connect Back-Channel Logout 1.0 and can be used to notify clients about session termination at the OpenID Provider.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "The Back-Channel Logout implements OpenID Connect Back-Channel Logout 1.0 and can be used to notify applications about session termination at the OpenID Provider.",
      "PERMISSIONCHECKV2": "Permission Check V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "If the flag is enabled, you'll be able to use the new API and its features.",
      "STATES": {
@@ -2434,7 +2434,7 @@
    },
    "SECONDFACTORTYPES": {
      "0": "Unknown",
-      "1": "One Time Password by Authenticator App (TOTP)",
+      "1": "One Time Password by Authenticator Application (TOTP)",
      "2": "Passkey",
      "3": "One Time Password by Email (Email OTP)",
      "4": "One Time Password by SMS (SMS OTP)",
@@ -2662,8 +2662,8 @@
      "IDTOKENROLEASSERTION": "User roles inside ID Token",
      "IDTOKENROLEASSERTION_DESCRIPTION": "When this option is enabled, the authenticated user's assigned roles will be added directly to their ID token. Ensure to enable the Project setting 'Assign user roles during authentication' or request via custom scope.",
      "IDTOKENUSERINFOASSERTION": "Include user's profile info in the ID Token",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Enables clients to retrieve profile, email, phone and address claims from ID token.",
-      "CLOCKSKEW": "Enables clients to handle clock skew of OP and client. The duration (0-5s) will be added to exp claim and subtracted from iats, auth_time and nbf.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Enables applications to retrieve profile, email, phone and address claims from ID token.",
+      "CLOCKSKEW": "Enables applications to handle clock skew of OP and application. The duration (0-5s) will be added to exp claim and subtracted from iats, auth_time and nbf.",
      "RECOMMENDED": "recommended",
      "NOTRECOMMENDED": "not recommended",
      "SELECTION": {
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Claves Web Activas y Futuras",
          "DESCRIPTION": "Tus claves web activas y próximas. Activar una nueva clave desactivará la actual.",
-          "NOTE": "Nota: El endpoint JWKs OIDC devuelve una respuesta almacenable en caché (por defecto 5 min). Evita activar una clave demasiado pronto, ya que puede que aún no esté disponible en cachés y clientes.",
+          "NOTE": "Nota: El endpoint JWKs OIDC devuelve una respuesta almacenable en caché (por defecto 5 min). Evita activar una clave demasiado pronto, ya que puede que aún no esté disponible en cachés y aplicaciones.",
          "ACTIVATE": "Activar la siguiente Clave Web",
          "ACTIVE": "Actualmente activa",
          "NEXT": "Siguiente en la cola",
@@ -388,7 +388,7 @@
      "APPLICATION_CREATED": {
        "title": "Registra tu aplicación",
        "description": "Registra tu aplicación web, nativa, api o saml y configura tu flujo de autenticación.",
-        "action": "Registrar app"
+        "action": "Registrar aplicación"
      },
      "AUTHENTICATION_SUCCEEDED_ON_APPLICATION": {
        "title": "Inicia sesión en tu aplicación",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "Tiene permiso para crear y gestionar usuarios",
    "IAM_ADMIN_IMPERSONATOR": "Tiene permiso para hacerse pasar por administradores y usuarios finales de todas las organizaciones",
    "IAM_END_USER_IMPERSONATOR": "Tiene permiso para hacerse pasar por usuarios finales de todas las organizaciones",
-    "IAM_LOGIN_CLIENT": "Tiene permiso para gestionar los clientes de inicio de sesión",
+    "IAM_LOGIN_CLIENT": "Tiene permiso para gestionar las aplicaciones de inicio de sesión",
    "ORG_OWNER": "Tiene permisos sobre toda la organización",
    "ORG_USER_MANAGER": "Tiene permiso para crear y gestionar usuarios de la organización",
    "ORG_OWNER_VIEWER": "TIene permiso para revisar toda la organización",
@@ -884,9 +884,9 @@
      "DESCRIPTION": "Añade un doble factor para configurar una seguridad óptima de tu cuenta.",
      "MANAGE_DESCRIPTION": "Gestiona el método de doble factor para tus usuarios.",
      "ADD": "Añadir factor",
-      "OTP": "App autenticadora para TOTP (Time-based One-Time Password)",
+      "OTP": "Aplicación autenticadora para TOTP (Time-based One-Time Password)",
      "OTP_DIALOG_TITLE": "Añadir TOTP",
-      "OTP_DIALOG_DESCRIPTION": "Escanea el código QR con una app autenticadora introduciendo el siguiente código para verificar y activar el método OTP.",
+      "OTP_DIALOG_DESCRIPTION": "Escanea el código QR con una aplicación autenticadora introduciendo el siguiente código para verificar y activar el método OTP.",
      "U2F": "Llave de acceso (Huella dactilar, claves de seguridad, Face ID y otros)",
      "U2F_DIALOG_TITLE": "Verificar factor",
      "U2F_DIALOG_DESCRIPTION": "Introduce un nombre para tu Multifactor universal.",
@@ -1612,7 +1612,7 @@
        "3": "Verificación de teléfono",
        "4": "Restablecimiento de contraseña",
        "5": "Inicialización de llave de acceso",
-        "6": "Secreto de App",
+        "6": "Secreto de aplicación",
        "7": "One Time Password (OTP) - SMS",
        "8": "One Time Password (OTP) - email"
      },
@@ -1645,7 +1645,7 @@
      "DEBUGOIDCPARENTERROR": "Debug OIDC Parent Error",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Si la bandera está habilitada, el error del padre OIDC se registrará en la consola.",
      "ENABLEBACKCHANNELLOGOUT": "Habilitar Backchannel Logout",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "El Back-Channel Logout implementa OpenID Connect Back-Channel Logout 1.0 y se puede usar para notificar a los clientes sobre la terminación de la sesión en el proveedor de OpenID.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "El Back-Channel Logout implementa OpenID Connect Back-Channel Logout 1.0 y se puede usar para notificar a las aplicaciones sobre la terminación de la sesión en el proveedor de OpenID.",
      "PERMISSIONCHECKV2": "Verificación de permisos V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Si la bandera está habilitada, podrá usar la nueva API y sus funciones.",
      "STATES": {
@@ -2405,7 +2405,7 @@
    },
    "SECONDFACTORTYPES": {
      "0": "Desconocido",
-      "1": "One Time Password por Authenticator App (TOTP)",
+      "1": "One Time Password por aplicación autenticadora (TOTP)",
      "2": "Llave de acceso",
      "3": "One Time Password por email (Email OTP)",
      "4": "One Time Password por SMS (SMS OTP)",
@@ -2629,8 +2629,8 @@
      "IDTOKENROLEASSERTION": "Roles de usuario dentro del Token de ID",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Si se selecciona, los roles solicitados para el usuario autenticado se añaden al token de ID.",
      "IDTOKENUSERINFOASSERTION": "Información del usuario dentro del Token de ID",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Permite a los clientes obtener los claims de perfil, email, teléfono y dirección del token de ID.",
-      "CLOCKSKEW": "Permite a los clientes manejar el sesgo de reloj de OP y el cliente. La duración (0-5 s) se agregará al claim exp y se restará de iats, auth_time y nbf.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Permite a las aplicaciones obtener los claims de perfil, email, teléfono y dirección del token de ID.",
+      "CLOCKSKEW": "Permite a las aplicaciones manejar el sesgo de reloj de OP y la aplicación. La duración (0-5 s) se agregará al claim exp y se restará de iats, auth_time y nbf.",
      "RECOMMENDED": "recomendado",
      "NOTRECOMMENDED": "no recomendado",
      "SELECTION": {
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Clés Web Actives et Futures",
          "DESCRIPTION": "Vos clés Web actives et à venir. L'activation d'une nouvelle clé désactivera l'actuelle.",
-          "NOTE": "Remarque : Le point de terminaison JWKs OIDC renvoie une réponse mise en cache (par défaut 5 min). Évitez d'activer une clé trop tôt, car elle pourrait ne pas encore être disponible pour les caches et les clients.",
+          "NOTE": "Remarque : Le point de terminaison JWKs OIDC renvoie une réponse mise en cache (par défaut 5 min). Évitez d'activer une clé trop tôt, car elle pourrait ne pas encore être disponible pour les caches et les applications.",
          "ACTIVATE": "Activer la prochaine Clé Web",
          "ACTIVE": "Actuellement active",
          "NEXT": "Prochaine dans la file d'attente",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "A le droit de créer et de gérer les utilisateurs",
    "IAM_ADMIN_IMPERSONATOR": "A l'autorisation de se faire passer pour l'administrateur et les utilisateurs finaux de toutes les organisations",
    "IAM_END_USER_IMPERSONATOR": "Est autorisé à usurper l'identité des utilisateurs finaux de toutes les organisations",
-    "IAM_LOGIN_CLIENT": "A la permission de gérer les clients de connexion",
+    "IAM_LOGIN_CLIENT": "A la permission de gérer les applications de connexion",
    "ORG_OWNER": "A le droit de contrôler l'ensemble de l'organisation",
    "ORG_USER_MANAGER": "A le droit de créer et de gérer les utilisateurs de l'organisation",
    "ORG_OWNER_VIEWER": "A le droit de passer en revue l'ensemble de l'organisation",
@@ -1644,7 +1644,7 @@
      "DEBUGOIDCPARENTERROR": "Debug OIDC Parent Error",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Si le drapeau est activé, l'erreur parent OIDC sera enregistrée dans la console.",
      "ENABLEBACKCHANNELLOGOUT": "Activer le Backchannel Logout",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Le Back-Channel Logout implémente OpenID Connect Back-Channel Logout 1.0 et peut être utilisé pour notifier les clients de la fin de session chez le fournisseur OpenID.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Le Back-Channel Logout implémente OpenID Connect Back-Channel Logout 1.0 et peut être utilisé pour notifier les applications de la fin de session chez le fournisseur OpenID.",
      "PERMISSIONCHECKV2": "Vérification des permissions V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Si le drapeau est activé, vous pourrez utiliser la nouvelle API et ses fonctionnalités.",
      "STATES": {
@@ -2633,8 +2633,8 @@
      "IDTOKENROLEASSERTION": "Rôles de l'utilisateur dans le jeton d'identification",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Si sélectionné, les rôles demandés à l'utilisateur authentifié sont ajoutés au jeton d'identification. Assurez-vous d'activer le paramètre de projet 'Attribuer des rôles d'utilisateur pendant l'authentification' ou de le demander via une portée personnalisée.",
      "IDTOKENUSERINFOASSERTION": "Informations sur l'utilisateur dans le jeton d'identification",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Permet aux clients de récupérer le profil, l'e-mail, le téléphone et l'adresse à partir du jeton d'identification.",
-      "CLOCKSKEW": "Permet aux clients de gérer le décalage d'horloge de l'OP et du client. La durée (0-5s) sera ajoutée à la réclamation exp et soustraite de iats, auth_time et nbf.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Permet aux applications de récupérer le profil, l'e-mail, le téléphone et l'adresse à partir du jeton d'identification.",
+      "CLOCKSKEW": "Permet aux applications de gérer le décalage d'horloge de l'OP et de l'application. La durée (0-5s) sera ajoutée à la réclamation exp et soustraite de iats, auth_time et nbf.",
      "RECOMMENDED": "recommandé",
      "NOTRECOMMENDED": "non recommandé",
      "SELECTION": {
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Aktív és Jövőbeli Webkulcsok",
          "DESCRIPTION": "Az aktív és közelgő webkulcsai. Egy új kulcs aktiválása deaktiválja az aktuálisat.",
-          "NOTE": "Megjegyzés: A JWKs OIDC végpont egy gyorsítótárazható választ ad vissza (alapértelmezett: 5 perc). Kerülje a kulcs túl korai aktiválását, mivel lehet, hogy még nem érhető el a gyorsítótárakban és a klienseknél.",
+          "NOTE": "Megjegyzés: A JWKs OIDC végpont egy gyorsítótárazható választ ad vissza (alapértelmezett: 5 perc). Kerülje a kulcs túl korai aktiválását, mivel lehet, hogy még nem érhető el a gyorsítótárakban és az alkalmazásoknál.",
          "ACTIVATE": "Következő Webkulcs aktiválása",
          "ACTIVE": "Jelenleg aktív",
          "NEXT": "Következő a sorban",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "Jogosultsága van felhasználók létrehozására és kezelésére",
    "IAM_ADMIN_IMPERSONATOR": "Jogosultsága van adminok és végfelhasználók megszemélyesítésére minden szervezetből",
    "IAM_END_USER_IMPERSONATOR": "Engedélye van az összes szervezet véghasználóinak megszemélyesítésére",
-    "IAM_LOGIN_CLIENT": "Jogosultsága van a bejelentkezési kliensek kezelésére",
+    "IAM_LOGIN_CLIENT": "Jogosultsága van a bejelentkezési alkalmazások kezelésére",
    "ORG_OWNER": "Engedélye van az egész szervezet fölött",
    "ORG_USER_MANAGER": "Engedélye van a szervezet felhasználóinak létrehozására és kezelésére",
    "ORG_OWNER_VIEWER": "Engedélye van az egész szervezet áttekintésére",
@@ -1642,7 +1642,7 @@
      "DEBUGOIDCPARENTERROR": "Debug OIDC Parent Error",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Ha a zászló engedélyezve van, az OIDC szülő hiba naplózva lesz a konzolban.",
      "ENABLEBACKCHANNELLOGOUT": "Backchannel Logout engedélyezése",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "A Back-Channel Logout megvalósítja az OpenID Connect Back-Channel Logout 1.0-t, és használható az ügyfelek értesítésére a munkamenet befejezéséről az OpenID szolgáltatónál.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "A Back-Channel Logout megvalósítja az OpenID Connect Back-Channel Logout 1.0-t, és használható az alkalmazások értesítésére a munkamenet befejezéséről az OpenID szolgáltatónál.",
      "PERMISSIONCHECKV2": "Engedély ellenőrzés V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Ha a zászló engedélyezve van, használhatja az új API-t és annak funkcióit.",
      "STATES": {
@@ -2428,7 +2428,7 @@
    },
    "SECONDFACTORTYPES": {
      "0": "Ismeretlen",
-      "1": "Egyszeri Jelszó az Authenticator App-al (TOTP)",
+      "1": "Egyszeri Jelszó az Authenticator alkalmazással (TOTP)",
      "2": "Passkey",
      "3": "Egyszeri Jelszó Emailben (Email OTP)",
      "4": "Egyszeri jelszó SMS-ben (SMS OTP)",
@@ -2656,8 +2656,8 @@
      "IDTOKENROLEASSERTION": "Felhasználói szerepkörök az ID Tokenben",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Ha kiválasztod, a hitelesített felhasználó kért szerepkörei hozzá lesznek adva az ID tokenhez.",
      "IDTOKENUSERINFOASSERTION": "Felhasználói információk az ID Tokenben",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Lehetővé teszi az ügyfelek számára, hogy lekérjék a profil-, e-mail-, telefon- és címadatokat az ID tokenből.",
-      "CLOCKSKEW": "Lehetővé teszi az ügyfelek számára az OP és az ügyfél óraeltolódásának kezelését. Az időtartam (0-5 másodperc) hozzá lesz adva az exp igényhez, és levonásra kerül az iats, auth_time és nbf értékeiből.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Lehetővé teszi az alkalmazások számára, hogy lekérjék a profil-, e-mail-, telefon- és címadatokat az ID tokenből.",
+      "CLOCKSKEW": "Lehetővé teszi az alkalmazások számára az OP és az alkalmazás óraeltolódásának kezelését. Az időtartam (0-5 másodperc) hozzá lesz adva az exp igényhez, és levonásra kerül az iats, auth_time és nbf értékeiből.",
      "RECOMMENDED": "ajánlott",
      "NOTRECOMMENDED": "nem ajánlott",
      "SELECTION": {
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Kunci Web Aktif dan Mendatang",
          "DESCRIPTION": "Kunci web Anda yang aktif dan akan datang. Mengaktifkan kunci baru akan menonaktifkan kunci yang sedang digunakan.",
-          "NOTE": "Catatan: Endpoint JWKs OIDC mengembalikan respons yang dapat di-cache (default 5 menit). Hindari mengaktifkan kunci terlalu cepat, karena mungkin belum tersedia di cache dan klien.",
+          "NOTE": "Catatan: Endpoint JWKs OIDC mengembalikan respons yang dapat di-cache (default 5 menit). Hindari mengaktifkan kunci terlalu cepat, karena mungkin belum tersedia di cache dan aplikasi.",
          "ACTIVATE": "Aktifkan Kunci Web Berikutnya",
          "ACTIVE": "Saat ini aktif",
          "NEXT": "Berikutnya dalam antrean",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "Memiliki izin untuk membuat dan mengelola pengguna",
    "IAM_ADMIN_IMPERSONATOR": "Memiliki izin untuk menyamar sebagai admin dan pengguna akhir dari semua organisasi",
    "IAM_END_USER_IMPERSONATOR": "Memiliki izin untuk meniru identitas pengguna akhir dari semua organisasi",
-    "IAM_LOGIN_CLIENT": "Memiliki izin untuk mengelola klien masuk",
+    "IAM_LOGIN_CLIENT": "Memiliki izin untuk mengelola aplikasi masuk",
    "ORG_OWNER": "Memiliki izin atas seluruh organisasi",
    "ORG_USER_MANAGER": "Memiliki izin untuk membuat dan mengelola pengguna organisasi",
    "ORG_OWNER_VIEWER": "Memiliki izin untuk meninjau seluruh organisasi",
@@ -1641,7 +1641,7 @@
      "ACTIONS_DESCRIPTION": "Tindakan v2 memungkinkan untuk mengelola eksekusi dan target data. Jika tanda ini diaktifkan, Anda akan dapat menggunakan API baru dan fitur-fiturnya.",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "If the flag is enabled, the OIDC parent error will be logged in the console.",
      "ENABLEBACKCHANNELLOGOUT": "Enable Backchannel Logout",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "The Back-Channel Logout implements OpenID Connect Back-Channel Logout 1.0 and can be used to notify clients about session termination at the OpenID Provider.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "The Back-Channel Logout implements OpenID Connect Back-Channel Logout 1.0 and can be used to notify applications about session termination at the OpenID Provider.",
      "PERMISSIONCHECKV2": "Permission Check V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "If the flag is enabled, you'll be able to use the new API and its features.",
      "STATES": {
@@ -2656,8 +2656,8 @@
      "IDTOKENROLEASSERTION": "Peran pengguna di dalam Token ID",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Jika dipilih, peran yang diminta dari pengguna yang diautentikasi akan ditambahkan ke token ID.",
      "IDTOKENUSERINFOASSERTION": "Info Pengguna di dalam Token ID",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Memungkinkan klien untuk mengambil klaim profil, email, telepon dan alamat dari token ID.",
-      "CLOCKSKEW": "Memungkinkan klien untuk menangani kemiringan jam OP dan klien. Durasi (0-5 detik) akan ditambahkan ke klaim exp dan dikurangi dari iats, auth_time, dan nbf.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Memungkinkan aplikasi untuk mengambil klaim profil, email, telepon dan alamat dari token ID.",
+      "CLOCKSKEW": "Memungkinkan aplikasi untuk menangani kemiringan jam OP dan aplikasi. Durasi (0-5 detik) akan ditambahkan ke klaim exp dan dikurangi dari iats, auth_time, dan nbf.",
      "RECOMMENDED": "direkomendasikan",
      "NOTRECOMMENDED": "tidak disarankan",
      "SELECTION": {
@@ -34,7 +34,7 @@
    },
    "PROJECTS": {
      "TITLE": "Progetti",
-      "DESCRIPTION": "Un progetto ospita una o più applicazioni, che puoi utilizzare per autenticare i tuoi utenti. Ad esempio, potresti avere un singolo progetto con 3 applicazioni: una per il tuo frontend web, una per la tua app mobile e una per il tuo backend. Puoi anche autorizzare i tuoi utenti con i progetti. Per permettere agli utenti di altre organizzazioni di accedere alle tue applicazioni, concedi loro l'accesso al tuo progetto.<br/><br/>Se non riesci a trovare un progetto, contatta il proprietario del progetto o qualcuno con i diritti corrispondenti per ottenere l'accesso.",
+      "DESCRIPTION": "Un progetto ospita una o più applicazioni, che puoi utilizzare per autenticare i tuoi utenti. Ad esempio, potresti avere un singolo progetto con 3 applicazioni: una per il tuo frontend web, una per la tua applicazione mobile e una per il tuo backend. Puoi anche autorizzare i tuoi utenti con i progetti. Per permettere agli utenti di altre organizzazioni di accedere alle tue applicazioni, concedi loro l'accesso al tuo progetto.<br/><br/>Se non riesci a trovare un progetto, contatta il proprietario del progetto o qualcuno con i diritti corrispondenti per ottenere l'accesso.",
      "OWNED": {
        "TITLE": "Progetti di Proprietà",
        "DESCRIPTION": "Questi sono i progetti che possiedi. Puoi gestire le impostazioni di questi progetti, le autorizzazioni e le applicazioni."
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Chiavi Web Attive e Future",
          "DESCRIPTION": "Le tue chiavi web attive e future. L'attivazione di una nuova chiave disattiverà quella attuale.",
-          "NOTE": "Nota: L'endpoint JWKs OIDC restituisce una risposta memorizzabile nella cache (predefinito 5 min). Evita di attivare una chiave troppo presto, poiché potrebbe non essere ancora disponibile nelle cache e nei client.",
+          "NOTE": "Nota: L'endpoint JWKs OIDC restituisce una risposta memorizzabile nella cache (predefinito 5 min). Evita di attivare una chiave troppo presto, poiché potrebbe non essere ancora disponibile nelle cache e nelle applicazioni.",
          "ACTIVATE": "Attiva la prossima Chiave Web",
          "ACTIVE": "Attualmente attiva",
          "NEXT": "Prossima in coda",
@@ -386,12 +386,12 @@
        "action": "Crea progetto"
      },
      "APPLICATION_CREATED": {
-        "title": "Registra la tua app",
+        "title": "Registra la tua applicazione",
        "description": "Registra la tua applicazione web, nativa, api o saml e configura un flusso di autenticazione.",
-        "action": "Registra app"
+        "action": "Registra applicazione"
      },
      "AUTHENTICATION_SUCCEEDED_ON_APPLICATION": {
-        "title": "Accedi alla tua app",
+        "title": "Accedi alla tua applicazione",
        "description": "Integra la tua applicazione con Zitadel per l'autenticazione e testala accedendo con il tuo utente amministratore.",
        "action": "Accedi"
      },
@@ -453,7 +453,7 @@
    "DEVMODEWARN": "La modalità sviluppatore è abilitata per impostazione predefinita. È possibile aggiornare i valori per la produzione in un secondo momento.",
    "GUIDE": "Guida",
    "BROWSEEXAMPLES": "Esplora esempi e SDK",
-    "DUPLICATEAPPRENAME": "Un'app con lo stesso nome esiste già. Scegli un nome diverso.",
+    "DUPLICATEAPPRENAME": "Un'applicazione con lo stesso nome esiste già. Scegli un nome diverso.",
    "DIALOG": {
      "CHANGE": {
        "TITLE": "Modifica framework",
@@ -655,7 +655,7 @@
    "IAM_USER_MANAGER": "Ha l'autorizzazione per creare e gestire utenti",
    "IAM_ADMIN_IMPERSONATOR": "Dispone dell'autorizzazione per rappresentare l'amministratore e gli utenti finali di tutte le organizzazioni",
    "IAM_END_USER_IMPERSONATOR": "Dispone dell'autorizzazione per rappresentare gli utenti finali di tutte le organizzazioni",
-    "IAM_LOGIN_CLIENT": "Ha il permesso di gestire i client di accesso",
+    "IAM_LOGIN_CLIENT": "Ha il permesso di gestire le applicazioni di accesso",
    "ORG_OWNER": "Ha il permesso su tutta l'organizzazione",
    "ORG_USER_MANAGER": "Ha l'autorizzazione per creare e gestire gli utenti dell'organizzazione",
    "ORG_OWNER_VIEWER": "Ha il permesso di esaminare l'intera organizzazione",
@@ -883,9 +883,9 @@
      "DESCRIPTION": "Aggiungi un secondo fattore per garantire la sicurezza ottimale del tuo account.",
      "MANAGE_DESCRIPTION": "Gestite i metodi del secondo fattore dei vostri utenti.",
      "ADD": "Aggiungi fattore",
-      "OTP": "App di autenticazione per TOTP (Time-based One-Time Password)",
+      "OTP": "Applicazione di autenticazione per TOTP (Time-based One-Time Password)",
      "OTP_DIALOG_TITLE": "Aggiungi TOTP",
-      "OTP_DIALOG_DESCRIPTION": "Scansiona il codice QR con un'app di autenticazione e inserisci il codice nel campo sottostante per verificare e attivare il metodo OTP.",
+      "OTP_DIALOG_DESCRIPTION": "Scansiona il codice QR con un'applicazione di autenticazione e inserisci il codice nel campo sottostante per verificare e attivare il metodo OTP.",
      "U2F": "Passkey",
      "U2F_DIALOG_TITLE": "Verifica Fattore",
      "U2F_DIALOG_DESCRIPTION": "Inserisci un nome per il tuo methodo o dispositivo.",
@@ -1644,7 +1644,7 @@
      "DEBUGOIDCPARENTERROR": "Debug OIDC Parent Error",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Se il flag è abilitato, l'errore OIDC originante verrà registrato nella console.",
      "ENABLEBACKCHANNELLOGOUT": "Abilita Backchannel Logout",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Il Back-Channel Logout implementa OpenID Connect Back-Channel Logout 1.0 e può essere utilizzato per notificare ai client la terminazione della sessione presso il provider OpenID.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Il Back-Channel Logout implementa OpenID Connect Back-Channel Logout 1.0 e può essere utilizzato per notificare alle applicazioni la terminazione della sessione presso il provider OpenID.",
      "PERMISSIONCHECKV2": "Controllo permessi V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Se il flag è abilitato, potrai utilizzare la nuova API e le sue funzionalità.",
      "STATES": {
@@ -2409,7 +2409,7 @@
    },
    "SECONDFACTORTYPES": {
      "0": "Sconosciuto",
-      "1": "One Time Password per Authenticator App (TOTP)",
+      "1": "One Time Password per applicazione di autenticazione (TOTP)",
      "2": "Passkey",
      "3": "One Time Password per Email (Email OTP)",
      "4": "One Time Password per SMS (SMS OTP)",
@@ -2634,7 +2634,7 @@
      "IDTOKENROLEASSERTION_DESCRIPTION": "Se selezionato, i ruoli richiesti dall'utente autenticato sono aggiunti all'ID Token.",
      "IDTOKENUSERINFOASSERTION": "Aggiungi le informazioni dell'utente nell'ID Token",
      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Aggiungi le richieste di profilo, email, telefono o indirizzo nell'ID Token.",
-      "CLOCKSKEW": "Permette ai clienti di gestire lo skew di OP e client. La durata (0-5s) sarà aggiunta a exp claim e sottratta da iats, auth_time e nbf.",
+      "CLOCKSKEW": "Permette alle applicazioni di gestire lo skew di OP e applicazione. La durata (0-5s) sarà aggiunta a exp claim e sottratta da iats, auth_time e nbf.",
      "RECOMMENDED": "raccomandato",
      "NOTRECOMMENDED": "non raccomandato",
      "SELECTION": {
@@ -34,7 +34,7 @@
    },
    "PROJECTS": {
      "TITLE": "プロジェクト",
-      "DESCRIPTION": "プロジェクトは、ユーザーを認証するために使用できる1つ以上のアプリケーションをホストします。例えば、Webフロントエンド、モバイルアプリ、バックエンド用にそれぞれ1つずつ、合計3つのアプリケーションを持つ単一のプロジェクトを持つことができます。また、プロジェクトでユーザーに権限を与えることもできます。他の組織のユーザーがあなたのアプリケーションにログインできるようにするには、プロジェクトへのアクセスを許可してください。<br/><br/>プロジェクトが見つからない場合は、プロジェクトの所有者または対応する権利を持つ人に連絡してアクセスを取得してください。",
+      "DESCRIPTION": "プロジェクトは、ユーザーを認証するために使用できる1つ以上のアプリケーションをホストします。例えば、Webフロントエンド、モバイルアプリケーション、バックエンド用にそれぞれ1つずつ、合計3つのアプリケーションを持つ単一のプロジェクトを持つことができます。また、プロジェクトでユーザーに権限を与えることもできます。他の組織のユーザーがあなたのアプリケーションにログインできるようにするには、プロジェクトへのアクセスを許可してください。<br/><br/>プロジェクトが見つからない場合は、プロジェクトの所有者または対応する権利を持つ人に連絡してアクセスを取得してください。",
      "OWNED": {
        "TITLE": "所有しているプロジェクト",
        "DESCRIPTION": "これらはあなたが所有しているプロジェクトです。これらのプロジェクトの設定、権限、アプリケーションを管理できます。"
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "アクティブおよび今後のWebキー",
          "DESCRIPTION": "現在アクティブなWebキーと、今後使用予定のWebキーです。新しいキーをアクティブ化すると、現在のキーは無効になります。",
-          "NOTE": "注意: JWKs OIDCエンドポイントはキャッシュ可能なレスポンスを返します（デフォルト5分）。キーを早くアクティブ化しすぎると、キャッシュやクライアントでまだ利用できない可能性があります。",
+          "NOTE": "注意: JWKs OIDCエンドポイントはキャッシュ可能なレスポンスを返します（デフォルト5分）。キーを早くアクティブ化しすぎると、キャッシュやアプリケーションでまだ利用できない可能性があります。",
          "ACTIVATE": "次のWebキーをアクティブ化",
          "ACTIVE": "現在アクティブ",
          "NEXT": "次のキュー",
@@ -386,12 +386,12 @@
        "action": "プロジェクトを作成"
      },
      "APPLICATION_CREATED": {
-        "title": "アプリを登録する",
+        "title": "アプリケーションを登録する",
        "description": "Web、ネイティブ、API、またはSAMLアプリケーションを登録し、認証フローをセットアップします。",
-        "action": "アプリを登録する"
+        "action": "アプリケーションを登録する"
      },
      "AUTHENTICATION_SUCCEEDED_ON_APPLICATION": {
-        "title": "アプリにログインする",
+        "title": "アプリケーションにログインする",
        "description": "アプリケーションをZitadelと統合して認証し、管理者ユーザーでログインしてテストします。",
        "action": "ログイン"
      },
@@ -453,7 +453,7 @@
    "DEVMODEWARN": "開発モードはデフォルトで有効になっています。実稼働用の値は後で更新できます。",
    "GUIDE": "ガイド",
    "BROWSEEXAMPLES": "サンプルを見る",
-    "DUPLICATEAPPRENAME": "同じ名前のアプリがすでに存在します。別の名前を選択してください。",
+    "DUPLICATEAPPRENAME": "同じ名前のアプリケーションがすでに存在します。別の名前を選択してください。",
    "DIALOG": {
      "CHANGE": {
        "TITLE": "変更の枠組み",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "ユーザーの作成および管理する権限を持ちます",
    "IAM_ADMIN_IMPERSONATOR": "すべての組織の管理者およびエンドユーザーになりすます権限を持っています",
    "IAM_END_USER_IMPERSONATOR": "すべての組織のエンドユーザーになりすます権限を持っています",
-    "IAM_LOGIN_CLIENT": "ログインクライアントを管理する権限を持っています",
+    "IAM_LOGIN_CLIENT": "ログインアプリケーションを管理する権限を持っています",
    "ORG_OWNER": "組織全体に対する権限を持ちます",
    "ORG_USER_MANAGER": "組織のユーザーを作成および管理する権限を持ちます",
    "ORG_OWNER_VIEWER": "組織全体を閲覧する権限を持ちます",
@@ -884,9 +884,9 @@
      "DESCRIPTION": "二要素認証を追加して、アカウントに最適なセキュリティを確保します。",
      "MANAGE_DESCRIPTION": "ユーザーの二要素認証を管理する。",
      "ADD": "二要素認証を追加する",
-      "OTP": "TOTP用認証アプリ（ワンタイム・パスワード）",
+      "OTP": "TOTP用認証アプリケーション（ワンタイム・パスワード）",
      "OTP_DIALOG_TITLE": "OTPの追加",
-      "OTP_DIALOG_DESCRIPTION": "認証アプリでQRコードを読み取り、下記のコードを入力することで、OTP方式の確認と有効化ができます。",
+      "OTP_DIALOG_DESCRIPTION": "認証アプリケーションでQRコードを読み取り、下記のコードを入力することで、OTP方式の確認と有効化ができます。",
      "U2F": "パスキー",
      "U2F_DIALOG_TITLE": "二要素認証の検証",
      "U2F_DIALOG_DESCRIPTION": "使用済みの二要素認証の名前を入力する。",
@@ -1611,7 +1611,7 @@
        "3": "電話番号認証",
        "4": "パスワードのリセット",
        "5": "パスキーの初期設定",
-        "6": "アプリのシークレット",
+        "6": "アプリケーションのシークレット",
        "7": "ワンタイムパスワード (OTP) - SMS",
        "8": "ワンタイムパスワード (OTP) - 電子メール"
      },
@@ -1644,7 +1644,7 @@
      "DEBUGOIDCPARENTERROR": "デバッグ OIDC 親エラー",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "フラグが有効になっている場合、OIDC 親エラーはコンソールに記録されます。",
      "ENABLEBACKCHANNELLOGOUT": "バックチャネルログアウトを有効にする",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "バックチャネルログアウトは OpenID Connect バックチャネルログアウト 1.0 を実装し、OpenID プロバイダーでのセッション終了についてクライアントに通知するために使用できます。",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "バックチャネルログアウトは OpenID Connect バックチャネルログアウト 1.0 を実装し、OpenID プロバイダーでのセッション終了についてアプリケーションに通知するために使用できます。",
      "PERMISSIONCHECKV2": "権限チェック V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "フラグが有効になっている場合、新しい API とその機能を使用できます。",
      "STATES": {
@@ -2430,7 +2430,7 @@
    },
    "SECONDFACTORTYPES": {
      "0": "不明",
-      "1": "認証アプリ用ワンタイムパスワード(TOTP)",
+      "1": "認証アプリケーション用ワンタイムパスワード(TOTP)",
      "2": "パスキー",
      "3": "Eメール用ワンタイムパスワード（email OTP）",
      "4": "SMS用ワンタイムパスワード（SMS OTP）",
@@ -2658,8 +2658,8 @@
      "IDTOKENROLEASSERTION": "IDトークン内のユーザーロール",
      "IDTOKENROLEASSERTION_DESCRIPTION": "選択した場合、認証されたユーザーの要求されたロールがIDトークンに追加されます。",
      "IDTOKENUSERINFOASSERTION": "IDトークン内のユーザー情報",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "クライアントは、IDトークンからプロフィール、メール、電話、住所のクレームを取得できます。",
-      "CLOCKSKEW": "OPとクライアントのクロックスキューをクライアントが処理できるようにします。持続時間（0～5s）は、exp claimに加算され、iats、auth_timeおよびnbfから減算されます。",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "アプリケーションは、IDトークンからプロフィール、メール、電話、住所のクレームを取得できます。",
+      "CLOCKSKEW": "OPとアプリケーションのクロックスキューをアプリケーションが処理できるようにします。持続時間（0～5s）は、exp claimに加算され、iats、auth_timeおよびnbfから減算されます。",
      "RECOMMENDED": "推奨",
      "NOTRECOMMENDED": "非推奨",
      "SELECTION": {
@@ -34,7 +34,7 @@
    },
    "PROJECTS": {
      "TITLE": "프로젝트",
-      "DESCRIPTION": "프로젝트는 하나 이상의 애플리케이션을 호스팅하여 사용자를 인증할 수 있습니다. 예를 들어, 웹 프론트엔드, 모바일 앱, 백엔드용으로 각각 하나씩, 총 3개의 애플리케이션을 가진 단일 프로젝트를 가질 수 있습니다. 또한 프로젝트를 통해 사용자에게 권한을 부여할 수 있습니다. 다른 조직의 사용자가 애플리케이션에 로그인할 수 있도록 프로젝트에 대한 액세스를 부여하세요.<br/><br/>프로젝트를 찾을 수 없는 경우 프로젝트 소유자 또는 관련 권한이 있는 사람에게 문의하여 액세스를 얻으세요.",
+      "DESCRIPTION": "프로젝트는 하나 이상의 애플리케이션을 호스팅하여 사용자를 인증할 수 있습니다. 예를 들어, 웹 프론트엔드, 모바일 애플리케이션, 백엔드용으로 각각 하나씩, 총 3개의 애플리케이션을 가진 단일 프로젝트를 가질 수 있습니다. 또한 프로젝트를 통해 사용자에게 권한을 부여할 수 있습니다. 다른 조직의 사용자가 애플리케이션에 로그인할 수 있도록 프로젝트에 대한 액세스를 부여하세요.<br/><br/>프로젝트를 찾을 수 없는 경우 프로젝트 소유자 또는 관련 권한이 있는 사람에게 문의하여 액세스를 얻으세요.",
      "OWNED": {
        "TITLE": "소유한 프로젝트",
        "DESCRIPTION": "이 프로젝트는 사용자가 소유한 프로젝트입니다. 프로젝트 설정, 권한 및 애플리케이션을 관리할 수 있습니다."
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "활성 및 예정된 웹 키",
          "DESCRIPTION": "현재 활성화된 웹 키와 앞으로 활성화될 웹 키입니다. 새로운 키를 활성화하면 기존 키는 비활성화됩니다.",
-          "NOTE": "참고: JWKs OIDC 엔드포인트는 캐시 가능한 응답을 반환합니다 (기본값: 5분). 키를 너무 빨리 활성화하면 캐시 및 클라이언트에서 아직 사용할 수 없을 수 있습니다.",
+          "NOTE": "참고: JWKs OIDC 엔드포인트는 캐시 가능한 응답을 반환합니다 (기본값: 5분). 키를 너무 빨리 활성화하면 캐시 및 애플리케이션에서 아직 사용할 수 없을 수 있습니다.",
          "ACTIVATE": "다음 웹 키 활성화",
          "ACTIVE": "현재 활성화됨",
          "NEXT": "대기 중인 다음 키",
@@ -386,12 +386,12 @@
        "action": "프로젝트 생성"
      },
      "APPLICATION_CREATED": {
-        "title": "앱 등록",
+        "title": "애플리케이션 등록",
        "description": "웹, 네이티브, API 또는 SAML 애플리케이션을 등록하고 인증 플로우를 설정하세요.",
-        "action": "앱 등록"
+        "action": "애플리케이션 등록"
      },
      "AUTHENTICATION_SUCCEEDED_ON_APPLICATION": {
-        "title": "앱에 로그인",
+        "title": "애플리케이션에 로그인",
        "description": "Zitadel로 애플리케이션을 통합하고 관리자 사용자로 로그인하여 테스트하세요.",
        "action": "로그인"
      },
@@ -453,7 +453,7 @@
    "DEVMODEWARN": "개발 모드가 기본으로 활성화되어 있습니다. 운영 환경에서는 나중에 설정 값을 변경할 수 있습니다.",
    "GUIDE": "가이드",
    "BROWSEEXAMPLES": "예제 및 SDK 둘러보기",
-    "DUPLICATEAPPRENAME": "같은 이름의 앱이 이미 존재합니다. 다른 이름을 선택하세요.",
+    "DUPLICATEAPPRENAME": "같은 이름의 애플리케이션이 이미 존재합니다. 다른 이름을 선택하세요.",
    "DIALOG": {
      "CHANGE": {
        "TITLE": "프레임워크 변경",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "사용자를 생성하고 관리할 수 있는 권한이 있습니다",
    "IAM_ADMIN_IMPERSONATOR": "모든 조직의 관리자와 최종 사용자를 대리할 수 있는 권한이 있습니다",
    "IAM_END_USER_IMPERSONATOR": "모든 조직의 최종 사용자를 대리할 수 있는 권한이 있습니다",
-    "IAM_LOGIN_CLIENT": "로그인 클라이언트를 관리할 수 있는 권한이 있습니다",
+    "IAM_LOGIN_CLIENT": "로그인 애플리케이션을 관리할 수 있는 권한이 있습니다",
    "ORG_OWNER": "조직에 대한 전체 권한이 있습니다",
    "ORG_USER_MANAGER": "조직의 사용자를 생성하고 관리할 수 있는 권한이 있습니다",
    "ORG_OWNER_VIEWER": "조직 전체를 검토할 수 있는 권한이 있습니다",
@@ -884,9 +884,9 @@
      "DESCRIPTION": "계정의 보안을 위해 두 번째 인증 요소를 추가하세요.",
      "MANAGE_DESCRIPTION": "사용자의 두 번째 인증 방법을 관리하세요.",
      "ADD": "인증 요소 추가",
-      "OTP": "TOTP (시간 기반 일회용 비밀번호)용 인증 앱",
+      "OTP": "TOTP (시간 기반 일회용 비밀번호)용 인증 애플리케이션",
      "OTP_DIALOG_TITLE": "OTP 추가",
-      "OTP_DIALOG_DESCRIPTION": "인증 앱으로 QR 코드를 스캔하고, 아래에 코드를 입력하여 OTP 방법을 검증하고 활성화하세요.",
+      "OTP_DIALOG_DESCRIPTION": "인증 애플리케이션으로 QR 코드를 스캔하고, 아래에 코드를 입력하여 OTP 방법을 검증하고 활성화하세요.",
      "U2F": "지문, 보안 키, Face ID 및 기타",
      "U2F_DIALOG_TITLE": "인증 요소 확인",
      "U2F_DIALOG_DESCRIPTION": "사용할 다중 인증의 이름을 입력하세요.",
@@ -1611,7 +1611,7 @@
        "3": "전화 검증",
        "4": "비밀번호 재설정",
        "5": "패스키 초기화",
-        "6": "앱 시크릿",
+        "6": "애플리케이션 시크릿",
        "7": "일회성 비밀번호 (OTP) - SMS",
        "8": "일회성 비밀번호 (OTP) - 이메일"
      },
@@ -1644,7 +1644,7 @@
      "DEBUGOIDCPARENTERROR": "디버그 OIDC 부모 오류",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "플래그가 활성화되면 OIDC 부모 오류가 콘솔에 기록됩니다.",
      "ENABLEBACKCHANNELLOGOUT": "백채널 로그아웃 활성화",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "백채널 로그아웃은 OpenID Connect 백채널 로그아웃 1.0을 구현하며, OpenID 제공자에서 세션 종료에 대해 클라이언트에게 알리는 데 사용할 수 있습니다.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "백채널 로그아웃은 OpenID Connect 백채널 로그아웃 1.0을 구현하며, OpenID 제공자에서 세션 종료에 대해 애플리케이션에게 알리는 데 사용할 수 있습니다.",
      "PERMISSIONCHECKV2": "권한 확인 V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "플래그가 활성화되면 새로운 API와 그 기능을 사용할 수 있습니다.",
      "STATES": {
@@ -2430,7 +2430,7 @@
    },
    "SECONDFACTORTYPES": {
      "0": "알 수 없음",
-      "1": "인증 앱을 통한 일회성 비밀번호(TOTP)",
+      "1": "인증 애플리케이션을 통한 일회성 비밀번호(TOTP)",
      "2": "지문, 보안 키, Face ID 및 기타",
      "3": "이메일을 통한 일회성 비밀번호(이메일 OTP)",
      "4": "SMS를 통한 일회성 비밀번호(SMS OTP)",
@@ -2658,8 +2658,8 @@
      "IDTOKENROLEASSERTION": "ID 토큰에 사용자 역할 추가",
      "IDTOKENROLEASSERTION_DESCRIPTION": "선택 시 인증된 사용자의 요청된 역할이 ID 토큰에 추가됩니다.",
      "IDTOKENUSERINFOASSERTION": "ID 토큰 내 사용자 정보",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "클라이언트가 ID 토큰에서 프로필, 이메일, 전화번호 및 주소 클레임을 검색할 수 있습니다.",
-      "CLOCKSKEW": "OP와 클라이언트 간의 시간 오차를 처리할 수 있도록 허용합니다. (0-5초) 동안 exp 클레임에 추가되고 iats, auth_time 및 nbf에서 감소됩니다.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "애플리케이션이 ID 토큰에서 프로필, 이메일, 전화번호 및 주소 클레임을 검색할 수 있습니다.",
+      "CLOCKSKEW": "OP와 애플리케이션 간의 시간 오차를 처리할 수 있도록 허용합니다. (0-5초) 동안 exp 클레임에 추가되고 iats, auth_time 및 nbf에서 감소됩니다.",
      "RECOMMENDED": "권장",
      "NOTRECOMMENDED": "권장하지 않음",
      "SELECTION": {
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Активни и Идни Веб-Клучеви",
          "DESCRIPTION": "Вашите активни и претстојни веб-клучеви. Активирањето на нов клуч ќе го деактивира тековниот.",
-          "NOTE": "Забелешка: JWKs OIDC крајната точка враќа одговор што може да се кешира (стандардно 5 минути). Избегнувајте активирање на клучот пребрзо, бидејќи можеби сè уште не е достапен во кешот и кај клиентите.",
+          "NOTE": "Забелешка: JWKs OIDC крајната точка враќа одговор што може да се кешира (стандардно 5 минути). Избегнувајте активирање на клучот пребрзо, бидејќи можеби сè уште не е достапен во кешот и кај апликациите.",
          "ACTIVATE": "Активирај го следниот веб-клуч",
          "ACTIVE": "Моментално активен",
          "NEXT": "Следен во редот",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "Има дозвола за креирање и менаџирање на корисници",
    "IAM_ADMIN_IMPERSONATOR": "Има дозвола да се претставува како администратор и крајни корисници од сите организации",
    "IAM_END_USER_IMPERSONATOR": "Има дозвола да ги имитира крајните корисници од сите организации",
-    "IAM_LOGIN_CLIENT": "Има дозвола за менаџирање на клиенти за најава",
+    "IAM_LOGIN_CLIENT": "Има дозвола за менаџирање на апликации за најава",
    "ORG_OWNER": "Има дозвола врз целата организација",
    "ORG_USER_MANAGER": "Има дозвола за креирање и менаџирање на корисници во организацијата",
    "ORG_OWNER_VIEWER": "Има дозвола за преглед на целата организација",
@@ -1645,7 +1645,7 @@
      "DEBUGOIDCPARENTERROR": "Дебагирање на OIDC родителска грешка",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Ако знамето е овозможено, грешката на OIDC родителот ќе биде регистрирана во конзолата.",
      "ENABLEBACKCHANNELLOGOUT": "Овозможи Backchannel Logout",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Back-Channel Logout имплементира OpenID Connect Back-Channel Logout 1.0 и може да се користи за известување на клиентите за завршување на сесијата кај OpenID провајдерот.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Back-Channel Logout имплементира OpenID Connect Back-Channel Logout 1.0 и може да се користи за известување на апликациите за завршување на сесијата кај OpenID провајдерот.",
      "PERMISSIONCHECKV2": "Проверка на дозволи V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Ако знамето е овозможено, ќе можете да ја користите новата API и нејзините функции.",
      "STATES": {
@@ -2629,8 +2629,8 @@
      "IDTOKENROLEASSERTION": "Улоги на корисникот внатре во ID токенот",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Ако е избрано, се додаваат бараните улоги на автентицираниот корисник во ID токенот.",
      "IDTOKENUSERINFOASSERTION": "Информации за корисникот внатре во ID токенот",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Овозможува клиентите да добијат информации за профилот, е-поштата, телефонскиот број и адресите од ID токенот.",
-      "CLOCKSKEW": "Овозможува клиентите да се справуваат со временски неподесеностите меѓу OP и клиентот. Времетраењето (0-5 сек.) ќе биде додадено на exp claim и одземено од iats, auth_time и nbf.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Овозможува апликациите да добијат информации за профилот, е-поштата, телефонскиот број и адресите од ID токенот.",
+      "CLOCKSKEW": "Овозможува апликациите да се справуваат со временски неподесеностите меѓу OP и апликацијата. Времетраењето (0-5 сек.) ќе биде додадено на exp claim и одземено од iats, auth_time и nbf.",
      "RECOMMENDED": "препорачано",
      "NOTRECOMMENDED": "не препорачано",
      "SELECTION": {
@@ -34,7 +34,7 @@
    },
    "PROJECTS": {
      "TITLE": "Projecten",
-      "DESCRIPTION": "Een project host een of meer applicaties, die je kunt gebruiken om je gebruikers te authenticeren. Bijvoorbeeld, je zou een enkel project kunnen hebben met 3 applicaties; een voor je web frontend, een voor je mobiele app, en een voor je backend. Ook kun je je gebruikers autoriseren met projecten. Om gebruikers van andere organisaties in staat te stellen in te loggen op je applicaties, geef ze toegang tot je project.<br/><br/>Als je een project niet kunt vinden, neem dan contact op met de eigenaar van het project of iemand met de bijbehorende rechten om toegang te krijgen.",
+      "DESCRIPTION": "Een project host een of meer applicaties, die je kunt gebruiken om je gebruikers te authenticeren. Bijvoorbeeld, je zou een enkel project kunnen hebben met 3 applicaties; een voor je web frontend, een voor je mobiele applicatie, en een voor je backend. Ook kun je je gebruikers autoriseren met projecten. Om gebruikers van andere organisaties in staat te stellen in te loggen op je applicaties, geef ze toegang tot je project.<br/><br/>Als je een project niet kunt vinden, neem dan contact op met de eigenaar van het project of iemand met de bijbehorende rechten om toegang te krijgen.",
      "OWNED": {
        "TITLE": "Eigen Projecten",
        "DESCRIPTION": "Dit zijn de projecten die je bezit. Je kunt de instellingen van deze projecten, autorisaties en applicaties beheren."
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Actieve en Toekomstige Websleutels",
          "DESCRIPTION": "Je actieve en aankomende websleutels. Het activeren van een nieuwe sleutel deactiveert de huidige.",
-          "NOTE": "Opmerking: Het JWKs OIDC-eindpunt geeft een cachebare respons terug (standaard 5 minuten). Vermijd het te vroeg activeren van een sleutel, omdat deze mogelijk nog niet beschikbaar is in caches en bij clients.",
+          "NOTE": "Opmerking: Het JWKs OIDC-eindpunt geeft een cachebare respons terug (standaard 5 minuten). Vermijd het te vroeg activeren van een sleutel, omdat deze mogelijk nog niet beschikbaar is in caches en bij applicaties.",
          "ACTIVATE": "Volgende Websleutel activeren",
          "ACTIVE": "Momenteel actief",
          "NEXT": "Volgende in de wachtrij",
@@ -386,12 +386,12 @@
        "action": "Project aanmaken"
      },
      "APPLICATION_CREATED": {
-        "title": "Registreer uw app",
+        "title": "Registreer uw applicatie",
        "description": "Registreer uw web-, native-, api- of saml-applicatie en stel een authenticatiestroom in.",
-        "action": "App registreren"
+        "action": "Applicatie registreren"
      },
      "AUTHENTICATION_SUCCEEDED_ON_APPLICATION": {
-        "title": "Log in op uw app",
+        "title": "Log in op uw applicatie",
        "description": "Integreer uw applicatie met Zitadel voor authenticatie en test het door in te loggen met uw beheerdersgebruiker.",
        "action": "Log in"
      },
@@ -453,7 +453,7 @@
    "DEVMODEWARN": "Dev-modus is standaard ingeschakeld. U kunt waarden voor productie later bijwerken.",
    "GUIDE": "Guide",
    "BROWSEEXAMPLES": "Bekijk voorbeelden",
-    "DUPLICATEAPPRENAME": "Er bestaat al een app met dezelfde aartsvijand. Kies een andere naam.",
+    "DUPLICATEAPPRENAME": "Er bestaat al een applicatie met dezelfde aartsvijand. Kies een andere naam.",
    "DIALOG": {
      "CHANGE": {
        "TITLE": "Verander Framework",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "Heeft toestemming om gebruikers aan te maken en te beheren",
    "IAM_ADMIN_IMPERSONATOR": "Heeft toestemming om zich voor te doen als beheerder en eindgebruikers van alle organisaties",
    "IAM_END_USER_IMPERSONATOR": "Heeft toestemming om eindgebruikers van alle organisaties na te bootsen",
-    "IAM_LOGIN_CLIENT": "Heeft toestemming om aanmeldklanten te beheren",
+    "IAM_LOGIN_CLIENT": "Heeft toestemming om aanmeldapplicaties te beheren",
    "ORG_OWNER": "Heeft toestemming over de hele organisatie",
    "ORG_USER_MANAGER": "Heeft toestemming om gebruikers van de organisatie aan te maken en te beheren",
    "ORG_OWNER_VIEWER": "Heeft toestemming om de hele organisatie te bekijken",
@@ -884,9 +884,9 @@
      "DESCRIPTION": "Voeg een tweede factor toe om optimale beveiliging voor uw account te garanderen.",
      "MANAGE_DESCRIPTION": "Beheer de tweede factor-methoden van uw gebruikers.",
      "ADD": "Factor toevoegen",
-      "OTP": "Authenticator App voor TOTP (Time-based One-Time Password)",
+      "OTP": "Authenticator Applicatie voor TOTP (Time-based One-Time Password)",
      "OTP_DIALOG_TITLE": "Voeg OTP toe",
-      "OTP_DIALOG_DESCRIPTION": "Scan de QR-code met een authenticator-app en voer de code hieronder in om de OTP-methode te verifiëren en te activeren.",
+      "OTP_DIALOG_DESCRIPTION": "Scan de QR-code met een authenticator-applicatie en voer de code hieronder in om de OTP-methode te verifiëren en te activeren.",
      "U2F": "Vingerafdruk, beveiligingssleutels, gezichtsherkenning en andere",
      "U2F_DIALOG_TITLE": "Verifieer factor",
      "U2F_DIALOG_DESCRIPTION": "Voer een naam in voor uw gebruikte universele multifactor.",
@@ -1611,7 +1611,7 @@
        "3": "Telefoon verificatie",
        "4": "Wachtwoord Reset",
        "5": "Passkey Initialisatie",
-        "6": "App Secret",
+        "6": "Applicatie Secret",
        "7": "Eenmalig Wachtwoord (OTP) - SMS",
        "8": "Eenmalig Wachtwoord (OTP) - Email"
      },
@@ -1644,7 +1644,7 @@
      "DEBUGOIDCPARENTERROR": "Debug OIDC Ouderfout",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Als de vlag is ingeschakeld, wordt de OIDC-ouderfout in de console geregistreerd.",
      "ENABLEBACKCHANNELLOGOUT": "Backchannel Logout inschakelen",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "De Back-Channel Logout implementeert OpenID Connect Back-Channel Logout 1.0 en kan worden gebruikt om clients te informeren over het beëindigen van de sessie bij de OpenID-provider.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "De Back-Channel Logout implementeert OpenID Connect Back-Channel Logout 1.0 en kan worden gebruikt om applicaties te informeren over het beëindigen van de sessie bij de OpenID-provider.",
      "PERMISSIONCHECKV2": "Permissiecontrole V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Als de vlag is ingeschakeld, kunt u de nieuwe API en de bijbehorende functies gebruiken.",
      "STATES": {
@@ -2427,7 +2427,7 @@
    },
    "SECONDFACTORTYPES": {
      "0": "Onbekend",
-      "1": "Eenmalig wachtwoord door Authenticator App (TOTP)",
+      "1": "Eenmalig wachtwoord door Authenticator Applicatie (TOTP)",
      "2": "Vingerafdruk, Beveiligingssleutels, Face ID en andere",
      "3": "Eenmalig wachtwoord per e-mail (Email OTP)",
      "4": "Eenmalig wachtwoord per SMS (SMS OTP)",
@@ -2651,8 +2651,8 @@
      "IDTOKENROLEASSERTION": "Gebruikersrollen in ID Token",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Indien geselecteerd, worden de aangevraagde rollen van de geauthenticeerde gebruiker toegevoegd aan het ID-token.",
      "IDTOKENUSERINFOASSERTION": "Gebruikersinformatie in ID Token",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Hiermee kunnen clients profiel-, e-mail-, telefoon- en adresclaims van ID-token ophalen.",
-      "CLOCKSKEW": "Hiermee kunnen clients de klok skew van OP en client verwerken. De duur (0-5s) wordt toegevoegd aan exp claim en afgetrokken van iats, auth_time en nbf.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Hiermee kunnen applicaties profiel-, e-mail-, telefoon- en adresclaims van ID-token ophalen.",
+      "CLOCKSKEW": "Hiermee kunnen applicaties de klok skew van OP en applicatie verwerken. De duur (0-5s) wordt toegevoegd aan exp claim en afgetrokken van iats, auth_time en nbf.",
      "RECOMMENDED": "aanbevolen",
      "NOTRECOMMENDED": "niet aanbevolen",
      "SELECTION": {
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Aktywne i Przyszłe Klucze Internetowe",
          "DESCRIPTION": "Twoje aktywne i nadchodzące klucze internetowe. Aktywacja nowego klucza spowoduje dezaktywację obecnego.",
-          "NOTE": "Uwaga: Punkt końcowy JWKs OIDC zwraca odpowiedź możliwą do buforowania (domyślnie 5 minut). Unikaj zbyt wczesnej aktywacji klucza, ponieważ może on nie być jeszcze dostępny w pamięci podręcznej i dla klientów.",
+          "NOTE": "Uwaga: Punkt końcowy JWKs OIDC zwraca odpowiedź możliwą do buforowania (domyślnie 5 minut). Unikaj zbyt wczesnej aktywacji klucza, ponieważ może on nie być jeszcze dostępny w pamięci podręcznej i dla aplikacji.",
          "ACTIVATE": "Aktywuj następny klucz internetowy",
          "ACTIVE": "Obecnie aktywny",
          "NEXT": "Następny w kolejce",
@@ -655,7 +655,7 @@
    "IAM_USER_MANAGER": "Ma uprawnienie do tworzenia i zarządzania użytkownikami",
    "IAM_ADMIN_IMPERSONATOR": "Ma uprawnienia do podszywania się pod administratora i użytkowników końcowych ze wszystkich organizacji",
    "IAM_END_USER_IMPERSONATOR": "Ma uprawnienia do podszywania się pod użytkowników końcowych ze wszystkich organizacji",
-    "IAM_LOGIN_CLIENT": "Ma uprawnienia do zarządzania klientami logowania",
+    "IAM_LOGIN_CLIENT": "Ma uprawnienia do zarządzania aplikacjami logowania",
    "ORG_OWNER": "Ma uprawnienie nad całą organizacją",
    "ORG_USER_MANAGER": "Ma uprawnienie do tworzenia i zarządzania użytkownikami organizacji",
    "ORG_OWNER_VIEWER": "Ma uprawnienie do przeglądania całej organizacji",
@@ -1643,7 +1643,7 @@
      "DEBUGOIDCPARENTERROR": "Debug OIDC Błąd nadrzędny",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Jeśli flaga jest włączona, błąd nadrzędny OIDC zostanie zarejestrowany w konsoli.",
      "ENABLEBACKCHANNELLOGOUT": "Włącz Backchannel Logout",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Back-Channel Logout implementuje OpenID Connect Back-Channel Logout 1.0 i może być używany do powiadamiania klientów o zakończeniu sesji u dostawcy OpenID.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Back-Channel Logout implementuje OpenID Connect Back-Channel Logout 1.0 i może być używany do powiadamiania aplikacji o zakończeniu sesji u dostawcy OpenID.",
      "PERMISSIONCHECKV2": "Sprawdzanie uprawnień V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Jeśli flaga jest włączona, będziesz mógł korzystać z nowego API i jego funkcji.",
      "STATES": {
@@ -2632,8 +2632,8 @@
      "IDTOKENROLEASSERTION": "Role użytkownika w tokenie ID",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Jeśli zaznaczone, żądane role uwierzytelnionego użytkownika zostaną dodane do tokenu ID.",
      "IDTOKENUSERINFOASSERTION": "Informacje o użytkowniku w tokenie ID",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Umożliwia klientom pobieranie twierdzeń profilu, e-mail, telefonu i adresu z tokenu ID.",
-      "CLOCKSKEW": "Umożliwia klientom obsługę opóźnienia zegara OP i klienta. Czas trwania (0-5s) zostanie dodany do twierdzenia exp i odjęty od iats, auth_time i nbf.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Umożliwia aplikacjom pobieranie twierdzeń profilu, e-mail, telefonu i adresu z tokenu ID.",
+      "CLOCKSKEW": "Umożliwia aplikacjom obsługę opóźnienia zegara OP i aplikacji. Czas trwania (0-5s) zostanie dodany do twierdzenia exp i odjęty od iats, auth_time i nbf.",
      "RECOMMENDED": "zalecane",
      "NOTRECOMMENDED": "niezalecane",
      "SELECTION": {
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Chaves Web Ativas e Futuras",
          "DESCRIPTION": "Suas chaves web ativas e futuras. Ativar uma nova chave desativará a atual.",
-          "NOTE": "Nota: O endpoint JWKs OIDC retorna uma resposta que pode ser armazenada em cache (padrão: 5 min). Evite ativar uma chave muito cedo, pois ela pode ainda não estar disponível no cache e para os clientes.",
+          "NOTE": "Nota: O endpoint JWKs OIDC retorna uma resposta que pode ser armazenada em cache (padrão: 5 min). Evite ativar uma chave muito cedo, pois ela pode ainda não estar disponível no cache e para os aplicativos.",
          "ACTIVATE": "Ativar próxima Chave Web",
          "ACTIVE": "Atualmente ativa",
          "NEXT": "Próxima na fila",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "Tem permissão para criar e gerenciar usuários",
    "IAM_ADMIN_IMPERSONATOR": "Tem permissão para se passar por administradores e usuários finais de todas as organizações",
    "IAM_END_USER_IMPERSONATOR": "Tem permissão para se passar por usuários finais de todas as organizações",
-    "IAM_LOGIN_CLIENT": "Tem permissão para gerenciar clientes de login",
+    "IAM_LOGIN_CLIENT": "Tem permissão para gerenciar aplicativos de login",
    "ORG_OWNER": "Tem permissão sobre toda a organização",
    "ORG_USER_MANAGER": "Tem permissão para criar e gerenciar usuários da organização",
    "ORG_OWNER_VIEWER": "Tem permissão para revisar toda a organização",
@@ -1645,7 +1645,7 @@
      "DEBUGOIDCPARENTERROR": "Erro de Depuração do Pai OIDC",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Se a bandeira estiver ativada, o erro do pai OIDC será registrado no console.",
      "ENABLEBACKCHANNELLOGOUT": "Ativar Logout de Backchannel",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "O Logout de Back-Channel implementa o OpenID Connect Back-Channel Logout 1.0 e pode ser usado para notificar os clientes sobre a terminação da sessão no Provedor de OpenID.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "O Logout de Back-Channel implementa o OpenID Connect Back-Channel Logout 1.0 e pode ser usado para notificar os aplicativos sobre a terminação da sessão no Provedor de OpenID.",
      "PERMISSIONCHECKV2": "Verificação de Permissão V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Se a bandeira estiver ativada, você poderá usar a nova API e seus recursos.",
      "STATES": {
@@ -2628,8 +2628,8 @@
      "IDTOKENROLEASSERTION": "Funções do usuário no ID Token",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Se selecionado, as funções solicitadas do usuário autenticado serão adicionadas ao ID token.",
      "IDTOKENUSERINFOASSERTION": "Informações do usuário no ID Token",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Permite que os clientes obtenham claims de perfil, e-mail, telefone e endereço do ID token.",
-      "CLOCKSKEW": "Permite que os clientes lidem com a discrepância de tempo do OP e do cliente. A duração (0-5s) será adicionada ao claim exp e subtraída de iat, auth_time e nbf.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Permite que os aplicativos obtenham claims de perfil, e-mail, telefone e endereço do ID token.",
+      "CLOCKSKEW": "Permite que os aplicativos lidem com a discrepância de tempo do OP e do aplicativo. A duração (0-5s) será adicionada ao claim exp e subtraída de iat, auth_time e nbf.",
      "RECOMMENDED": "recomendado",
      "NOTRECOMMENDED": "não recomendado",
      "SELECTION": {
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Chei Web Active și Viitoare",
          "DESCRIPTION": "Cheile tale web active și viitoare. Activarea unei noi chei va dezactiva cheia curentă.",
-          "NOTE": "Notă: Endpoint-ul JWKs OIDC returnează un răspuns care poate fi stocat în cache (implicit 5 min). Evită activarea unei chei prea devreme, deoarece este posibil să nu fie încă disponibilă în cache și pentru clienți.",
+          "NOTE": "Notă: Endpoint-ul JWKs OIDC returnează un răspuns care poate fi stocat în cache (implicit 5 min). Evită activarea unei chei prea devreme, deoarece este posibil să nu fie încă disponibilă în cache și pentru aplicații.",
          "ACTIVATE": "Activează următoarea Cheie Web",
          "ACTIVE": "În prezent activă",
          "NEXT": "Următoarea în coadă",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "Are permisiunea de a crea și gestiona utilizatori",
    "IAM_ADMIN_IMPERSONATOR": "Are permisiunea de a impersona administratorul și utilizatorii finali din toate organizațiile",
    "IAM_END_USER_IMPERSONATOR": "Are permisiunea de a impersona utilizatorii finali din toate organizațiile",
-    "IAM_LOGIN_CLIENT": "Are permisiunea de a gestiona clientii de login",
+    "IAM_LOGIN_CLIENT": "Are permisiunea de a gestiona aplicațiile de login",
    "ORG_OWNER": "Are permisiunea asupra întregii organizații",
    "ORG_USER_MANAGER": "Are permisiunea de a crea și gestiona utilizatorii organizației",
    "ORG_OWNER_VIEWER": "Are permisiunea de a revizui întreaga organizație",
@@ -1642,7 +1642,7 @@
      "DEBUGOIDCPARENTERROR": "Eroare de Depanare Părinte OIDC",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Dacă steagul este activat, eroarea părinte OIDC va fi înregistrată în consolă.",
      "ENABLEBACKCHANNELLOGOUT": "Activează Logout Backchannel",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Logout-ul Back-Channel implementează OpenID Connect Back-Channel Logout 1.0 și poate fi folosit pentru a notifica clienții despre terminarea sesiunii la Producătorul OpenID.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Logout-ul Back-Channel implementează OpenID Connect Back-Channel Logout 1.0 și poate fi folosit pentru a notifica aplicațiile despre terminarea sesiunii la Producătorul OpenID.",
      "PERMISSIONCHECKV2": "Verificare Permisiuni V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Dacă steagul este activat, veți putea folosi noua API și funcțiile sale.",
      "STATES": {
@@ -2654,8 +2654,8 @@
      "IDTOKENROLEASSERTION": "Roluri utilizator în interiorul token-ului ID",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Dacă este selectat, rolurile solicitate ale utilizatorului autentificat sunt adăugate la token-ul ID.",
      "IDTOKENUSERINFOASSERTION": "Informații utilizator în interiorul token-ului ID",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Permite clienților să preia revendicări de profil, e-mail, telefon și adresă din token-ul ID.",
-      "CLOCKSKEW": "Permite clienților să gestioneze decalajul de ceas al OP și al clientului. Durata (0-5s) va fi adăugată revendicării exp și scăzută din iats, auth_time și nbf.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Permite aplicațiilor să preia revendicări de profil, e-mail, telefon și adresă din token-ul ID.",
+      "CLOCKSKEW": "Permite aplicațiilor să gestioneze decalajul de ceas al OP și al aplicației. Durata (0-5s) va fi adăugată revendicării exp și scăzută din iats, auth_time și nbf.",
      "RECOMMENDED": "recomandat",
      "NOTRECOMMENDED": "nerecomandat",
      "SELECTION": {
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Активные и будущие веб-ключи",
          "DESCRIPTION": "Ваши активные и будущие веб-ключи. Активация нового ключа приведёт к деактивации текущего.",
-          "NOTE": "Примечание: Конечная точка JWKs OIDC возвращает кэшируемый ответ (по умолчанию 5 минут). Избегайте слишком ранней активации ключа, так как он может ещё не быть доступен в кэше и у клиентов.",
+          "NOTE": "Примечание: Конечная точка JWKs OIDC возвращает кэшируемый ответ (по умолчанию 5 минут). Избегайте слишком ранней активации ключа, так как он может ещё не быть доступен в кэше и у приложений.",
          "ACTIVATE": "Активировать следующий веб-ключ",
          "ACTIVE": "В настоящее время активен",
          "NEXT": "Следующий в очереди",
@@ -403,6 +403,15 @@
        "description": "Обеспечьте пользователям доступ к вашему приложению и настройте их роль.",
        "action": "Предоставить пользователю"
      }
+    },
+    "MILESTONES": {
+      "APPLICATION_CREATED": {
+        "title": "Зарегистрируйте свое приложение",
+        "action": "Зарегистрировать приложение"
+      },
+      "AUTHENTICATION_SUCCEEDED_ON_APPLICATION": {
+        "title": "Войдите в свое приложение"
+      }
    }
  },
  "MENU": {
@@ -655,7 +664,7 @@
    "IAM_USER_MANAGER": "Имеет разрешение на создание и управление пользователями",
    "IAM_ADMIN_IMPERSONATOR": "Имеет разрешение выдавать себя за администратора и конечных пользователей из всех организаций",
    "IAM_END_USER_IMPERSONATOR": "Имеет разрешение выдавать себя за конечных пользователей из всех организаций",
-    "IAM_LOGIN_CLIENT": "Имеет разрешение на управление клиентами входа",
+    "IAM_LOGIN_CLIENT": "Имеет разрешение на управление приложениями входа",
    "ORG_OWNER": "Имеет разрешение на всю организацию",
    "ORG_USER_MANAGER": "Имеет разрешение на создание и управление пользователями организации",
    "ORG_OWNER_VIEWER": "Имеет разрешение на просмотр всей организации",
@@ -1696,7 +1705,7 @@
      "DEBUGOIDCPARENTERROR": "Отладка Ошибки Родителя OIDC",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Если флаг включен, ошибка родителя OIDC будет записана в консоль.",
      "ENABLEBACKCHANNELLOGOUT": "Включить Backchannel Logout",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Back-Channel Logout реализует OpenID Connect Back-Channel Logout 1.0 и может использоваться для уведомления клиентов о завершении сеанса у поставщика OpenID.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Back-Channel Logout реализует OpenID Connect Back-Channel Logout 1.0 и может использоваться для уведомления приложений о завершении сеанса у поставщика OpenID.",
      "PERMISSIONCHECKV2": "Проверка Разрешений V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Если флаг включен, вы сможете использовать новый API и его функции.",
      "STATES": {
@@ -2739,8 +2748,8 @@
      "IDTOKENROLEASSERTION": "Роли пользователей внутри ID Токена",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Если выбран данный параметр, запрошенные роли аутентифицированного пользователя добавляются в ID Токен.",
      "IDTOKENUSERINFOASSERTION": "Информация о пользователе внутри ID Токена",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Позволяет клиентам получить информацию о профиле, электронной почте, телефоне и адресах из ID Токена.",
-      "CLOCKSKEW": "Позволяет клиентам обрабатывать временные искажения OP и клиента. Длительность (0–5 с) будет добавлена к exp и вычтена из iats, auth_time и nbf.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Позволяет приложениям получить информацию о профиле, электронной почте, телефоне и адресах из ID Токена.",
+      "CLOCKSKEW": "Позволяет приложениям обрабатывать временные искажения OP и приложения. Длительность (0–5 с) будет добавлена к exp и вычтена из iats, auth_time и nbf.",
      "RECOMMENDED": "рекомендовано",
      "NOTRECOMMENDED": "не рекомендовано",
      "SELECTION": {
@@ -34,7 +34,7 @@
    },
    "PROJECTS": {
      "TITLE": "Projekt",
-      "DESCRIPTION": "Ett projekt är värd för en eller flera applikationer som du kan använda för att autentisera dina användare. Till exempel kan du ha ett enda projekt med 3 applikationer; en för din webbfrontend, en för din mobilapp och en för din backend. Du kan också auktorisera dina användare med projekt. För att tillåta användare från andra organisationer att logga in på dina applikationer, ge dem åtkomst till ditt projekt.<br/><br/>Om du inte kan hitta ett projekt, kontakta projektets ägare eller någon med motsvarande rättigheter för att få åtkomst.",
+      "DESCRIPTION": "Ett projekt är värd för en eller flera applikationer som du kan använda för att autentisera dina användare. Till exempel kan du ha ett enda projekt med 3 applikationer; en för din webbfrontend, en för din mobilapplikation, och en för din backend. Du kan också auktorisera dina användare med projekt. För att tillåta användare från andra organisationer att logga in på dina applikationer, ge dem åtkomst till ditt projekt.<br/><br/>Om du inte kan hitta ett projekt, kontakta projektets ägare eller någon med motsvarande rättigheter för att få åtkomst.",
      "OWNED": {
        "TITLE": "Ägda projekt",
        "DESCRIPTION": "Detta är de projekt du äger. Du kan hantera dessa projekts inställningar, behörigheter och applikationer."
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Aktiva och framtida webbnycklar",
          "DESCRIPTION": "Dina aktiva och kommande webbnycklar. Aktivering av en ny nyckel kommer att inaktivera den nuvarande.",
-          "NOTE": "Observera: JWKs OIDC-slutpunkten returnerar ett cachebart svar (standard 5 min). Undvik att aktivera en nyckel för tidigt, eftersom den kanske ännu inte är tillgänglig i cache och för klienter.",
+          "NOTE": "Observera: JWKs OIDC-slutpunkten returnerar ett cachebart svar (standard 5 min). Undvik att aktivera en nyckel för tidigt, eftersom den kanske ännu inte är tillgänglig i cache och för applikationer.",
          "ACTIVATE": "Aktivera nästa webbnyckel",
          "ACTIVE": "För närvarande aktiv",
          "NEXT": "Nästa i kön",
@@ -386,12 +386,12 @@
        "action": "Skapa projekt"
      },
      "APPLICATION_CREATED": {
-        "title": "Registrera din app",
+        "title": "Registrera din applikation",
        "description": "Registrera din webb-, native-, API- eller SAML-applikation och ställ in ett autentiseringsflöde.",
-        "action": "Registrera app"
+        "action": "Registrera applikation"
      },
      "AUTHENTICATION_SUCCEEDED_ON_APPLICATION": {
-        "title": "Logga in på din app",
+        "title": "Logga in på din applikation",
        "description": "Integrera din applikation med Zitadel för autentisering och testa det genom att logga in med din administratörsanvändare.",
        "action": "Logga in"
      },
@@ -453,7 +453,7 @@
    "DEVMODEWARN": "Utvecklingsläge är aktiverat som standard. Du kan uppdatera värden för produktion senare.",
    "GUIDE": "Guide",
    "BROWSEEXAMPLES": "Bläddra bland Exempel och SDKs",
-    "DUPLICATEAPPRENAME": "En app med samma namn finns redan. Vänligen välj ett annat namn.",
+    "DUPLICATEAPPRENAME": "En applikation med samma namn finns redan. Vänligen välj ett annat namn.",
    "DIALOG": {
      "CHANGE": {
        "TITLE": "Byt Ramverk",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "Har behörighet att skapa och hantera användare",
    "IAM_ADMIN_IMPERSONATOR": "Har behörighet att imitera administratörer och slutanvändare från alla organisationer",
    "IAM_END_USER_IMPERSONATOR": "Har behörighet att imitera slutanvändare från alla organisationer",
-    "IAM_LOGIN_CLIENT": "Har behörighet att hantera inloggningsklienter",
+    "IAM_LOGIN_CLIENT": "Har behörighet att hantera inloggningsapplikationer",
    "ORG_OWNER": "Har behörighet över hela organisationen",
    "ORG_USER_MANAGER": "Har behörighet att skapa och hantera användare i organisationen",
    "ORG_OWNER_VIEWER": "Har behörighet att granska hela organisationen",
@@ -884,9 +884,9 @@
      "DESCRIPTION": "Lägg till en andra faktor för att säkerställa optimal säkerhet för ditt konto.",
      "MANAGE_DESCRIPTION": "Hantera användarnas andra faktormetoder.",
      "ADD": "Lägg till faktor",
-      "OTP": "Autentiseringsapp för TOTP (Tidsbaserat engångslösenord)",
+      "OTP": "Autentiseringsapplikation för TOTP (Tidsbaserat engångslösenord)",
      "OTP_DIALOG_TITLE": "Lägg till OTP",
-      "OTP_DIALOG_DESCRIPTION": "Skanna QR-koden med en autentiseringsapp och ange koden nedan för att verifiera och aktivera OTP-metoden.",
+      "OTP_DIALOG_DESCRIPTION": "Skanna QR-koden med en autentiseringsapplikation och ange koden nedan för att verifiera och aktivera OTP-metoden.",
      "U2F": "Passkey",
      "U2F_DIALOG_TITLE": "Verifiera faktor",
      "U2F_DIALOG_DESCRIPTION": "Ange ett namn för din använda universella tvåfaktor.",
@@ -1615,7 +1615,7 @@
        "3": "Telefonverifiering",
        "4": "Återställning av lösenord",
        "5": "Passkey-initiering",
-        "6": "App-hemlighet",
+        "6": "Applikations-hemlighet",
        "7": "Engångslösenord (OTP) - SMS",
        "8": "Engångslösenord (OTP) - E-post"
      },
@@ -1648,7 +1648,7 @@
      "DEBUGOIDCPARENTERROR": "Debugga OIDC Föräldrafel",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Om flaggan är aktiverad kommer OIDC-föräldrafel att loggas i konsolen.",
      "ENABLEBACKCHANNELLOGOUT": "Aktivera Backchannel Logout",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Back-Channel Logout implementerar OpenID Connect Back-Channel Logout 1.0 och kan användas för att meddela klienter om sessionens avslutning hos OpenID-leverantören.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Back-Channel Logout implementerar OpenID Connect Back-Channel Logout 1.0 och kan användas för att meddela applikationer om sessionens avslutning hos OpenID-leverantören.",
      "PERMISSIONCHECKV2": "Behörighetskontroll V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Om flaggan är aktiverad kan du använda den nya API:n och dess funktioner.",
      "STATES": {
@@ -2433,7 +2433,7 @@
    },
    "SECONDFACTORTYPES": {
      "0": "Okänd",
-      "1": "Engångslösenord via autentiseringsapp (TOTP)",
+      "1": "Engångslösenord via autentiseringsapplikation (TOTP)",
      "2": "Passkey",
      "3": "Engångslösenord via e-post (E-post OTP)",
      "4": "Engångslösenord via SMS (SMS OTP)",
@@ -2661,8 +2661,8 @@
      "IDTOKENROLEASSERTION": "Användarroller i ID-token",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Om valt, läggs de begärda rollerna för den autentiserade användaren till ID-token.",
      "IDTOKENUSERINFOASSERTION": "Användarinformation i ID-token",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Möjliggör för klienter att hämta profil, e-post, telefon och adressanspråk från ID-token.",
-      "CLOCKSKEW": "Möjliggör för klienter att hantera klockförskjutning av OP och klient. Varaktigheten (0-5s) kommer att läggas till exp-anspråket och dras av från iats, auth_time och nbf.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Möjliggör för applikationer att hämta profil, e-post, telefon och adressanspråk från ID-token.",
+      "CLOCKSKEW": "Möjliggör för applikationer att hantera klockförskjutning av OP och applikation. Varaktigheten (0-5s) kommer att läggas till exp-anspråket och dras av från iats, auth_time och nbf.",
      "RECOMMENDED": "rekommenderad",
      "NOTRECOMMENDED": "inte rekommenderad",
      "SELECTION": {
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Aktif ve Gelecek Web Anahtarları",
          "DESCRIPTION": "Aktif ve yaklaşan web anahtarlarınız. Yeni bir anahtar etkinleştirmek mevcut olanı devre dışı bırakacaktır.",
-          "NOTE": "Not: JWKs OIDC endpoint önbelleğe alınabilir bir yanıt döndürür (varsayılan 5 dk). Henüz önbelleklerde ve istemcilerde mevcut olmayabileceği için bir anahtarı çok erken etkinleştirmekten kaçının.",
+          "NOTE": "Not: JWKs OIDC endpoint önbelleğe alınabilir bir yanıt döndürür (varsayılan 5 dk). Henüz önbelleklerde ve uygulamalarda mevcut olmayabileceği için bir anahtarı çok erken etkinleştirmekten kaçının.",
          "ACTIVATE": "Sonraki Web Anahtarını Etkinleştir",
          "ACTIVE": "Şu anda aktif",
          "NEXT": "Sırada",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "Kullanıcıları oluşturma ve yönetme iznine sahiptir",
    "IAM_ADMIN_IMPERSONATOR": "Tüm organizasyonlardan admin ve son kullanıcıların kimliğine bürünme iznine sahiptir",
    "IAM_END_USER_IMPERSONATOR": "Tüm organizasyonlardan son kullanıcıların kimliğine bürünme iznine sahiptir",
-    "IAM_LOGIN_CLIENT": "Giriş istemcilerini yönetme iznine sahiptir",
+    "IAM_LOGIN_CLIENT": "Giriş uygulamalarını yönetme iznine sahiptir",
    "ORG_OWNER": "Tüm organizasyon üzerinde izne sahiptir",
    "ORG_USER_MANAGER": "Organizasyonun kullanıcılarını oluşturma ve yönetme iznine sahiptir",
    "ORG_OWNER_VIEWER": "Tüm organizasyonu gözden geçirme iznine sahiptir",
@@ -1647,7 +1647,7 @@
      "DEBUGOIDCPARENTERROR": "OIDC Üst Hatayı Hata Ayıkla",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Bayrak etkinleştirilirse, OIDC üst hatası konsolda günlüğe kaydedilecektir.",
      "ENABLEBACKCHANNELLOGOUT": "Arka Kanal Çıkışını Etkinleştir",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Arka Kanal Çıkışı OpenID Connect Arka Kanal Çıkışı 1.0'ı uygular ve OpenID Sağlayıcısında oturum sonlandırma hakkında istemcileri bilgilendirmek için kullanılabilir.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Arka Kanal Çıkışı OpenID Connect Arka Kanal Çıkışı 1.0'ı uygular ve OpenID Sağlayıcısında oturum sonlandırma hakkında uygulamaları bilgilendirmek için kullanılabilir.",
      "PERMISSIONCHECKV2": "İzin Kontrolü V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Bayrak etkinleştirilirse, yeni API'yi ve özelliklerini kullanabileceksiniz.",
      "STATES": {
@@ -2661,8 +2661,8 @@
      "IDTOKENROLEASSERTION": "ID Token içinde kullanıcı rolleri",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Seçilirse, kimliği doğrulanmış kullanıcının istenen rolleri ID token'a eklenir.",
      "IDTOKENUSERINFOASSERTION": "ID Token içinde Kullanıcı Bilgisi",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "İstemcilerin ID token'dan profil, e-posta, telefon ve adres bilgilerini almasını sağlar.",
-      "CLOCKSKEW": "İstemcilerin OP ve istemci saat farklılığını ele almasını sağlar. Süre (0-5s) exp claim'ine eklenecek ve iats, auth_time ve nbf'den çıkarılacaktır.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Uygulamaların ID token'dan profil, e-posta, telefon ve adres bilgilerini almasını sağlar.",
+      "CLOCKSKEW": "Uygulamaların OP ve uygulama saat farklılığını ele almasını sağlar. Süre (0-5s) exp claim'ine eklenecek ve iats, auth_time ve nbf'den çıkarılacaktır.",
      "RECOMMENDED": "önerilen",
      "NOTRECOMMENDED": "önerilmeyen",
      "SELECTION": {
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "Активні та майбутні веб-ключі",
          "DESCRIPTION": "Ваші активні та майбутні веб-ключі. Активація нового ключа деактивує поточний.",
-          "NOTE": "Примітка: JWKs OIDC ендпоінт повертає кешовану відповідь (за замовчуванням 5 хв). Уникайте активації ключа занадто рано, оскільки він може бути ще недоступний для кешів та клієнтів.",
+          "NOTE": "Примітка: JWKs OIDC ендпоінт повертає кешовану відповідь (за замовчуванням 5 хв). Уникайте активації ключа занадто рано, оскільки він може бути ще недоступний для кешів та додатків.",
          "ACTIVATE": "Активувати наступний веб-ключ",
          "ACTIVE": "Зараз активний",
          "NEXT": "Наступний у черзі",
@@ -657,7 +657,7 @@
    "IAM_USER_MANAGER": "Має дозвіл створювати та керувати користувачами",
    "IAM_ADMIN_IMPERSONATOR": "Має дозвіл виконувати персоніфікацію адміністраторів та кінцевих користувачів з усіх організацій",
    "IAM_END_USER_IMPERSONATOR": "Має дозвіл виконувати персоніфікацію кінцевих користувачів з усіх організацій",
-    "IAM_LOGIN_CLIENT": "Має дозвіл керувати клієнтами входу",
+    "IAM_LOGIN_CLIENT": "Має дозвіл керувати додатками входу",
    "ORG_OWNER": "Має дозвіл на всю організацію",
    "ORG_USER_MANAGER": "Має дозвіл створювати та керувати користувачами організації",
    "ORG_OWNER_VIEWER": "Має дозвіл переглядати всю організацію",
@@ -1648,7 +1648,7 @@
      "DEBUGOIDCPARENTERROR": "Налагодження батьківської помилки OIDC",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "Якщо прапорець увімкнено, батьківська помилка OIDC буде записана в консоль.",
      "ENABLEBACKCHANNELLOGOUT": "Увімкнути вихід через зворотний канал",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Вихід через зворотний канал реалізує OpenID Connect Back-Channel Logout 1.0 і може використовуватися для сповіщення клієнтів про завершення сесії у провайдера OpenID.",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Вихід через зворотний канал реалізує OpenID Connect Back-Channel Logout 1.0 і може використовуватися для сповіщення додатків про завершення сесії у провайдера OpenID.",
      "PERMISSIONCHECKV2": "Перевірка дозволів V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "Якщо прапорець увімкнено, ви зможете використовувати новий API та його можливості.",
      "STATES": {
@@ -2664,8 +2664,8 @@
      "IDTOKENROLEASSERTION": "Ролі користувача в ID токені",
      "IDTOKENROLEASSERTION_DESCRIPTION": "Якщо обрано, запитані ролі автентифікованого користувача додаються до ID токена.",
      "IDTOKENUSERINFOASSERTION": "Інформація користувача в ID токені",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Дозволяє клієнтам отримувати profile, email, phone та address claims з ID токена.",
-      "CLOCKSKEW": "Дозволяє клієнтам обробляти розбіжність годинника OP та клієнта. Тривалість (0-5с) буде додана до exp claim і віднята від iats, auth_time та nbf.",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "Дозволяє додаткам отримувати profile, email, phone та address claims з ID токена.",
+      "CLOCKSKEW": "Дозволяє додаткам обробляти розбіжність годинника OP та додатка. Тривалість (0-5с) буде додана до exp claim і віднята від iats, auth_time та nbf.",
      "RECOMMENDED": "рекомендовано",
      "NOTRECOMMENDED": "не рекомендовано",
      "SELECTION": {
@@ -191,7 +191,7 @@
        "TABLE": {
          "TITLE": "活动和未来的 Web 密钥",
          "DESCRIPTION": "您的当前活动和即将启用的 Web 密钥。激活新密钥将会停用当前密钥。",
-          "NOTE": "注意：JWKs OIDC 端点返回可缓存的响应（默认 5 分钟）。请避免过早激活密钥，否则它可能尚未在缓存或客户端中可用。",
+          "NOTE": "注意：JWKs OIDC 端点返回可缓存的响应（默认 5 分钟）。请避免过早激活密钥，否则它可能尚未在缓存或应用中可用。",
          "ACTIVATE": "激活下一个 Web 密钥",
          "ACTIVE": "当前活动",
          "NEXT": "队列中的下一个",
@@ -453,7 +453,7 @@
    "DEVMODEWARN": "默认情况下启用开发模式。您可以稍后更新生产值。",
    "GUIDE": "指南",
    "BROWSEEXAMPLES": "浏览示例",
-    "DUPLICATEAPPRENAME": "具有相同 neme 的应用程序已经存在。请选择不同的名称。",
+    "DUPLICATEAPPRENAME": "具有相同名称的应用程序已经存在。请选择不同的名称。",
    "DIALOG": {
      "CHANGE": {
        "TITLE": "变革框架",
@@ -656,7 +656,7 @@
    "IAM_USER_MANAGER": "有权创建和管理用户",
    "IAM_ADMIN_IMPERSONATOR": "有权模拟所有组织的管理员和最终用户",
    "IAM_END_USER_IMPERSONATOR": "有权模拟所有组织的最终用户",
-    "IAM_LOGIN_CLIENT": "具有管理登录客户端的权限",
+    "IAM_LOGIN_CLIENT": "具有管理登录应用程序的权限",
    "ORG_OWNER": "拥有整个组织的权限",
    "ORG_USER_MANAGER": "有权创建和管理组织的用户",
    "ORG_OWNER_VIEWER": "有权审查整个组织",
@@ -1614,7 +1614,7 @@
        "3": "电话号码验证",
        "4": "重置密码",
        "5": "Passkey 初始化",
-        "6": "App 验证",
+        "6": "应用密钥",
        "7": "一次性密码 (OTP) - SMS",
        "8": "一次性密码 (OTP) - 电子邮件"
      },
@@ -1647,7 +1647,7 @@
      "DEBUGOIDCPARENTERROR": "调试 OIDC 父错误",
      "DEBUGOIDCPARENTERROR_DESCRIPTION": "如果启用该标志，OIDC 父错误将记录在控制台中。",
      "ENABLEBACKCHANNELLOGOUT": "启用 Backchannel 注销",
-      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Back-Channel 注销实现了 OpenID Connect Back-Channel Logout 1.0，可用于通知客户端在 OpenID 提供商处终止会话。",
+      "ENABLEBACKCHANNELLOGOUT_DESCRIPTION": "Back-Channel 注销实现了 OpenID Connect Back-Channel Logout 1.0，可用于通知应用程序在 OpenID 提供商处终止会话。",
      "PERMISSIONCHECKV2": "权限检查 V2",
      "PERMISSIONCHECKV2_DESCRIPTION": "如果启用该标志，您将能够使用新的 API 及其功能。",
      "STATES": {
@@ -2665,8 +2665,8 @@
      "IDTOKENROLEASSERTION": "在 ID Token 中包含用户角色",
      "IDTOKENROLEASSERTION_DESCRIPTION": "如果勾选，则已验证用户的请求角色将添加到 ID Token 中。",
      "IDTOKENUSERINFOASSERTION": "在 ID Token 中包含用户信息",
-      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "使客户端能够从 ID Token 中读取个人资料、电子邮件、电话和地址声明。",
-      "CLOCKSKEW": "使客户端能够处理 OP 和客户端的时钟偏差。持续时间（0-5 秒）将添加到 exp 声明中，并从 iats、auth_time 和 nbf 中减去。",
+      "IDTOKENUSERINFOASSERTION_DESCRIPTION": "使应用程序能够从 ID Token 中读取个人资料、电子邮件、电话和地址声明。",
+      "CLOCKSKEW": "使应用程序能够处理 OP 和应用程序的时钟偏差。持续时间（0-5 秒）将添加到 exp 声明中，并从 iats、auth_time 和 nbf 中减去。",
      "RECOMMENDED": "推荐的",
      "NOTRECOMMENDED": "不推荐的",
      "SELECTION": {
@@ -257,14 +257,14 @@ func TestServer_VerifyClient(t *testing.T) {
 			wantErr: true,
 		},
 		{
-			name: "native client success",
+			name: "native application success",
 			client: clientDetails{
 				authReqClientID: nativeClient.GetClientId(),
 				clientID:        nativeClient.GetClientId(),
 			},
 		},
 		{
-			name: "web client basic secret empty error",
+			name: "web application basic secret empty error",
 			client: clientDetails{
 				authReqClientID: basicWebClient.GetClientId(),
 				clientID:        basicWebClient.GetClientId(),
@@ -273,7 +273,7 @@ func TestServer_VerifyClient(t *testing.T) {
 			wantErr: true,
 		},
 		{
-			name: "web client basic secret invalid error",
+			name: "web application basic secret invalid error",
 			client: clientDetails{
 				authReqClientID: basicWebClient.GetClientId(),
 				clientID:        basicWebClient.GetClientId(),
@@ -282,7 +282,7 @@ func TestServer_VerifyClient(t *testing.T) {
 			wantErr: true,
 		},
 		{
-			name: "web client basic secret success",
+			name: "web application basic secret success",
 			client: clientDetails{
 				authReqClientID: basicWebClient.GetClientId(),
 				clientID:        basicWebClient.GetClientId(),
@@ -290,7 +290,7 @@ func TestServer_VerifyClient(t *testing.T) {
 			},
 		},
 		{
-			name: "web client JWT profile empty assertion error",
+			name: "web application JWT profile empty assertion error",
 			client: clientDetails{
 				authReqClientID: jwtWebClient.GetClientId(),
 				clientID:        jwtWebClient.GetClientId(),
@@ -298,7 +298,7 @@ func TestServer_VerifyClient(t *testing.T) {
 			wantErr: true,
 		},
 		{
-			name: "web client JWT profile invalid assertion error",
+			name: "web application JWT profile invalid assertion error",
 			client: clientDetails{
 				authReqClientID: jwtWebClient.GetClientId(),
 				clientID:        jwtWebClient.GetClientId(),
@@ -307,7 +307,7 @@ func TestServer_VerifyClient(t *testing.T) {
 			wantErr: true,
 		},
 		{
-			name: "web client JWT profile success",
+			name: "web application JWT profile success",
 			client: clientDetails{
 				authReqClientID: jwtWebClient.GetClientId(),
 				clientID:        jwtWebClient.GetClientId(),
@@ -44,7 +44,7 @@ func (s *ServiceProvider) LoginURL(id string) string {
 	if s.SP.LoginBaseURI == nil || s.SP.LoginBaseURI.String() == "" {
 		return s.defaultLoginURLV2 + id
 	}
-	// for clients with a specific URI (internal or external) we only need to add the auth request id
+	// for applications with a specific URI (internal or external) we only need to add the auth request id
 	uri := s.SP.LoginBaseURI.JoinPath(LoginPath)
 	q := uri.Query()
 	q.Set(LoginSamlRequestParam, id)
@@ -1087,7 +1087,7 @@ service AdminService {
        option (grpc.gateway.protoc_gen_openapiv2.options.openapiv2_operation) = {
            tags: "Settings";
            summary: "Add OIDC Settings";
-            description: "Create new OIDC settings. The OIDC Settings define the lifetimes of the different tokens in OIDC. These settings are used for all organizations and clients."
+            description: "Create new OIDC settings. The OIDC Settings define the lifetimes of the different tokens in OIDC. These settings are used for all organizations and applications."
        };
    }

@@ -1104,7 +1104,7 @@ service AdminService {
        option (grpc.gateway.protoc_gen_openapiv2.options.openapiv2_operation) = {
            tags: "Settings";
            summary: "Add OIDC Settings";
-            description: "Update existing OIDC settings. The OIDC Settings define the lifetimes of the different tokens in OIDC. These settings are used for all organizations and clients."
+            description: "Update existing OIDC settings. The OIDC Settings define the lifetimes of the different tokens in OIDC. These settings are used for all organizations and applications."
        };
    }

@@ -32,7 +32,7 @@ option (grpc.gateway.protoc_gen_openapiv2.options.openapiv2_swagger) = {
    info: {
        title: "Management API";
        version: "1.0";
-        description: "The management API is as the name states the interface where systems can mutate IAM objects like organizations, projects, clients, users and so on if they have the necessary access rights.";
+        description: "The management API is as the name states the interface where systems can mutate IAM objects like organizations, projects, applications, users and so on if they have the necessary access rights.";
        contact:{
            name: "ZITADEL"
            url: "https://zitadel.com"
@@ -49,7 +49,7 @@ option (grpc.gateway.protoc_gen_openapiv2.options.openapiv2_swagger) = {
        },
        {
            name: "Applications",
-            description: "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. All applications share the roles and authorizations of their project."
+            description: "Applications are the entry point to your project. 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."
        },
        {
            name: "Authentication Methods"
@@ -13,7 +13,7 @@ describe('instance secret generators', () => {
      cy.contains('Phone verification');
      cy.contains('Password Reset');
      cy.contains('Passkey Initialization');
-      cy.contains('App Secret');
+      cy.contains('Application Secret');
      cy.contains('One Time Password (OTP) - SMS');
      cy.contains('One Time Password (OTP) - Email');
    });