ci: bump actions/create-github-app-token from 3.1.1 to 3.2.0

Bumps [actions/create-github-app-token](https://github.com/actions/create-github-app-token) from 3.1.1 to 3.2.0.
- [Release notes](https://github.com/actions/create-github-app-token/releases)
- [Changelog](https://github.com/actions/create-github-app-token/blob/main/CHANGELOG.md)
- [Commits](1b10c78c78...bcd2ba4921)

---
updated-dependencies:
- dependency-name: actions/create-github-app-token
  dependency-version: 3.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

.github/workflows/gen-image-compress.yml

@@ -29,7 +29,7 @@ jobs:
        github.event.pull_request.head.repo.full_name == github.repository)
     steps:
       - id: generate_token
-        uses: actions/create-github-app-token@1b10c78c7865c340bc4f6099eb2f838309f1e8c3 # v2
+        uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v2
         with:
           app-id: ${{ secrets.GH_APP_ID }}
           private-key: ${{ secrets.GH_APP_PRIV_KEY }}

.github/workflows/gen-update-webauthn-mds.yml

@@ -16,7 +16,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - id: generate_token
-        uses: actions/create-github-app-token@1b10c78c7865c340bc4f6099eb2f838309f1e8c3 # v2
+        uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v2
         with:
           app-id: ${{ secrets.GH_APP_ID }}
           private-key: ${{ secrets.GH_APP_PRIV_KEY }}

.github/workflows/gh-cherry-pick.yml

@@ -10,7 +10,7 @@ jobs:
     steps:
       - id: app-token
         name: Generate app token
-        uses: actions/create-github-app-token@1b10c78c7865c340bc4f6099eb2f838309f1e8c3 # v2
+        uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v2
         if: ${{ env.GH_APP_ID != '' }}
         with:
           app-id: ${{ secrets.GH_APP_ID }}

.github/workflows/gh-ghcr-retention.yml

@@ -16,7 +16,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - id: generate_token
-        uses: actions/create-github-app-token@1b10c78c7865c340bc4f6099eb2f838309f1e8c3 # v2
+        uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v2
         with:
           app-id: ${{ secrets.GH_APP_ID }}
           private-key: ${{ secrets.GH_APP_PRIV_KEY }}

.github/workflows/release-branch-off.yml

@@ -29,7 +29,7 @@ jobs:
     steps:
       - id: app-token
         name: Generate app token
-        uses: actions/create-github-app-token@1b10c78c7865c340bc4f6099eb2f838309f1e8c3 # v2
+        uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v2
         with:
           app-id: ${{ secrets.GH_APP_ID }}
           private-key: ${{ secrets.GH_APP_PRIV_KEY }}
@@ -57,7 +57,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - id: generate_token
-        uses: actions/create-github-app-token@1b10c78c7865c340bc4f6099eb2f838309f1e8c3 # v2
+        uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v2
         with:
           app-id: ${{ secrets.GH_APP_ID }}
           private-key: ${{ secrets.GH_APP_PRIV_KEY }}

.github/workflows/release-tag.yml

@@ -67,7 +67,7 @@ jobs:
     steps:
       - id: app-token
         name: Generate app token
-        uses: actions/create-github-app-token@1b10c78c7865c340bc4f6099eb2f838309f1e8c3 # v2
+        uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v2
         with:
           app-id: ${{ secrets.GH_APP_ID }}
           private-key: ${{ secrets.GH_APP_PRIV_KEY }}
@@ -119,7 +119,7 @@ jobs:
     steps:
       - id: app-token
         name: Generate app token
-        uses: actions/create-github-app-token@1b10c78c7865c340bc4f6099eb2f838309f1e8c3 # v2
+        uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v2
         with:
           app-id: ${{ secrets.GH_APP_ID }}
           private-key: ${{ secrets.GH_APP_PRIV_KEY }}
@@ -161,7 +161,7 @@ jobs:
     steps:
       - id: app-token
         name: Generate app token
-        uses: actions/create-github-app-token@1b10c78c7865c340bc4f6099eb2f838309f1e8c3 # v2
+        uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v2
         with:
           app-id: ${{ secrets.GH_APP_ID }}
           private-key: ${{ secrets.GH_APP_PRIV_KEY }}

.github/workflows/repo-stale.yml

@@ -15,7 +15,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - id: generate_token
-        uses: actions/create-github-app-token@1b10c78c7865c340bc4f6099eb2f838309f1e8c3 # v2
+        uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v2
         with:
           app-id: ${{ secrets.GH_APP_ID }}
           private-key: ${{ secrets.GH_APP_PRIV_KEY }}

.github/workflows/translation-extract-compile.yml

@@ -21,7 +21,7 @@ jobs:
     steps:
       - id: generate_token
         if: ${{ github.event_name != 'pull_request' }}
-        uses: actions/create-github-app-token@1b10c78c7865c340bc4f6099eb2f838309f1e8c3 # v2
+        uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v2
         with:
           app-id: ${{ secrets.GH_APP_ID }}
           private-key: ${{ secrets.GH_APP_PRIV_KEY }}

web/src/admin/applications/ApplicationForm.ts

@@ -129,7 +129,7 @@ export class ApplicationForm extends WithCapabilitiesConfig(ModelForm<Applicatio
                 label=${msg("Application Name")}
                 spellcheck="false"
                 required
-                help=${msg("The name displayed in the application library.")}
+                help=${msg("The name displayed in the Application Dashboard.")}
             ></ak-text-input>
             <ak-slug-input
                 name="slug"
@@ -197,16 +197,16 @@ export class ApplicationForm extends WithCapabilitiesConfig(ModelForm<Applicatio
                         ?checked=${this.instance?.openInNewTab ?? false}
                         label=${msg("Open in new tab")}
                         help=${msg(
-                            "If checked, the launch URL will open in a new browser tab or window from the user's application library.",
+                            "If checked, the launch URL will open in a new browser tab or window from the user's Application Dashboard.",
                         )}
                     >
                     </ak-switch-input>
                     <ak-switch-input
                         name="metaHide"
                         ?checked=${this.instance?.metaHide ?? false}
-                        label=${msg("Hide from My applications")}
+                        label=${msg("Hide from Application Dashboard")}
                         help=${msg(
-                            "If checked, this application will not be shown on the user's My applications page.",
+                            "If checked, this application will not be shown on the user's Application Dashboard.",
                         )}
                     >
                     </ak-switch-input>
@@ -225,7 +225,7 @@ export class ApplicationForm extends WithCapabilitiesConfig(ModelForm<Applicatio
                         name="metaPublisher"
                         value="${ifDefined(this.instance?.metaPublisher)}"
                         placeholder=${msg("Type an optional publisher name...")}
-                        help=${msg("The publisher is shown in the application library.")}
+                        help=${msg("The publisher is shown in the Application Dashboard.")}
                     ></ak-text-input>
                     <ak-textarea-input
                         label=${msg("Description")}
@@ -233,7 +233,7 @@ export class ApplicationForm extends WithCapabilitiesConfig(ModelForm<Applicatio
                         placeholder=${msg("Type an optional description...")}
                         value=${ifDefined(this.instance?.metaDescription)}
                         help=${msg(
-                            "The description is shown in the application library and may provide additional information about the application to end users.",
+                            "The description is shown in the Application Dashboard and may provide additional information about the application to end users.",
                         )}
                     ></ak-textarea-input>
                 </div>

web/src/admin/applications/wizard/steps/ak-application-wizard-application-step.ts

@@ -131,7 +131,7 @@ export class ApplicationWizardApplicationStep extends ApplicationWizardStep {
                     spellcheck="false"
                     required
                     .errorMessages=${errors.name ?? this.errorMessages("name")}
-                    help=${msg("The name displayed in the application library.")}
+                    help=${msg("The name displayed in the Application Dashboard.")}
                 ></ak-text-input>
                 <ak-slug-input
                     name="slug"
@@ -183,16 +183,16 @@ export class ApplicationWizardApplicationStep extends ApplicationWizardStep {
                             ?checked=${app.openInNewTab ?? false}
                             label=${msg("Open in new tab")}
                             help=${msg(
-                                "If checked, the launch URL will open in a new browser tab or window from the user's application library.",
+                                "If checked, the launch URL will open in a new browser tab or window from the user's Application Dashboard.",
                             )}
                         >
                         </ak-switch-input>
                         <ak-switch-input
                             name="metaHide"
                             ?checked=${app.metaHide ?? false}
-                            label=${msg("Hide from My applications")}
+                            label=${msg("Hide from Application Dashboard")}
                             help=${msg(
-                                "If checked, this application will not be shown on the user's My applications page.",
+                                "If checked, this application will not be shown on the user's Application Dashboard.",
                             )}
                         >
                         </ak-switch-input>
@@ -211,7 +211,7 @@ export class ApplicationWizardApplicationStep extends ApplicationWizardStep {
                             name="metaPublisher"
                             value="${ifDefined(app.metaPublisher)}"
                             .errorMessages=${errors.metaPublisher}
-                            help=${msg("The publisher is shown in the application library.")}
+                            help=${msg("The publisher is shown in the Application Dashboard.")}
                         ></ak-text-input>
                         <ak-textarea-input
                             label=${msg("Description")}
@@ -219,7 +219,7 @@ export class ApplicationWizardApplicationStep extends ApplicationWizardStep {
                             value=${ifDefined(app.metaDescription)}
                             .errorMessages=${errors.metaDescription}
                             help=${msg(
-                                "The description is shown in the application library and may provide additional information about the application to end users.",
+                                "The description is shown in the Application Dashboard and may provide additional information about the application to end users.",
                             )}
                         ></ak-textarea-input>
                     </div>

web/src/elements/stories/AppIcon.stories.ts

@@ -21,7 +21,7 @@ const metadata: Meta<AppIcon> = {
                 component: /* md */ `
 # Application Icon
 
-AppIcon displays an icon associated with an authentik application on the User Library page. It takes
+AppIcon displays an icon associated with an authentik application on the Application Dashboard page. It takes
 an API "Application" object and a size, with a default size of "medium."
 
 ## Usage

web/src/user/LibraryPage/ak-library-impl.ts

@@ -178,7 +178,7 @@ export class LibraryPage extends WithSession(AKElement) {
         threshold: 0.3,
     });
 
-    public pageTitle = msg("My Applications");
+    public pageTitle = msg("Application Dashboard");
 
     //#region Lifecycle
 
@@ -432,7 +432,7 @@ export class LibraryPage extends WithSession(AKElement) {
     protected override render() {
         return html`<div class="pf-c-page__main">
             <div class="pf-c-page__header pf-c-content">
-                <h1 class="pf-c-page__title">${msg("My applications")}</h1>
+                <h1 class="pf-c-page__title">${msg("Application Dashboard")}</h1>
                 ${this.searchEnabled ? this.renderSearch() : nothing}
             </div>
             <main

web/src/user/LibraryPage/ak-library.ts

@@ -93,7 +93,7 @@ export class LibraryPage extends AKElement {
         );
     }
 
-    public pageTitle = msg("My Applications");
+    public pageTitle = msg("Application Dashboard");
 
     render() {
         if (this.apps.loading) {

website/docs/add-secure-apps/applications/index.md

@@ -2,7 +2,7 @@
 title: Applications
 ---
 
-Applications, as defined in authentik, are used to configure and separate the authorization/access control and the appearance of a specific software application in the **My applications** page.
+Applications, as defined in authentik, are used to configure and separate the authorization/access control and the appearance of a specific software application in the **Application Dashboard** page.
 
 When a user logs into authentik, they see a list of the applications for which authentik is configured to provide authentication and authorization (the applications that they are authorized to use).
 
@@ -30,7 +30,7 @@ The following options can be configured:
 
     For a reference of all fields available, see [the API schema for the User object](https://api.goauthentik.io/reference/core-users-retrieve/).
 
-    Only apps with launch URLs that begin with `http://` or `https://`, or that use relative paths, appear on the user's **My applications** page. To keep an app accessible but remove it from that page, use the **Hide from My applications** option (see [Hide applications](./manage_apps.mdx#hide-applications)).
+    Only apps with launch URLs that begin with `http://` or `https://`, or that use relative paths, appear on the user's **Application Dashboard** page. To keep an app accessible but remove it from that page, use the **Hide from Application Dashboard** option (see [Hide applications](./manage_apps.mdx#hide-applications)).
 
 - _Icon (URL)_: Optionally configure an icon for the application. You can select from files uploaded to the [Files](../../customize/files.md) library or enter an absolute URL.
 

website/docs/add-secure-apps/applications/manage_apps.mdx

@@ -6,7 +6,7 @@ Managing the applications that your team uses involves several tasks, from initi
 
 ### Create an application and provider pair
 
-To add an application to authentik and have it display on users' **My applications** page, follow these steps:
+To add an application to authentik and have it display on users' **Application Dashboard** page, follow these steps:
 
 1. Log in to authentik as an administrator and open the authentik Admin interface.
 
@@ -27,7 +27,7 @@ By default, if you click **New Application**, you are prompted to create the new
 
     - **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and any additional required configurations.
 
-    - **Configure Bindings**: to manage which applications a user can view and access via their **My applications** page, you can optionally create a [binding](../bindings-overview/index.md) between the application and a specific policy, group, or user. Note that if you do not define any bindings, then all users have access to the application. For more information about user access, refer to our documentation about [policy-driven authorization](#policy-driven-authorization), [using application entitlements](../applications/manage_apps.mdx#create-an-application-entitlement) and [hiding an application](#hide-applications).
+    - **Configure Bindings**: to manage which applications a user can view and access via their **Application Dashboard** page, you can optionally create a [binding](../bindings-overview/index.md) between the application and a specific policy, group, or user. Note that if you do not define any bindings, then all users have access to the application. For more information about user access, refer to our documentation about [policy-driven authorization](#policy-driven-authorization), [using application entitlements](../applications/manage_apps.mdx#create-an-application-entitlement) and [hiding an application](#hide-applications).
 
 4. On the **Review and Submit Application** panel, review the configuration for the new application and its provider, and then click **Create Application**.
 
@@ -111,12 +111,12 @@ return {
 
 ## Hide applications
 
-To hide an application without modifying its policy settings or removing it, you can use the **Hide from My applications** option on the application. The application will no longer appear on the **My applications** page.
+To hide an application without modifying its policy settings or removing it, you can use the **Hide from Application Dashboard** option on the application. The application will no longer appear on the **Application Dashboard** page.
 
 Keep in mind that users still have access, so they can still authorize access when the login process is started from the application.
 
 :::info Hiding applications before 2026.5
-Before authentik 2026.5, an application was hidden by setting its **Launch URL** to `blank://blank`. Existing applications using that value are automatically migrated to using the **Hide from My applications** option upon upgrading.
+Before authentik 2026.5, an application was hidden by setting its **Launch URL** to `blank://blank`. Existing applications using that value are automatically migrated to using the **Hide from Application Dashboard** option upon upgrading.
 :::
 
 ## Launch URLs

website/docs/add-secure-apps/providers/rac/create-rac-provider.md

@@ -82,6 +82,6 @@ The RAC provider requires the deployment of an [RAC Outpost](../../outposts/inde
 
 ## Access the remote machine
 
-To verify your configuration and access the remote machine, go to the **User interface** of your authentik instance. On the **My applications** page, click the **Remote Access** application to start a secure session on the remote machine in your web browser.
+To verify your configuration and access the remote machine, go to the **User interface** of your authentik instance. On the **Application Dashboard** page, click the **Remote Access** application to start a secure session on the remote machine in your web browser.
 
 If you defined multiple endpoints, click the endpoint for the remote machine that you want to access.

website/docs/add-secure-apps/providers/rac/index.md

@@ -2,7 +2,7 @@
 title: Remote Access Control (RAC) Provider
 ---
 
-The RAC provider allows users to access remote Windows, macOS, and Linux machines via [RDP](https://en.wikipedia.org/wiki/Remote_Desktop_Protocol)/[SSH](https://en.wikipedia.org/wiki/Secure_Shell)/[VNC](https://en.wikipedia.org/wiki/Virtual_Network_Computing). Just like other providers in authentik, the RAC provider is associated with an application that appears on a user's **My applications** page.
+The RAC provider allows users to access remote Windows, macOS, and Linux machines via [RDP](https://en.wikipedia.org/wiki/Remote_Desktop_Protocol)/[SSH](https://en.wikipedia.org/wiki/Secure_Shell)/[VNC](https://en.wikipedia.org/wiki/Virtual_Network_Computing). Just like other providers in authentik, the RAC provider is associated with an application that appears on a user's **Application Dashboard** page.
 
 For instructions on creating a RAC provider, refer to the [Create a Remote Access Control (RAC) provider](./create-rac-provider.md) documentation. Alternatively, watch our ["Remote Access Control (RAC) in authentik" video on YouTube](https://www.youtube.com/watch?v=9wahIBRV6Ts).
 

website/docs/add-secure-apps/providers/rac/rac_credentials_prompt.md

@@ -91,4 +91,4 @@ Other options for the connection security type are: `any`, `nla`, `nla-ext`, `vm
 
 ## Configuration verification
 
-Log in to authentik with a user account that has the required privileges to access the RAC application. Open the User interface, and on the **My applications** page click the RAC application. You should then be redirected to the prompt stage and prompted for a username and password. Enter the credentials for the RAC endpoint and if the credentials are valid the RDP/SSH/VNC connection should be established.
+Log in to authentik with a user account that has the required privileges to access the RAC application. Open the User interface, and on the **Application Dashboard** page click the RAC application. You should then be redirected to the prompt stage and prompted for a username and password. Enter the credentials for the RAC endpoint and if the credentials are valid the RDP/SSH/VNC connection should be established.

website/docs/core/glossary/terms/application.mdx

@@ -4,7 +4,7 @@ sidebar_custom_props:
     termName: Application
     tags:
         - Core Concepts
-    shortDescription: An application is what you authenticate into with authentik and is displayed on the "My applications" page in the User interface.
+    shortDescription: An application is what you authenticate into with authentik and is displayed on the "Application Dashboard" page in the User interface.
     authentikSpecific: true
     longDescription: An application is paired with a provider, and with defined policies and other configurations controls user access. It also holds information like UI name, icon, and more.
 ---

website/docs/customize/interfaces/admin/index.mdx

@@ -9,7 +9,7 @@ To add, remove, or modify attributes for a brand, log in to the Admin interface
 
 Most attributes defined in a brand apply to _both_ the User and Admin interfaces. However, any settings that are specific to only the Admin interface are explicitly noted as such below.
 
-The following screenshot shows the syntax for setting several attributes for a brand: dark mode, a 3-column display of applications on the **My applications** page of the User interface, and hiding the API and Notifications drawers from the Admin interface toolbar.
+The following screenshot shows the syntax for setting several attributes for a brand: dark mode, a 3-column display of applications on the **Application Dashboard** page of the User interface, and hiding the API and Notifications drawers from the Admin interface toolbar.
 
 ![](./admin-interface-attributes.png)
 

website/docs/customize/interfaces/user/index.mdx

@@ -9,7 +9,7 @@ To add, remove, or modify attributes for a brand, log in as an administrator and
 
 Most attributes defined in a brand apply to _both_ the User and Admin interfaces. However, any settings that are specific to only one interface are explicitly noted as such below.
 
-The following screenshot shows the syntax for setting several attributes for a brand: light mode, a 3-column display of applications on the **My applications** page, hiding the API drawer and the Notification drawer from the toolbar, and disallowing users to edit applications on the **My applications** page.
+The following screenshot shows the syntax for setting several attributes for a brand: light mode, a 3-column display of applications on the **Application Dashboard** page, hiding the API drawer and the Notification drawer from the toolbar, and disallowing users to edit applications on the **Application Dashboard** page.
 
 ![](./user-interface-attributes.png)
 
@@ -27,7 +27,7 @@ import Enabledfeatureslist from "../\_enabledfeatureslist.mdx";
 
 #### `settings.enabledFeatures.applicationEdit` (User interface only)
 
-Display the Edit option for each application on the **My applications** page (only shown when the user is a superuser).
+Display the Edit option for each application on the **Application Dashboard** page (only shown when the user is a superuser).
 
 import Generalattributes from "../\_generalattributes.mdx";
 
@@ -37,7 +37,7 @@ import Generalattributes from "../\_generalattributes.mdx";
 
 #### `settings.layout.type`
 
-Which layout to use for the **My applications** page. Defaults to `row`. Choices: `row`, `2-column`, `3-column`
+Which layout to use for the **Application Dashboard** page. Defaults to `row`. Choices: `row`, `2-column`, `3-column`
 
 import Global from "../_global/global.mdx";
 

website/docs/enterprise/manage-enterprise.mdx

@@ -100,9 +100,9 @@ Accounts that are disabled, as well as service accounts, are excluded from the l
 
 ### Internal vs external users
 
-An **internal** user is typically a team member, such as a company employee, who is granted access to the full Enterprise feature set. This includes the ability to view and use the **My Applications** and **User Settings** pages.
+An **internal** user is typically a team member, such as a company employee, who is granted access to the full Enterprise feature set. This includes the ability to view and use the **Application Dashboard** and **User Settings** pages.
 
-An **external** user might be an external consultant, a volunteer in a charitable site, or a B2C customer. External users can't access the **My Applications** and **User Settings** pages. Instead, external users are typically authenticated and then redirected to log directly into their [default application](../sys-mgmt/brands/index.md#external-user-settings).
+An **external** user might be an external consultant, a volunteer in a charitable site, or a B2C customer. External users can't access the **Application Dashboard** and **User Settings** pages. Instead, external users are typically authenticated and then redirected to log directly into their [default application](../sys-mgmt/brands/index.md#external-user-settings).
 
 ### License violation notifications
 

website/docs/install-config/first-steps/index.mdx

@@ -51,7 +51,7 @@ Now that you have your authentik instance installed and configured with the requ
 
 :::tip Security Best Practice
 
-In a production environment, best practice is to first [create a group](../../users-sources/groups/manage_groups.mdx#create-a-group), then [create the user(s)](../../users-sources/user/user_basic_operations.md#create-a-user), and then add the application. Then you can configure the application to have a [binding](../../add-secure-apps/bindings-overview/work-with-bindings.md#) to a specific group or user. The binding controls the access to the application (whether or not it is displayed on a user's My Applications page).
+In a production environment, best practice is to first [create a group](../../users-sources/groups/manage_groups.mdx#create-a-group), then [create the user(s)](../../users-sources/user/user_basic_operations.md#create-a-user), and then add the application. Then you can configure the application to have a [binding](../../add-secure-apps/bindings-overview/work-with-bindings.md#) to a specific group or user. The binding controls the access to the application (whether or not it is displayed on a user's Application Dashboard page).
 
 :::
 
@@ -90,7 +90,7 @@ Every application that you add to authentik requires a provider, which is used t
           then access to the application is granted. The mode **ALL** means that every one of any
           policies bound to the application must pass in order for a user to have access to the
           application.
-    - **UI Settings**: optional UI settings that are displayed about the application, including the launch URL, and three settings to display extra information about the application on the **My Applications** page: an optional icon, the publisher of the application, and a brief description.
+    - **UI Settings**: optional UI settings that are displayed about the application, including the launch URL, and three settings to display extra information about the application on the **Application Dashboard** page: an optional icon, the publisher of the application, and a brief description.
 - **Choose a Provider type**: select **OAuth2/OpenID Connect** as the provider type.
 - **Configure the Provider**:
     - **Name**: Provide a name (or accept the auto-provided name).
@@ -114,7 +114,7 @@ Every application that you add to authentik requires a provider, which is used t
         - <strong className="tip">TIP</strong>: authentik generates a key that you can use, called
           the `authentik Self-signed Certificate`, if you do not have a specific signing key for an
           application.
-- **Configure Bindings** _(optional)_: for this tutorial, skip this step because you do not yet have a user. Later, after you create your first user, you can [create a binding](../../add-secure-apps/bindings-overview/work-with-bindings.md) to manage the display and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: for this tutorial, skip this step because you do not yet have a user. Later, after you create your first user, you can [create a binding](../../add-secure-apps/bindings-overview/work-with-bindings.md) to manage the display and access to applications on a user's **Application Dashboard** page.
     - <strong className="tip">TIP</strong>: By creating a binding between an application and a
       specific user, you are ensuring that the application is accessible only to that user and any
       other users or groups for whom you created a binding. Learn more about how bindings are used

website/docs/releases/2026/v2026.5.md

@@ -96,14 +96,14 @@ The login flow has additional UI improvements to reduce friction and make it eas
 - Better error handling and messaging for failed login attempts, including more specific error messages for WebAuthn when authentication fails.
 - Additional mobile optimizations, such as better keyboard handling, field focus, and responsive design improvements to make the login flow easier to use on mobile and tablet devices.
 
-### Small general improvements (SAML issuer, hide applications)
+### Small general improvements (SAML issuer, Application Dashboard)
 
 **SAML issuer**: authentik now automatically generates your SAML issuer URL. You can still override the default SAML issuer.
 
-**Hide applications**: You can [hide applications](../../add-secure-apps/applications/manage_apps.mdx#hide-applications) from the **My applications** page for situations when a user needs access to an application that should not appear there.
+**Application Dashboard**: The **My applications** page has been renamed to **Application Dashboard**, and related option labels have been updated to match. Our documentation and integration guides have been updated as well. You can now also [hide applications](../../add-secure-apps/applications/manage_apps.mdx#hide-applications) from the **Application Dashboard** page using the new **Hide from Application Dashboard** toggle.
 
 :::info
-Before authentik 2026.5, an application was hidden by setting its **Launch URL** to `blank://blank`. Existing applications using that value are automatically migrated to using the **Hide from My applications** option upon upgrading.
+Before authentik 2026.5, an application was hidden by setting its **Launch URL** to `blank://blank`. Existing applications using that value are automatically migrated to using the **Hide from Application Dashboard** option upon upgrading.
 :::
 
 ### Performance improvements

website/docs/users-sources/groups/manage_groups.mdx

@@ -53,7 +53,7 @@ Roles are inherited through group hierarchy. If a parent group has a role assign
 
 ## Bind a group to an application
 
-These bindings control which groups can access an application, and whether or not the application is visible in a group member's **My applications** page. If no bindings for an application are defined, this means that all users and groups can access the application.
+These bindings control which groups can access an application, and whether or not the application is visible in a group member's **Application Dashboard** page. If no bindings for an application are defined, this means that all users and groups can access the application.
 
 For instructions refer to [Manage applications](../../add-secure-apps/applications/manage_apps.mdx#bind-a-user-or-group-to-an-application).
 

website/docs/users-sources/user/user-interface.mdx

@@ -13,7 +13,7 @@ This document covers the basic tasks that end-users accomplish in the User inter
 
 ## Access the User interface
 
-As an end-user, you will typically first see the User interface when you log in to authentik. The main page of the User interface is the **My applications** page, where you can find all of the applications that you access through authentik.
+As an end-user, you will typically first see the User interface when you log in to authentik. The main page of the User interface is the **Application Dashboard** page, where you can find all of the applications that you access through authentik.
 
 To view your own settings click the gear icon in the upper right. The following sections are displayed on the page:
 

website/docs/users-sources/user/user_basic_operations.md

@@ -99,7 +99,7 @@ Users also inherit roles from the groups they belong to. The **Roles** tab has t
 
 ## Bind a user to an application
 
-These bindings control which users can access an application, and whether or not the application is visible in the user's **My applications** page. If no bindings for an application are defined, this means that all users and groups can access the application.
+These bindings control which users can access an application, and whether or not the application is visible in the user's **Application Dashboard** page. If no bindings for an application are defined, this means that all users and groups can access the application.
 
 For instructions refer to [Manage applications](../../add-secure-apps/applications/manage_apps.mdx#bind-a-user-or-group-to-an-application).
 

website/integrations/chat-communication-collaboration/affine/index.md

@@ -35,7 +35,7 @@ To support the integration of AFFiNE with authentik, you need to create an appli
         - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
         - Add one `Strict` redirect URI and set it to `https://affine.company/oauth/callback`.
         - Select any available signing key.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/chatgpt/index.mdx

@@ -49,7 +49,7 @@ To support the integration of ChatGPT with authentik, you need to create an appl
         - Note the **Client ID** and **Client Secret** values because they will be required later.
         - Temporarily set a `Strict` redirect URI to `https://temp.temp`.
         - Select any available signing key.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 
@@ -96,7 +96,7 @@ To support the integration of ChatGPT with authentik, you need to create an appl
     - **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
         - Temporarily set the **ACS URL** to `https://temp.temp` (you will update this after completing the ChatGPT configuration).
         - Under **Advanced protocol settings**, set **Signing Certificate** to use any available certificate.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/espo-crm/index.md

@@ -40,7 +40,7 @@ To support the integration of EspoCRM with authentik, you need to create an appl
         - Set a `Strict` redirect URI to `https://espocrm.company/oauth-callback.php`.
         - Select any available signing key.
         - Under **Advanced protocol settings**, set **Subject mode** to **Based on the User's username**.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/hedgedoc/index.md

@@ -35,7 +35,7 @@ To support the integration of HedgeDoc with authentik, you need to create an app
         - Note the **Client ID** and **Client Secret** values because they will be required later.
         - Set a `Strict` redirect URI to `https://hedgedoc.company/auth/oauth2/callback`.
         - Select any available signing key.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 3. Click **Submit** to save the new application and provider.
 
 ## HedgeDoc configuration

website/integrations/chat-communication-collaboration/joplin/index.md

@@ -59,7 +59,7 @@ To support the integration of Joplin with authentik, you need to create property
     - Set the **ACS URL** to `https://joplin.company/api/saml`.
     - Under **Advanced protocol settings**, select an available **Signing certificate** and ensure **Sign assertions** and **Sign responses** are enabled.
     - Under **Property mappings**, add the two property mappings created in the previous section.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/kanboard/index.md

@@ -35,7 +35,7 @@ To support the integration of Kanboard with authentik, you need to create an app
         - Note the **Client ID** and **Client Secret** values because they will be required later.
         - Set a `Strict` redirect URI to `https://kanboard.company/oauth/callback`.
         - Select any available signing key.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/kimai/index.md

@@ -39,7 +39,7 @@ To support the integration of Kimai with authentik, you need to create an applic
             - Select an available **Signing certificate**.
             - Set **NameID Property Mapping** to `authentik default SAML Mapping: Email`.
             - Set **Default NameID Policy** to `Email Address`.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/mailcow/index.md

@@ -40,7 +40,7 @@ To support the integration of mailcow with authentik, you need to create an appl
     - Note the **Client ID** and **Client Secret** values because they will be required later.
     - Set a `Strict` redirect URI to `https://mailcow.company`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/mastodon/index.md

@@ -36,7 +36,7 @@ To support the integration of Mastodon with authentik, you need to create an app
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://mastodon.company/auth/auth/openid_connect/callback`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/matrix-synapse/index.md

@@ -37,7 +37,7 @@ To support the integration of Matrix Synapse with authentik, you need to create
     - Set a `Strict` redirect URI to `https://matrix.company/_synapse/client/oidc/callback`.
     - Select any available RSA signing key. Matrix Synapse doesn't support ECC keys.
     - Do not set an encryption key because this is not supported by Matrix Synapse.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/mattermost-team-edition/index.mdx

@@ -86,7 +86,7 @@ The following `id` property mapping is optional. If omitted, Mattermost will gen
         - Set a `Strict` redirect URI to `https://mattermost.company/signup/gitlab/complete`.
         - Select any available signing key.
         - Under **Advanced protocol settings**, add the scopes you just created to the list of selected scopes.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 
@@ -166,7 +166,7 @@ To support the integration of Mattermost with authentik via SAML, you need to up
             - Enable **Sign responses**.
             - Set the **Verification Certificate** to the Mattermost certificate you uploaded earlier.
             - Set the **Encryption Certificate** to the Mattermost certificate you uploaded earlier.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/mobilizon/index.md

@@ -36,7 +36,7 @@ To support the integration of Mobilizon with authentik, you need to create an ap
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://mobilizon.company/auth/keycloak/callback`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/nextcloud/index.mdx

@@ -125,7 +125,7 @@ To connect to an existing Nextcloud user, set the `nextcloud_user_id` attribute
         - Under **Advanced protocol settings**:
             - _(optional)_ If you created the `Nextcloud Profile` scope mapping, add it to **Selected Scopes**.
             - **Subject Mode**: `Based on the User's UUID`
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 
@@ -220,7 +220,7 @@ If you require [server side encryption](https://docs.nextcloud.com/server/latest
         - Set the **ACS URL** to `https://nextcloud.company/apps/user_saml/saml/acs`.
         - Set the **Audience** to `https://nextcloud.company/apps/user_saml/saml/metadata`.
         - Under **Advanced protocol settings**, set an available **Signing certificate**.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 
@@ -348,7 +348,7 @@ This documentation lists only the settings that you need to change from their de
     - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings.
     - **Choose a Provider type**: select **LDAP** as the provider type.
     - **Configure the Provider**: provide a name (or accept the auto-provided name) and the bind flow to use for this provider
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/openproject/index.md

@@ -67,7 +67,7 @@ OpenProject requires a first and last name for each user. By default authentik o
         - **Scopes**:
             - Remove `authentik default OAuth Mapping: OpenID 'profile'` from **Selected Scopes**.
             - Add the scope that you created in the previous section (e.g. `Open Project Profile Scope`) to **Selected Scopes**.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/owncloud/index.md

@@ -70,7 +70,7 @@ The configuration for each application is nearly identical, except for the **Cli
     - **Advanced protocol settings:**
         - **Scopes**: Select the following scopes for each of the four application/provider pairs: `email`, `offline_access`, `openid`, `profile`.
 
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/placetel/index.md

@@ -38,7 +38,7 @@ To support the integration of Placetel with authentik, you need to create an app
         - Ensure that **Encryption Certificate** is empty.
         - Remove all **Property Mappings** except for `authentik default SAML Mapping: Email`.
         - Set **NameID Property Mapping** to `authentik default SAML Mapping: Email`.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/planka/index.mdx

@@ -35,7 +35,7 @@ To support the integration of Planka with authentik, you need to create an appli
         - Note the **Client ID** and **Client Secret** values because they will be required later.
         - Set a `Strict` redirect URI to `https://planka.company/oidc-callback`.
         - Select any available signing key.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/rocketchat/index.md

@@ -40,7 +40,7 @@ To support the integration of Rocket.chat with authentik, you need to create an
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://rocket.company/\_oauth/authentik`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/roundcube/index.md

@@ -63,7 +63,7 @@ To support the integration of Roundcube with authentik, you need to create an ap
     - Select any available signing key.
     - Under **Advanced protocol settings**:
         - Under **Scopes**, add `dovecotprofile` and `authentik default OAuth Mapping: OpenID 'offline_access'` to the list of selected scopes.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/seatable/index.md

@@ -40,7 +40,7 @@ To support the integration of SeaTable with authentik, you need to create an app
         - Set the **ACS URL** to `https://seatable.company/saml/acs/`.
         - Set the **Audience** to `https://seatable.company/saml/metadata/`.
         - Under **Advanced protocol settings**, set an available **Signing certificate**.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/slack/index.md

@@ -52,7 +52,7 @@ To support the integration of Slack with authentik, you need to create an applic
 - **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
     - Set the **ACS URL** to `https://company.slack.com/sso/saml`.
     - Under **Advanced protocol settings**, select an available **Signing certificate** and add the two **Property Mappings** you created in the previous section.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/vikunja/index.mdx

@@ -44,7 +44,7 @@ To support the integration of Vikunja with authentik, you need to create an appl
         - For web login, set a `Strict` redirect URI to `https://vikunja.company/auth/openid/authentik`.
         - If using the Vikunja desktop client, add a `Regex` redirect URI such as `^http://127\\.0\\.0\\.1:[0-9]+/auth/openid/authentik$` to allow loopback redirects to `127.0.0.1`.
         - Select any available signing key.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 3. Click **Submit** to save the new application and provider.
 
 ## Vikunja configuration

website/integrations/chat-communication-collaboration/wekan/index.mdx

@@ -36,7 +36,7 @@ To support the integration of Wekan with authentik, you need to create an applic
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://wekan.company/_oauth/oidc`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/writefreely/index.md

@@ -40,7 +40,7 @@ To support the integration of Writefreely with authentik, you need to create an
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://writefreely.company/oauth/callback/generic`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/zoom/index.md

@@ -42,7 +42,7 @@ To support the integration of Zoom with authentik, you need to create an applica
         - Set the **Logout Method** to `Front-channel (Native)`.
         - Set the **Audience** to `company.zoom.us`.
         - Under **Advanced protocol settings**, select an available **Signing Certificate**.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/chat-communication-collaboration/zulip/index.md

@@ -38,7 +38,7 @@ To support the integration of Zulip with authentik, you need to create an applic
     - Set the **SLS Binding** to `Redirect`.
     - Set the **Logout Method** to `Front-channel (Iframe)`.
     - Under **Advanced protocol settings**, select an available **Signing certificate**.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/cloud-providers/aws-classic/index.mdx

@@ -113,7 +113,7 @@ To support the integration of AWS with authentik via the Classic IAM method, you
         - Set the **Audience** to `urn:amazon:webservices`
         - Under **Advanced protocol settings**, select an available **Signing Certificate**, ensure both **Signing Assertions** and **Signing Responses** are enabled, then add, under **Property Mappings**, both property mappings you created in the previous section.
         - Set **NameID Property Mapping** to `authentik default SAML Mapping: Email`.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 
@@ -235,7 +235,7 @@ Repeat the role creation process for each role that you want to make available t
 
 ### Test the integration
 
-1. Log in to authentik and visit the Application library.
+1. Log in to authentik and visit the Application Dashboard.
 2. Click on the AWS application.
 3. You should be redirected to AWS and logged in. Check the top-right corner of the AWS console to verify your identity is displayed in the format `<role_name>/<username>` (e.g., `authentik-admin/dominic`).
 
@@ -273,7 +273,7 @@ To support the integration of AWS with authentik using OIDC, you need to create
         - Set a `Strict` redirect URI to match the AWS resource that you want to access via OIDC.
         - Select any available signing key.
         - Under **Advanced protocol settings** > **Selected Scopes**, add `authentik default OAuth Mapping: OpenID 'entitlements'`.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/cloud-providers/aws/index.mdx

@@ -56,7 +56,7 @@ To support the integration of AWS with authentik using SAML, you need to create
         - Under **Advanced Protocol Settings**:
             - Set an available signing certificate.
             - Set **NameID Property Mapping** to `authentik default SAML Mapping: Email`.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/cloud-providers/digitalocean/index.md

@@ -77,7 +77,7 @@ To support the integration of DigitalOcean with authentik, you need to create a
         - Under **Advanced protocol settings**:
             - Add the `profile` scope created in the previous section. Do not remove authentik’s `authentik default OAuth Mapping: OpenID 'profile'`, as claims such as `name` are required by DigitalOcean.
             - Under **Advanced protocol settings** > **Selected Scopes**, add `authentik default OAuth Mapping: OpenID 'entitlements'`.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/cloud-providers/oracle-cloud/index.md

@@ -37,7 +37,7 @@ To support the integration of Oracle Cloud with authentik, you need to create an
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://tenant.identity.oraclecloud.com/oauth2/v1/social/callback`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 
@@ -68,7 +68,7 @@ To integrate authentik with Oracle Cloud, you must configure authentik as a soci
 
 ## Configuration verification
 
-To confirm that authentik is correctly configured with Oracle Cloud, log out of your current session. Then, try signing in by either selecting the application's icon in the User Library or by going directly to the Oracle Cloud login page, depending on your setup. On the login page, click **authentik**. You'll be redirected to authentik, and after a successful login, automatically signed in to Oracle Cloud.
+To confirm that authentik is correctly configured with Oracle Cloud, log out of your current session. Then, try signing in by either selecting the application's icon in the Application Dashboard or by going directly to the Oracle Cloud login page, depending on your setup. On the login page, click **authentik**. You'll be redirected to authentik, and after a successful login, automatically signed in to Oracle Cloud.
 
 ## Resources
 

website/integrations/cloud-providers/ovhcloud/index.md

@@ -33,7 +33,7 @@ To support the integration of OVHcloud with authentik, you need to create an app
             - `https://us.ovhcloud.com/auth/` for US region.
         - Under **Advanced protocol settings**, set an available **Signing certificate**.
 
-    - **Configure Bindings** _(optional)_: You can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: You can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/dashboards/homarr/index.md

@@ -36,7 +36,7 @@ To support the integration of Homarr with authentik, you need to create an appli
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Create two `Strict` redirect URIs: `https://homarr.company/api/auth/callback/oidc` and `http://localhost:50575/api/auth/callback/oidc`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/dashboards/linkwarden/index.md

@@ -36,7 +36,7 @@ To support the integration of Linkwarden with authentik, you need to create an a
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://linkwarden.company/api/v1/auth/callback/authentik`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/development/coder/index.md

@@ -36,7 +36,7 @@ To support the integration of Coder with authentik, you need to create an applic
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://coder.company/api/v2/users/oidc/callback`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/development/engomo/index.mdx

@@ -49,7 +49,7 @@ To support the integration of Engomo with authentik, you need to create an appli
     - Add two `Strict` redirect URIs and set them to `https://engomo.company/auth` and `com.engomo.engomo://callback/`.
     - Select any available signing key.
     - Under **Advanced protocol settings**, add the scope you just created to the list of available scopes.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/development/forgejo/index.md

@@ -36,7 +36,7 @@ To support the integration of Forgejo with authentik, you need to create an appl
         - Set a `Strict` redirect URI to `https://<forgejo.company>/user/oauth2/authentik/callback`.
         - Select any available signing key.
         - Under **Advanced protocol settings** > **Selected Scopes**, add `authentik default OAuth Mapping: OpenID 'entitlements'`.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/development/frappe/index.md

@@ -42,7 +42,7 @@ To support the integration of Frappe with authentik, you need to create an appli
     - Set a `Strict` redirect URI to `https://frappe.company/api/method/frappe.integrations.oauth2_logins.custom/<provider-name>`. Replace `<provider-name>` with the name of the provider in Frappe.
     - Select any available signing key.
     - Under **Advanced protocol settings**, set **Subject mode** to be `Based on the Users's username`.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/development/ghec-emu/index.mdx

@@ -159,7 +159,7 @@ To support the integration of GitHub Enterprise EMU with authentik, you need to
             - Set **Default NameID Policy** to `urn:oasis:names:tc:SAML:2.0:nameid-format:persistent`.
             - Select an available **Signing certificate**. Download this certificate because it is required later.
             - Enable **Sign assertion** and **Sign response**.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page. If you add the SCIM provider as a backchannel provider later, only users who can view this application are synchronized.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page. If you add the SCIM provider as a backchannel provider later, only users who can view this application are synchronized.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/development/ghec/index.md

@@ -41,7 +41,7 @@ To support the integration of GitHub Enterprise Cloud with authentik, you need t
         - Set **ACS URL** to `https://github.com/orgs/foo/saml/consume`.
         - Set **Audience** to `https://github.com/orgs/foo`.
         - Under **Advanced protocol settings**, select an available **Signing certificate**. Download this certificate because it is required later.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/development/ghes/index.md

@@ -39,7 +39,7 @@ To support the integration of GitHub Enterprise Server with authentik, you need
         - Under **Advanced protocol settings**:
             - Select an available **Signing certificate**. Download this certificate because it is required later.
             - Set **NameID Property Mapping** to `authentik default SAML Mapping: Username`.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page. If you add the SCIM provider as a backchannel provider later, only users who can view this application are synchronized.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page. If you add the SCIM provider as a backchannel provider later, only users who can view this application are synchronized.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/development/gitea/index.md

@@ -37,7 +37,7 @@ To support the integration of Gitea with authentik, you need to create an applic
     - Set a `Strict` redirect URI to `https://<gitea.company>/user/oauth2/authentik/callback`.
     - Select any available signing key.
     - Under **Advanced protocol settings** > **Selected Scopes**, add `authentik default OAuth Mapping: OpenID 'entitlements'`.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/development/gitlab/index.mdx

@@ -113,7 +113,7 @@ To support the integration of GitLab with authentik, you need to create an appli
     - Set a `Strict` redirect URI to `https://gitlab.company/users/auth/openid_connect/callback`.
     - Select any available signing key.
     - Under **Advanced protocol settings**, set the **Subject mode** to `Based on the User's Email`.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/development/gravitee/index.md

@@ -38,7 +38,7 @@ To support the integration of Gravitee with authentik, you need to create an app
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Add two `Strict` redirect URI and set them to `https://gravitee.company/user/login` and `https://gravitee.company/console/`. Ensure a trailing slash is present at the end of the second redirect URI.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/development/jenkins/index.md

@@ -36,7 +36,7 @@ To support the integration of Jenkins with authentik, you need to create an appl
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://jenkins.company/securityRealm/finishLogin`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/development/node-red/index.md

@@ -42,7 +42,7 @@ To support the integration of Node-RED with authentik, you need to create an app
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://nodered.company/auth/strategy/callback/`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/development/weblate/index.md

@@ -74,7 +74,7 @@ To support the integration of Weblate with authentik, you need to create an appl
     - Set the **ACS URL** to `https://weblate.company/accounts/complete/saml/`.
     - Set the **Audience** to `https://weblate.company/accounts/metadata/saml/`.
     - Under **Advanced protocol settings**, select an available **Signing certificate**. Then, under **Property mappings**, add the ones you just created.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/device-management/meshcentral/index.md

@@ -36,7 +36,7 @@ To support the integration of MeshCentral with authentik, you need to create an
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://meshcentral.company/auth-oidc-callback`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/documentation/appflowy/index.mdx

@@ -54,7 +54,7 @@ To support the integration of AppFlowy with authentik, you need to create a cert
             - **Verification certificate**: select the same certificate
             - **NameID Property Mapping**: `authentik default SAML Mapping: Email`
             - **Default relay state**: `https://appflowy.company/auth/callback`
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 3. Click **Submit** to create the application and provider.
 
 ### Copy metadata download link

website/integrations/documentation/bookstack/index.mdx

@@ -50,7 +50,7 @@ To support the integration of BookStack with authentik, you need to create an ap
         - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
         - Set a `Strict` redirect URI to `https://bookstack.company/oidc/callback`.
         - Select any available signing key.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 
@@ -93,7 +93,7 @@ To support the integration of BookStack with authentik, you need to create an ap
     - Set the **Logout Method** to `Front-channel (Iframe)`.
     - Set the **Audience** to `https://bookstack.company/saml2/metadata`.
     - Under **Advanced protocol settings**, set **Signing Certificate** to use any available certificate.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/documentation/dokuwiki/index.md

@@ -31,14 +31,14 @@ To support the integration of DokuWiki with authentik, you need to create an app
 2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard.
 
 - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings.
-    - _(Optional)_ Under **UI Settings**, set the **Launch URL** to `https://dokuwiki.company/doku.php?id=start&oauthlogin=generic`. This will allow you to log in directly to DokuWiki from the authentik applications dashboard and skip the DokuWiki OAuth Login button.
+    - _(Optional)_ Under **UI Settings**, set the **Launch URL** to `https://dokuwiki.company/doku.php?id=start&oauthlogin=generic`. This will allow you to log in directly to DokuWiki from the authentik Application Dashboard and skip the DokuWiki OAuth Login button.
 - **Choose a Provider type**: select **OAuth2/OpenID Connect** as the provider type.
 - **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
     - Note the **Client ID** and **Client Secret** values because they will be required later.
     - Set a `Strict` redirect URI to `https://dokuwiki.company/doku.php`.
     - Select any available signing key.
     - Under **Advanced protocol settings**, add the following OAuth mapping under **Scopes**: `authentik default OAuth Mapping: OpenID 'offline_access'`
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/documentation/glpi/index.md

@@ -92,7 +92,7 @@ To support the integration of GLPI with authentik, you need to create property m
             - Select any available **Signing Certificate** and enable **Sign assertions**.
             - Set **NameID Property Mapping** to `authentik default SAML Mapping: Email`.
             - Under **Property mappings**, add the two property mappings that you created in the previous section: `givenname` and `surname`.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/documentation/karakeep/index.md

@@ -36,7 +36,7 @@ To support the integration of Karakeep with authentik, you need to create an app
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://karakeep.company/api/auth/callback/custom`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/documentation/mealie/index.md

@@ -36,7 +36,7 @@ To support the integration of Mealie with authentik, you need to create an appli
     - Note the **Client ID**, **Client Secret**, , and **slug** values because they will be required later.
     - Create two `Strict` redirect URIs and set to `https://mealie.company/login` and `https://mealie.company/login?direct=1`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/documentation/netbox/index.md

@@ -36,7 +36,7 @@ To support the integration of NetBox with authentik, you need to create an appli
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://netbox.company/oauth/complete/oidc/`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/documentation/outline/index.md

@@ -38,7 +38,7 @@ To support the integration of Outline with authentik, you need to create an appl
     - Set a `Strict` redirect URI to `https://outline.company/auth/oidc.callback`.
     - Select any available signing key.
     - Under **Advanced protocol settings**, set the **Subject Mode** to **Based on the User's username**.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/documentation/paperless-ngx/index.mdx

@@ -34,7 +34,7 @@ To support the integration of Paperless-ngx with authentik, you need to create a
     - **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
         - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
         - Set a `Strict` redirect URI to `https://paperless.company/accounts/oidc/authentik/login/callback/`.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
     - **Advanced protocol settings**:
         - **Selected Scopes**: Add the following
             - `authentik default OAuth Mapping: OpenID 'openid'`

website/integrations/documentation/papra/index.mdx

@@ -35,7 +35,7 @@ To support the integration of Papra with authentik, you need to create an applic
         - Note the **Client ID**, **Client Secret**, and **Slug** values because they will be required later.
         - Set a `Strict` redirect URI to `https://papra.company/api/auth/oauth2/callback/authentik`.
         - Select any available signing key.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/documentation/tandoor/index.md

@@ -36,7 +36,7 @@ To support the integration of Tandoor with authentik, you need to create an appl
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://tandoor.company/accounts/oidc/authentik/login/callback/`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/documentation/wiki-js/index.md

@@ -46,7 +46,7 @@ To support the integration of Wiki.js with authentik, you need to create an appl
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://wiki.company/login/id-from-wiki/callback`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/documentation/youtrack/index.md

@@ -38,7 +38,7 @@ To support the integration of YouTrack with authentik, you need to create an app
     - Set the **Audience** to `https://placeholder.com`. You will replace this after YouTrack provides the real SP entity ID.
     - Under **Advanced protocol settings**, set an available signing key and make sure **Sign assertions** is toggled.
     - Then, also under **Advanced protocol settings**, make sure **NameID Property Mapping** is set to `authentik default SAML Mapping: username`. Make sure the [Allow users to change username](https://docs.goauthentik.io/docs/sys-mgmt/settings#allow-users-to-change-username) setting is disabled to prevent authentication issues.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/hypervisors-orchestrators/arcane/index.md

@@ -57,7 +57,7 @@ Arcane either requires the email scope to return a `true` value for whether the
         - Select any available signing key.
         - Under **Advanced protocol settings**:
             - Remove the `authentik default OAuth Mapping: OpenID 'email'` scope, and add the custom scope mapping you created above.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/hypervisors-orchestrators/portainer/index.md

@@ -41,7 +41,7 @@ To support the integration of Portainer with authentik, you need to create an ap
     - Set a `Strict` redirect URI to `https://portainer.company/`.
     - Select any available signing key.
     - Under **Advanced protocol settings** > **Selected Scopes**, add `authentik default OAuth Mapping: OpenID 'entitlements'`.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/hypervisors-orchestrators/proxmox-ve/index.md

@@ -43,7 +43,7 @@ To support the integration of Proxmox with authentik, you need to create an appl
     - Ensure that encryption is disabled.
     - Under **Advanced protocol settings**:
         - Set **Subject mode** to `Based on the User's Email`.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/hypervisors-orchestrators/vmware-cloud-director/index.md

@@ -33,7 +33,7 @@ To support the integration of VMware Cloud Director with authentik, you need to
         - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
         - Set a `Strict` redirect URI to `https://clouddirector.company/login/oauth?service=provider`.
         - Select any available signing key.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 :::info Tenant configuration
 The redirect URI is for provider level configuration. If you're configuring a tenant-level integration in VMware Cloud Director, use the URI displayed in [step 2 of the VMware Cloud Director configuration](#vmware-cloud-director-configuration).

website/integrations/hypervisors-orchestrators/vmware-vcenter/index.md

@@ -38,7 +38,7 @@ To support the integration of vCenter with authentik, you need to create an appl
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://vcenter.company/ui/login/oauth2/authcode`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/hypervisors-orchestrators/xen-orchestra/index.md

@@ -41,7 +41,7 @@ To support the integration of Xen Orchestra with authentik, you need to create a
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to `https://xenorchestra.company/signin/oidc/callback`.
     - Select any available signing key.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/infrastructure/apache-guacamole/index.mdx

@@ -40,7 +40,7 @@ To support the integration of Apache Guacamole with authentik, you need to creat
     - Set a `Strict` redirect URI to `https://guacamole.company/`. If you have configured [Apache Tomcat](https://tomcat.apache.org/) to run Apache Guacamole on a subpath, you will need to update this value accordingly.
     - Select any available signing key.
     - Note that Apache Guacamole does not support session tokens longer than 300 minutes (5 hours).
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/infrastructure/argocd/index.md

@@ -35,7 +35,7 @@ To support the integration of ArgoCD with authentik, you need to create an appli
         - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
         - Add two `Strict` redirect URI and set them to `https://argocd.company/api/dex/callback` and `https://localhost:8085/auth/callback`.
         - Select any available signing key.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/infrastructure/awx-tower/index.md

@@ -40,7 +40,7 @@ To support the integration of AWX Tower with authentik, you need to create an ap
     - Set the **ACS URL** to `https://awx.company/sso/complete/saml/`.
     - Set the **Audience** to `awx`.
     - Under **Advanced protocol settings**, select an available **Signing certificate**.
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/infrastructure/harbor/index.md

@@ -40,7 +40,7 @@ To support the integration of Harbor with authentik, you need to create an appli
     - **Advanced Protocol Settings**:
         - **Scopes**: add `authentik default OAuth Mapping: OpenID 'offline_access'` to **Selected Scopes**.
 
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/infrastructure/keycloak/index.mdx

@@ -52,7 +52,7 @@ To support the integration of Keycloak with authentik, you need to create an app
         - Set the **Logout URI** to `https://keycloak.company/realms/<keycloak-realm-name>/protocol/openid-connect/logout/backchannel-logout`.
         - Set the **Logout Method** to `Back-channel`.
         - Select any available signing key.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 
@@ -88,7 +88,7 @@ To support the integration of Keycloak with authentik, you need to create an app
         - Set the **Audience** to `https://keycloak.company/realms/<keycloak-realm-name>`.
         - Under **Advanced protocol settings**, set **Signing Certificate** to use any available certificate.
 
-- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/infrastructure/komodo/index.mdx

@@ -35,7 +35,7 @@ To support the integration of Komodo with authentik, you need to create an appli
         - Note the **Client ID** and **Client Secret** values because they will be required later.
         - Set a `Strict` redirect URI to `https://komodo.company/auth/oidc/callback`.
         - Select any available signing key.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.
 

website/integrations/infrastructure/minio/index.mdx

@@ -42,7 +42,7 @@ To support the integration of MinIO with authentik, you need to create an applic
         - Note the **Client ID** and **Client Secret** values because they will be required later.
         - Set a `Strict` redirect URI to `https://minio.company/oauth_callback`.
         - Select any available signing key.
-    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
+    - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
 
 3. Click **Submit** to save the new application and provider.