> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/hablla/settings/domains.md).
# Domains
## 🧭 Introduction
The system allows the user to register **custom domains** to create your own, friendly, and easy-to-share URLs.\
These domains are used in various features — such as calendars, public pages, scheduling links, forms, and areas accessible by external clients.
> 🌟 **Real example:**\
> `https://agendamento.seusistema.com/hablla`\
> In this case, **hablla** is the *slug* configured by the user. **agendamento.seusistema.com** is the *domain* configured by the user.
***
## 🎯 What is the domain for?
The domain allows the user to create custom URLs for:
* 📅 Calendar and scheduling pages
* 💬 Webchat
* 🛠 Public platform services
* 🔗 Custom shareable links
* 🧭 Public identification of resources without exposing internal IDs
> 💡 **Direct benefit:** it improves visual identity and makes promotion easier, allowing memorable and professional URLs.
***
## 🔍 What is a **slug** and what is the difference from a domain?
A **slug** is the final part of a URL, which uniquely identifies a resource within the system. In a parallel example, it would be the identification of a room in a building.
#### Examples:
* `meusite.com/**support**`
* `meusite.com/**attendant-john**`
* `meusite.com/**central**`
#### Main characteristics:
* 🔹 Must be **unique**
* 🔹 Must be **short and friendly**
* 🔹 Cannot contain spaces or complex special characters
* 🔹 Makes the URL accessible and more professional
***
## ❌ Important restrictions
#### 🔸 1. Repeating slugs is not allowed
Each slug must be unique to avoid URL conflicts.
> 🛑 **If two calendars used the same domain:**\
> `agenda.hablla.com/support`\
> → The system would not know which calendar to display.
The correct approach is to use 2 different slugs (allowed on the same domain)
> `agenda.hablla.com/support1`\
> `agenda.hablla.com/support2`
***
## ⚙️ How to register
1. Access [Hablla](https://studio.hablla.com/) as an administrator, go to settings -> domains -> +Add domain
2. After adding your domain within Hablla, you will need to configure DNS so it can be successfully activated. To do this, click on the domain you just registered to open its information.
3. With the window open, copy the information and configure the DNS directly in your provider; after propagation, it will be activated within Hablla.
***
## ❓ Frequently Asked Questions
#### **Can I change the domain later?**
Yes, as long as the new domain is not being used.
#### **Does the domain affect any internal automation?**
No — it only defines the public URL.
#### **What happens to the old URL after changing the domain?**
It stops working immediately.
#### **Can the domain have accents?**
No. Always use simple characters.
---
# 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.hablla.com/hablla-docs-en/hablla/settings/domains.md?ask=&goal=
```
`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.