> For the complete documentation index, see [llms.txt](https://docs.mailtrap.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mailtrap.io/account-and-organization/management.md). # User Management & Organizations Manage users, teams, and organizational structure in Mailtrap. Control permissions, access, and collaboration. Efficiently manage your team's access to Mailtrap. Control permissions, organize users into teams, and maintain security across your organization. ## User Management Features


Organization & Sub-Accounts	Structure your Mailtrap account with organizations and sub-accounts for better resource management and billing separation.	Organization & Sub-Accounts
User Roles & Management	Add, remove, and manage team members. Control access levels and permissions for different users.	User Roles & User Management
User Profile	Manage individual user profiles, preferences, and settings within your organization.	User Profile
My Profile	Personal profile management including account settings, notifications, and security options.	My Profile
SSO Guide	Learn how to configure SAML 2.0 single sign-on (SSO) with Mailtrap using any Identity Provider that supports the SAML 2.0 protocol.	SSO Guide

--- # 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.mailtrap.io/account-and-organization/management.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.