> For the complete documentation index, see [llms.txt](https://docs.released.so/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.released.so/guide/getting-started/setup-guide.md).

# Setup Guide

{% stepper %}
{% step %}

#### Install Released

Learn how to install Released from the Atlassian marketplace.

{% content-ref url="/pages/nKmXMm9RXx2kOKw7UQUF" %}
[Installing Released](/guide/getting-started/setup-guide/installing-the-app.md)
{% endcontent-ref %}
{% endstep %}

{% step %}

#### Setup your Hub

The Product Hub serves as a central hub for accessing your portals. Customize the branding, terminology and domain where your Hub can be reached.

{% content-ref url="/pages/i4gki5pPUDjXyF4jQgx8" %}
[Product Hub](/guide/product/administration/general.md)
{% endcontent-ref %}
{% endstep %}

{% step %}

#### Create a workspace

Workspaces are your internal control center. This is where your team creates roadmap views, writes release notes, and manages feedback.

{% content-ref url="/pages/sRUzRQum19v6hLj1UzCP" %}
[Workspaces & Portals](/guide/product/portals.md)
{% endcontent-ref %}
{% endstep %}

{% step %}

#### Customize your portal

Portals are the external-facing side of Released. They’re where you share the content created in a workspace with a specific audience.

Manage [access](/guide/product/portals/access.md) and customize the look and feel of your portal.

{% content-ref url="/pages/MCPtjQdINLhgfcWPjlQ4" %}
[Portal](/guide/product/portals/portal.md)
{% endcontent-ref %}

**Embedding a portal**

Embed a portal into your website or app,

{% content-ref url="/pages/ispJ29ISoPloJpGTzDOR" %}
[Page Embed](/guide/product/portals/portal/announcement-page.md)
{% endcontent-ref %}

{% content-ref url="/pages/NBuObCAJ5ItQ3Acn0WEq" %}
[Widget Embed](/guide/product/portals/portal/widget.md)
{% endcontent-ref %}
{% endstep %}

{% step %}

#### Verify your users <mark style="color:$info;">(optional)</mark>

To create a seamless experience when you embed portals, you can verify a user’s identity automatically. This removes the need for them to log in to view private portals or leave feedback.

{% content-ref url="/pages/uxxQ5dtYHYwQ0jl9ynSY" %}
[Implementing User Verification](/guide/getting-started/setup-guide/implementing-user-verification.md)
{% endcontent-ref %}
{% endstep %}

{% step %}

#### Integrations <mark style="color:$info;">(optional)</mark>

Integrate Released with the apps you're already using.

{% content-ref url="/pages/hAhLp2i5l8IKvVxBhbI9" %}
[Integrations](/guide/product/integrations.md)
{% endcontent-ref %}
{% endstep %}
{% endstepper %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.released.so/guide/getting-started/setup-guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.