> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/setup-guidepro/admin/quickstart.md).

# Setting Up a Custom Domain for Equipme

**How to Set Up Your Custom URL for Equipme**\
Would you like your Equipme portal to be accessible to your customers and employees through your own web address (URL), such as [***https://portal.your-company.com***](https://portal.your-company.com/)? Here’s a step-by-step guide on how to set it up. 

If you have any questions or need assistance, you can always contact us: <support@equipme.io>.&#x20;

**Important:**

* To use this feature, you will need the Equipme license add-on "Advanced Customization.
* The custom URL will be the same for all your customers and cannot be set individually for each customer.

**What Does This Mean?**\
Instead of using the general addresses like [https://pro.equipme.io](https://pro.equipme.io/) (for providers) or [https://app.equipme.io](https://app.equipme.io/) (for your customers) to access Equipme, you can publish Equipme under your own web address (URL). This gives a more professional appearance and enhances the trust of your users.

**How Does It Work?**\
To publish Equipme under your domain, you'll need to make an adjustment with your DNS provider, where your domain is registered. This adjustment is called a "CNAME record." It might sound complicated, but it’s essentially just a record that ensures your URL points to Equipme.

**Example:**\
If your desired URL for customer access to Equipme is *portal.your-company.com*, the CNAME record should look like this:

*portal.your-company.com CNAME proxy.equipme.io*

**What Does This Mean?** \
It tells your DNS provider: "When someone enters *portal.your-company.com*, they should be redirected to Equipme.

**How to Proceed:**\
Since the process can vary depending on the DNS provider, it’s a good idea to consult with your DNS administrator or the person managing your website who has access to the DNS provider where your domain is registered. They can create the record quickly and accurately for you.

**Separate URL for Customer and Provider Pages**\
Equipme is a two-sided platform consisting of customer portals and a provider backend.

The provider backend can be accessed by appending “/pro” to your chosen URL for customer portals, e.g., <https://portal.your-company.com/pro>.

However, we recommend creating a separate access point for the provider backend, such as <https://pro.your-company.com/>. To do this, you can set up a redirect on your DNS server from <https://pro.your-company.com/> to <https://portal.your-company.com/pro>.

**Configuration on the Equipme Side**

To complete the process, we need to know which URL you’ve chosen once you’ve set up the DNS records as described above. You can simply provide us with this information [here](https://form.jotform.com/242421577182052). After that, we'll take care of the rest and inform you when the setup is complete.

**Next Step: Configuring Custom Email in Equipme**

In the [next article](https://hub.equipme.io/posts/provider-setup-configuring-custom-email-in-equipme), you'll learn how to set up Equipme so that the platform sends emails to your employees and customers using your custom company email address instead of an @equipme.io address.&#x20;


---

# 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:

```
GET https://hub.equipme.io/setup-guidepro/admin/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.