> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/reference-documentation/application-settings/primary-app-link.md).

# Primary App Link

Assign a specific environment service to be the primary hostname URL

Release shines with multiservice applications.

Your application might have a frontend, a backend, a database, a caching server, and some APIs – all with public hostnames.

When linking to all of your app's services at once (for example, in Release's automated GitHub pull request comments), everyone on your team would need to know which link to click to get to your staging deployment.

Here's a GitHub comment with far too many links:

![Before selecting a Primary App Link](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-ce0b45f0a44e14999ca3d1871d73f3d4a790ac1f%2Fprimary-app-link-pr-before.png?alt=media\&token=8a4d0f24-4554-4202-9664-543c5ce12abd)

By selecting a Primary App Link, Release will show a single URL on your GitHub pull requests and in the environment list summary.

This is a Release pull request comment after selecting a Primary App Link:

![After selecting a Primary App Link](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-ddc1ef1a5049d9600e0b494bccb64cc98925b2fe%2Fprimary-app-link-pr-after.png?alt=media\&token=38a5f7a5-7ee0-4c78-bbe4-93a3b92ce19f)

Selecting a Primary App Link makes it easier to share ephemeral environments without flooding your pull requests with links to irrelevant supporting services.

## How to select a Primary App Link in Release

To select or change your Primary App Link, navigate to **App Settings**, and click on **App Link**.

Click the dropdown to select the hostname template that you would like to use as your Primary App Link, and click **Set Primary Link**.

![Advanced Application Settings for Primary App Link](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-c5890a41864ffb6d5a45054aef0a353f0d82eb41%2Fapp-link.png?alt=media)

If you need to view other supporting services besides the primary app, it is still possible to see all the additional hostnames on the Environment Details page in Release.


---

# 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.release.com/reference-documentation/application-settings/primary-app-link.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.