> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/updates/release-notes/introducing-launchpad-one-click-access-to-your-applications-early-access.md).

# Introducing Launchpad: One-Click Access to Your Applications (Early Access)

**Launchpad** gives users a single place to open the applications they already have access to. Users no longer need to remember a different sign-in address for each application: they open Launchpad, select an application, and BalkanID opens its sign-in page in a new tab — through your identity provider or directly on the application's login page. Launchpad is available as an Early Access capability; contact BalkanID Support to have it turned on for your tenant.

### [**Launchpad**](https://docs.balkan.id/lifecycle-management/launchpad-early-access.md)

Launchpad lists the applications where a user has an active identity, so the page always reflects the access BalkanID has discovered.

**What’s new:**

* **One-click sign-in:** Users select an application tile to open it in a new tab. Each application shows whether it signs in through single sign-on (for example, **SSO via Okta**) or a **Direct URL**.
* **Only the access you already have:** Launchpad shows the user's own identities and hides identities that are suspended, deprovisioned or otherwise switched off in the application.
* **Newly granted access stands out:** Applications granted through a BalkanID access request in the last 14 days are marked **New** until the user opens them.
* **Where the access came from:** The details panel shows the identity the user signs in as, the last access date and the application owner. For access granted through BalkanID, it also shows the originating access request — who requested it, the reviewers, the expiry, the purpose and the reason — with a link to the full request.
* **Search, tiles and list:** Users can search their applications and switch between a tile and a list view.
* **Request what's missing:** The **Request access** button and the **Request an app** tile take users straight to the service catalog (or a new access request) to ask for a new application. Once access is granted, the application appears on Launchpad.

### [**Launch URL for applications**](https://docs.balkan.id/lifecycle-management/launchpad-early-access.md#add-a-launch-url-to-an-application)

Administrators control which applications appear on Launchpad by adding a launch URL to each integration.

**What’s new:**

* **Launch URL field:** The **Optional configuration** step of an integration now has a **Launch URL** field for the application's sign-in address, such as your identity provider's link for the application or the application's login page. Applications without a launch URL are not shown on Launchpad.
* **Safe links only:** Launch URLs must be full **https\://** addresses and cannot contain a username or password.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.balkan.id/updates/release-notes/introducing-launchpad-one-click-access-to-your-applications-early-access.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
