> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/account-settings/users-security/user-roles.md). # User roles & permissions Roles & permissions in Kiflo allow you to comply with the *principle of least privilege,* one of the key concepts in terms of security. Kiflo offers built-in roles for users in your partnership team. Find on this page the description of each of those roles. **Owner** Owners can access all functionalities of Kiflo, manage the subscription, and remove all data. **Admin** Admins can configure Kiflo. They can configure the way you work with partners, define the onboarding pipelines, configure partner programs, and rewards, customize the partner portal, etc. They can access all functionalities, including the technical configuration (email domain, API access tokens, SSO, etc). They cannot manage the subscription nor remove all data. Example: top managers, or developers in charge of integrating Kiflo with your ecosystem. **User** Users can manage partners. They can create partners, and manage their leads & deals. They can publish news manage assets, etc. They cannot configure the way you work with partners (define onboarding pipelines, programs, rewards, etc). Examples: sales reps, partner managers **Viewer** Viewers are read-only users. They can access all data but the account settings. Examples: c-levels, managers --- # 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-vnext.kiflo.com/account-settings/users-security/user-roles.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.