> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/inbox-and-messaging/domains/how-to-use-your-own-domain-for-the-guest-portal.md).

# How to use your own domain for the guest portal

This guide shows you how to open the guest portal on your own domain, such as guests.yourcompany.com, instead of the Guestway address.

{% hint style="info" %}
**Before you start**

* You need access to the DNS settings of your domain provider, for example GoDaddy, Cloudflare or OVH.
* You have the **Admin** or **Super admin** role, or a role with **Advanced configuration** → **Domains** at **Edit**. See [Users and roles](https://docs.guestway.io/account-and-administration/users-and-roles.md).
  {% endhint %}

## Add the portal domain

{% stepper %}
{% step %}

### Open the domains

Go to **Settings** → **Domains** and open the **Guest portal domains** tab.
{% endstep %}

{% step %}

### Add the domain

Click **Add portal domain**. Enter the **Domain**, for example *guests.yourcompany.com*, and click **Create**. The domain opens.

Guestway prepares the domain. When **Setup** shows **Not Done**, click the check icon (**Check domain status**) to try again.
{% endstep %}
{% endstepper %}

## Add the DNS records

{% stepper %}
{% step %}

### Copy the record

Open the domain. In **DNS record**, copy the **Name** and the **Value** of the CNAME record.

If someone else manages your domain, click **Email these instructions** and send them the record.
{% endstep %}

{% step %}

### Add it at your domain provider

In the DNS settings of your domain provider, add a CNAME record with this name and value. Save.
{% endstep %}
{% endstepper %}

## Verify the domain

{% stepper %}
{% step %}

### Check the domain

Open the domain in **Settings** → **Domains** and click the check icon (**Check domain status**).

Changes at your domain provider can take up to 24 hours. If **DNS record** is not done yet, wait and check again.
{% endstep %}

{% step %}

### Wait for the secure connection

When the DNS record is in place, Guestway adds a security certificate automatically. When **HTTPS** is done, the domain shows **Verified**.
{% endstep %}
{% endstepper %}

## Use the domain for the guest portal

{% stepper %}
{% step %}

### Open the branding

Open the domain in **Settings** → **Domains**. In the step **Use it**, click **Choose it in a branding**.

If you have one branding, its editor opens at **Custom domains**. If you have more than one, the list of brandings opens: open the branding that you want to change.
{% endstep %}

{% step %}

### Select the domain in your branding

In **Guest portal domain**, select the domain instead of **Guestway default**. Click **Save changes**. See [Branding](https://docs.guestway.io/guest-experience/branding.md).

Guests of the properties with this branding now open the guest portal on your domain.
{% endstep %}
{% endstepper %}

## Related

* [Domains](https://docs.guestway.io/inbox-and-messaging/domains.md#guest-portal-domains)
* [Guest portal](https://docs.guestway.io/guest-experience/guest-portal.md)
* [Branding](https://docs.guestway.io/guest-experience/branding.md)
* [How to use your own domain for short links](https://docs.guestway.io/inbox-and-messaging/domains/how-to-use-your-own-domain-for-short-links.md)


---

# 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.guestway.io/inbox-and-messaging/domains/how-to-use-your-own-domain-for-the-guest-portal.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.
