> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/tech/en/serve/contacts/role-vs-contact.md). # Differences Between Roles and Contacts Internal members use roles (Role) to manage platform permissions, while external users are identified as contacts (Contact); see the user manual for a complete comparison MaiAgent has two types of people: **Members (Member)** log in to the MaiAgent admin console, and their permissions are determined by **Roles (Role)**. **Contacts (Contact)** are end users who converse with an Agent and do not need a MaiAgent account. Conversation history, custom attributes, knowledge query scope (`query_metadata`), and tool credentials are all associated with the contact. Use contacts when integrating external-facing services and roles when assigning internal platform permissions. Each uses its own mechanism. For definitions, a comparison, and guidance on choosing between them, see [Differences Between Roles and Contacts](https://docs.maiagent.ai/org/roles/contact-role-comparison) in the user manual. For contact API integration, see [Introduction to Contacts (Contact) and Integration](/tech/en/serve/contacts.md). For knowledge scope configuration, see [Knowledge Management Permissions (Query Metadata)](/tech/en/identity-and-access/zhi-shi-guan-li-quan-xian-query-metadata-cha-xun-yuan-zi-liao-zong-lan.md). --- # 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.maiagent.ai/tech/en/serve/contacts/role-vs-contact.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.