> For the complete documentation index, see [llms.txt](https://support.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.docstudio.com/admin-panel/users-and-user-roles/access-restrictions-unverified-domains-and-deleted-accounts.md). # Access Restrictions: Unverified Domains and Deleted Accounts This document explains how user access and admin capabilities change when a domain is unverified and what happens to corporate users if an account is deleted. ### If the domain is unverified If a domain becomes unverified, nothing changes for corporate users who already have access. They keep their current permissions and can continue working in the account and its mailboxes. The restriction applies to the account administrator. While the domain remains unverified, the administrator cannot create new corporate users for that domain or delete existing ones. ### If the account is deleted If an account is deleted, the corporate user loses access to that account and all of its mailboxes. They can no longer use anything that belongs to that account. At the same time, the user still remains a corporate user in the system. Because of that, they cannot create a new account or delete their own profile. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.docstudio.com/admin-panel/users-and-user-roles/access-restrictions-unverified-domains-and-deleted-accounts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.