> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gcore.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up Customer Portal product URLs

> Configure Gcore customer product URLs, subdomains, CDN resources, SSL certificates, DNS, and technical account for a reseller.

export const Caution = ({children}) => {
  return <div class="my-4 px-5 py-4 overflow-hidden rounded-2xl flex gap-3 border danger-admonition dark:danger-admonition">
      <div class="mt-0.5 w-4">
        <svg width="14" height="14" viewBox="0 0 14 14" fill="rgb(239, 68, 68)" xmlns="http://www.w3.org/2000/svg" class="w-4 h-4 text-sky-500" aria-label="Danger">
          <path fill-rule="evenodd" clip-rule="evenodd" d="M7 1.3C10.14 1.3 12.7 3.86 12.7 7C12.7 10.14 10.14 12.7 7 12.7C5.48908 12.6974 4.0408 12.096 2.97241 11.0276C1.90403 9.9592 1.30264 8.51092 1.3 7C1.3 3.86 3.86 1.3 7 1.3ZM7 0C3.14 0 0 3.14 0 7C0 10.86 3.14 14 7 14C10.86 14 14 10.86 14 7C14 3.14 10.86 0 7 0ZM8 3H6V8H8V3ZM8 9H6V11H8V9Z"></path>
        </svg>
      </div>
      <div class="text-sm prose min-w-0">
        {children}
      </div>
    </div>;
};

The customer's Customer Portal combines several Gcore products, each served from its own subdomain of a shared Base customer portal domain, configured on the [Vendor settings](/reseller-support/customer-portal/vendor-settings) page. Setting up a new reseller starts with choosing that domain and providing it to the Gcore account manager, who configures the products to use it.

## Product URL structure

Every product URL shares the same Base customer portal domain, for example `gcore.com`, with the product's subdomain added automatically:

* `auth.gcore.com`: authorization.
* `accounts.gcore.com`: customer account management.
* `cdn.gcore.com`: CDN product.
* `cloud.gcore.com`: Edge Cloud product.
* `streaming.gcore.com`: Video Streaming product.
* `storage.gcore.com`: Storage product.
* `waap.gcore.com`: Web Application and API Protection (WAAP) product.
* `dns.gcore.com`: Managed DNS product.
* `api.gcore.com`: API domain.
* `api.gcore.com/docs`: API documentation.

Single sign-on ([SSO](/reseller-support/security/authorization)) links these products together, so once a user logs in to the Customer Portal through the authorization service, the same session grants access to the other products automatically.

## CDN Resources and the technical account

A CDN Resource powers every product URL. Gcore creates these resources in the reseller's technical account: the first customer account in the Admin Portal, created automatically with an email address and company name matching the reseller's own. The technical account collects statistics for [monthly reports](/reseller-support/reports-and-activity/generate-monthly-reports) and lists every Admin Portal user, both Reseller and Sellers, but can't be deleted.

<Caution>
  Avoid making changes to the technical account or its CDN Resources, since unexpected changes can affect Customer Portal performance.
</Caution>

## SSL and DNS configuration

The Customer Portal works only over HTTPS, so each CDN Resource requires an SSL certificate, either one per resource or a single wildcard certificate covering the Base customer portal domain.

After Gcore configures the CDN Resources, the reseller adds one CNAME record per product URL to their DNS settings, pointed to a personal domain zone that Gcore provides. Once the CNAME records are in place, Gcore adds the Base customer portal domain to the matching field on the **Branding settings** page.