> 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/documentation/equipme-pro/setting-up-your-custom-url.md). # Setting Up Your Custom URL Want your Equipme portal accessible through your own domain—like `https://portal.your-company.com` instead of the generic Equipme URLs? This guide shows you exactly how to make that happen. Using your own branded URL isn't just about looking professional (though that's a nice bonus). It builds trust with your customers and creates a seamless experience across all your platforms. When users see your company's domain in the address bar, they know they're in the right place. **Need Help?** If you get stuck at any point, we're here: [**support@equipme.io**](mailto:support@equipme.io) ### What You'll Need Before diving in, make sure you have: * The **"Advanced Customization"** add-on license for Equipme Pro * Access to your company's DNS provider (or the contact info for whoever manages it) * A registered domain name (the one you already own, like your-company.com) * About 15-30 minutes **Heads up:** Your custom URL will be the same for all customers—you can't set different URLs for different clients. ### How It Works Right now, your Equipme portal lives at addresses like `https://pro.equipme.io` (for you) and `https://app.equipme.io` (for your customers). Here's what you're going to do: you'll create a simple DNS record called a CNAME that tells the internet "when someone visits portal.your-company.com, show them what's at Equipme." It's like putting up a sign that says "our portal is this way." The technical term is a **CNAME record**, but don't let that intimidate you. It's just three pieces of information: 1. **What subdomain you want** (like "portal" or "app") 2. **That it's a CNAME** (you'll select this from a dropdown) 3. **Where to point it** (always `proxy.equipme.io`) **Real-world example** Let's say you want `https://portal.acme-corp.com`. You'd create a CNAME record that looks like: * **Host:** `portal` * **Type:** `CNAME` * **Value:** `proxy.equipme.io` That's it. When someone types in portal.acme-corp.com, they get your Equipme portal. *** ### The Setup Process #### 1. Pick Your URLs First, decide what you want your URLs to be. Most companies go with something like: * **For customers:** `portal.your-company.com` or `app.your-company.com` * **For your team:** `pro.your-company.com` or `admin.your-company.com` Keep it simple and memorable. Your customers will actually type these, so avoid anything overly complicated. #### 2. Find Your DNS Provider Your DNS provider is wherever you registered your domain. Common ones include GoDaddy, Cloudflare, Namecheap, Google Domains, or Amazon Route 53. Not sure who that is? Check with whoever set up your company website, or look at your domain renewal emails—they'll tell you. #### 3. Create the CNAME Record Log into your DNS provider and look for something like "DNS Management" or "DNS Records." The exact wording varies, but every provider has this section. Here's what you'll do: 1. Click "Add Record" or "Create New Record" 2. Choose "CNAME" as the type 3. Enter your subdomain in the "Host" or "Name" field (just `portal`, not the full URL) 4. Enter `proxy.equipme.io` in the "Value" or "Target" field 5. Leave TTL as "Automatic" or set it to "3600" 6. Save it Every DNS provider's interface looks different, but they all have these same fields. If you're not sure where something is, their support team can walk you through it—most have detailed CNAME guides. #### 4. Set Up Provider Access (Recommended) You can access the provider backend by just adding `/pro` to your customer URL (like `portal.your-company.com/pro`), but we recommend creating a separate URL for cleaner bookmarks and better organization. **The simple way:** Create another CNAME record with a subdomain like `pro`, pointing to `proxy.equipme.io`. Now you have `https://pro.your-company.com`. **The redirect way:** Set up a URL redirect from `pro.your-company.com` to `portal.your-company.com/pro`. This requires redirect rules in your DNS provider but gives you more flexibility. #### 5. Wait for DNS to Propagate After you save your CNAME records, the changes need to spread across the internet. This usually takes **15-30 minutes**, but can occasionally take up to 48 hours. You can check if it's live using a tool like whatsmydns.net: 1. Enter your custom URL 2. Select "CNAME" as the record type 3. See if it shows `proxy.equipme.io` #### 6. Let Us Know Once your DNS is set up, email us at [**support@equipme.io**](mailto:support@equipme.io) with: * Your customer portal URL (e.g., ) * Your provider backend URL if you made one (e.g., ) We'll configure everything on our end and let you know when it's ready. Then you can test it out and start using your branded URLs. *** ### When Things Don't Work #### "DNS Record Not Found" Usually means one of three things: * The DNS changes haven't propagated yet (give it another hour) * You typed something wrong in the CNAME record * You edited the wrong domain **Fix it:** Double-check your CNAME setup and use a DNS checker tool. If it's been more than 2 hours and still nothing, contact your DNS provider. #### "Security Certificate Warning" This happens when: * We haven't finished setting up the SSL certificate yet * DNS isn't fully propagated **Fix it:** Wait for our confirmation email. SSL certificates can take a few hours to generate after DNS is working. #### "Page Not Found" or 404 Error This means: * We don't know about your custom URL yet * We haven't finished configuring it **Fix it:** Email us at [**support@equipme.io**](mailto:support@equipme.io) with your URL if you haven't already, or check in if we haven't confirmed completion yet. ### Pro Tips * **Test from multiple places:** Once it's live, try accessing from different devices and networks to make sure everything works * **Update your docs:** Change any internal documentation, training materials, or bookmarks to use the new URLs * **Tell people ahead of time:** Give your team and customers a heads up before switching over * **Keep your DNS info handy:** Write down which DNS provider you use and what URLs you configured—you'll thank yourself later ### What's Next? Once your custom URL is running, you'll want to set up custom email next. This lets Equipme send emails from your company's domain instead of @equipme.io, which completes the branded experience. custom-email-setup.md ### Quick Reference **Common DNS provider help topics to search:** * **GoDaddy:** "Add a CNAME record" * **Cloudflare:** "Managing DNS records" * **Namecheap:** "How to create a CNAME record" * **Amazon Route 53:** "Creating records" * **Google Domains:** "Add a CNAME record" **Key terms:** * **CNAME Record:** An alias that points one domain to another * **DNS Provider:** Where your domain is registered and managed * **DNS Propagation:** How long it takes for DNS changes to spread (15 min to 48 hours) * **Subdomain:** The part before your domain (like "portal" in portal.your-company.com) * **SSL Certificate:** What makes the connection secure (the padlock in the browser) * **TTL:** How long DNS info is cached before refreshing --- # 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/documentation/equipme-pro/setting-up-your-custom-url.md?ask= ``` 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.