> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/workspace-management/accounts.md). # Accounts Formsort Accounts are tied to a specific business entity. ## Inviting new users to Formsort If you would like to add more accounts to your organization, you can do so by going into the **Accounts** tab once you've logged into the Formsort studio. Any user can invite co-workers. However, a user can only assign a new account the same or fewer [permissions](/workspace-management/accounts/roles-and-permissions.md) than themselves. {% hint style="info" %} If your organization has set up a security policy within Formsort, accounts may be restricted to emails tied to your whitelisted domains. {% endhint %} ## Seeing active Formsort account Please email to get an active list of accounts. ## Deleting Formsort accounts If you are a workspace admin, you can delete accounts from the **Accounts > View accounts** table. --- # 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://docs.formsort.com/workspace-management/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.