Update from support feedback: custom domain claimed by another org - #6914
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
ethanpalm
reviewed
Aug 8, 2026
ethanpalm
approved these changes
Aug 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Support has been fielding tickets where customers hit
Domain is already claimed by another organization(or the same-org variant) when adding a custom domain, because it is still bound to an inaccessible or orphaned Mintlify deployment. The custom domain page had no self-serve guidance for this, so users had to open a ticket to make progress.Changes
customize/custom-domain.mdxcovering both dashboard-side errors, self-service release from the losing deployment, and how to request a release from support with proof of ownership.mint add-domainCLI reference so users hitting the failure from either surface land on the fix.Support context
Note
Low Risk
Documentation-only changes with no product, API, or security behavior changes.
Overview
Adds self-serve troubleshooting for when adding a custom domain fails because another Mintlify deployment or organization already holds it.
A new Help center page explains the two error strings (
Domain is already in use by another deployment in your organizationvsDomain is already claimed by another organization), how to release the domain from the holding deployment in the dashboard, and what to send support@mintlify.com when the org is inaccessible. Remove a custom domain now states that removal releases the domain for reuse.mint add-domainin the CLI reference and the custom domain guide link to that article so dashboard and CLI users hit the same fix path. The page is registered indocs.jsonunder the hidden, searchable Help center tab.Reviewed by Cursor Bugbot for commit a3adf35. Bugbot is set up for automated code reviews on this repo. Configure here.