Organization Workspace and Domains

Every organization owns its connected Discord server, competitions, staff access, progression, and billing. It also includes a public competition hub that organizers can share directly. GotNext does not advertise the hub or its competitions on the organizer's behalf. A custom subdomain is optional.

Your managed address

Your included address uses the organization slug:

your-org.gotnext.gg

It is created and secured automatically. It remains available as a fallback even after a custom subdomain becomes primary.

Customize the organization site

Open Organization Settings to prepare the public site. The controls are split into three focused workspaces so an admin does not have to build a page from scratch:

The Organization website workspace begins with a recommended setup checklist. Complete it in any order. The site works with the platform defaults, so these steps improve clarity and identity rather than block publishing.

Theme, About, link, and visibility changes remain local to your browser until you choose Save public page. Saving those settings updates the public site. Use Preview current draft to review the unsaved appearance and the homepage builder's current row order. After saving, choose Preview public site to verify the exact page with live competition data.

Homepage structure has its own draft and publishing workflow. Open Homepage builder, arrange the rows, choose Save draft, and then choose Publish homepage when the draft is ready for visitors. The Organization website page shows whether the saved draft matches the published revision or has unpublished changes.

Spotlight and featured competitions

Select the Featured spotlight block in the Homepage Builder to choose what visitors see first:

• Automatic chooses the most relevant live or upcoming competition.
• Specific competition uses the ladder or tournament selected by the admin.
• Discovery intro shows the organization introduction and a link to browse competitions.
• A published news article can replace the competition, with the competition choice kept as its fallback.

To remove the spotlight completely, remove its block from the builder. When First featured tournament is selected, the spotlight uses the first item in Featured competitions. Reorder that list to change the fallback. The remaining featured tournaments appear as a supporting homepage list.

Homepage builder

The visual builder controls the complete homepage flow. Available sections include the featured spotlight, latest news, player teams, competition shortcuts, competition discovery, match center, active ladders, About, and community links.

Move sections between the Header and Body areas. Each row can use one column, equal columns, or a wider left or right column. Sections that support a result count let you choose how many items to show. The spotlight can lead with the automatic competition selection or one published news article.

Save draft keeps the work private. Publish homepage makes that saved draft live and creates a restorable revision. The publishing panel lists recent revisions and can restore one into the draft for review before publishing it again.

The About editor is for durable organization information. Publish announcements, results, and event updates from the News workspace instead. Visitor action links are intended for destinations such as Discord, tryouts, merchandise, donations, schedules, or rulebooks.

Custom-domain availability

The current GotNext organization subscription includes one self-serve custom domain. A free organization uses its included managed GotNext address. Legacy or operator-assigned plans can have different limits; the Custom domains workspace shows the organization's actual allowance.

The managed GotNext.gg address does not count against this limit. Existing active custom-domain claims remain available when an organization changes plans.

Choose a supported address

Self-serve setup supports a subdomain that you control. We recommend one of these patterns:

• play.example.com
• www.example.com
• events.example.com

Root or apex addresses such as example.com require operator-assisted setup. Connect a supported subdomain, then configure a redirect from the root at your registrar. Contact support if the organization must use an apex address.

Connect the subdomain

1. 1

   Add the subdomain

   Open Organization Settings, choose Custom domains, and enter the complete subdomain. You can paste an https:// URL. Only the hostname is saved.

2. 2

   Copy the ownership record

   Add the displayed TXT record in the DNS control panel at the company that manages the domain. Copy the Name and Value exactly as shown.

3. 3

   Copy the routing record

   Add the displayed CNAME record. It routes the selected subdomain to the organization site hosted by GotNext.gg.

4. 4

   Verify the setup

   Return to Custom domains and choose Verify setup. Automatic checks also run while the domain is pending.

5. 5

   Make it primary

   After both the domain and secure connection are active, choose Make primary. The managed address stays available and redirects visitors to the primary address.

DNS record tips

• Enter the record Name exactly as shown. Some providers automatically append the root domain.
• Leave the record unproxied or DNS-only if the provider offers a proxy switch, unless support gives different instructions.
• Remove conflicting A, AAAA, or CNAME records for the same subdomain before adding the routing record.
• DNS updates often appear within minutes, but provider caching can take longer.

Verification and status

A domain is ready for visitors only when the domain status and secure connection are both active. Do not remove the DNS records after activation.

Primary domain and redirects

Only one address is primary. Other active addresses redirect to it so shared links converge on one canonical site address. The managed address cannot be removed. If a primary custom domain is disabled, the site falls back to another active address.

Root-domain redirects are configured at your registrar, not in the GotNext.gg dashboard. Redirect example.com to the connected www.example.com or play.example.com address with a permanent redirect when your provider supports it.

Security and ownership

The TXT record proves control of the domain before it can route to an organization. Never reuse a verification value for another organization. A domain already claimed by another organization cannot be transferred automatically. Contact support so ownership can be checked safely.

Connecting a domain does not create a separate account system or grant new staff access. Visitors can browse the public competition hub on the custom address. When someone signs in, accepts an invitation, manages a team, updates a profile, or opens organization administration, GotNext.gg automatically continues that action on the organization's included your-org.gotnext.gg address. The page stays branded and scoped to the same organization.

This handoff means competitors never enter their GotNext.gg password on a customer-controlled domain. They still use one account across every organization. Platform-owned addresses may be approved for the complete signed-in experience without the handoff.

Remove a custom domain

Choose Disable on the domain card and confirm the address. Visitors stop reaching the organization at that hostname. Remove the related TXT and CNAME records from the DNS provider after the domain is disabled. The managed address and organization workspace remain available.

Troubleshooting

The TXT record is not found

Check whether the DNS provider appended the root domain twice. For example, entering _gotnext-verification.play.example.com in a zone that automatically appends example.com can create the wrong record. Use the provider's DNS lookup or record preview to confirm the final hostname.

The CNAME record conflicts with another record

A hostname generally cannot have a CNAME and another A, AAAA, or CNAME record at the same time. Remove or rename the conflicting record, then add the routing value shown in the dashboard.

DNS is active but HTTPS is pending

Certificate preparation starts after ownership and routing are visible. Keep the CNAME in place and retry verification after DNS propagation. Contact support if the secure connection reports a failed status or remains pending after the records are visible.

Setup failed before DNS instructions appeared

Disable the failed entry and add the subdomain again. If the provider fails a second time, contact support and include the organization name, hostname, and the technical details shown on the domain card.

Get help