> For the complete documentation index, see [llms.txt](https://docs.overleaf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overleaf.com/groups/overleaf-group-single-sign-on/domain-management/halting-domain-capture.md).
# Halting domain capture
Overleaf Pro group administrators can remove a domain in order to stop capturing users under that domain.
A removed domain will revert to the "Generate token" state. Overleaf will not attempt to verify these domains. If a domain should not be associated with your organization, please contact Overleaf Support, who can remove it from the domain management table.
When domain capture is inactive for a domain, users may register Overleaf accounts with emails under that domain without being directed to join the subscription of the organization that owns the domain. Members can still be directly invited to join the subscription when the domain is inactive.
If domain capture is re-activated for a domain, users who previously registered under that domain while it was inactive will be prompted to join the subscription and become managed on their next login to Overleaf.
---
# 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, and the optional `goal` query parameter:
```
GET https://docs.overleaf.com/groups/overleaf-group-single-sign-on/domain-management/halting-domain-capture.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.