> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/private-panels/organization-settings/user-management-and-permissions.md). # User management and permissions ## Users User membership in Private Panels is handled at the organizational level. The system is designed so each user has a single Private Panels account, which can then join one or more organizations. Each user should have their own account, where they can manage their personal preferences, including notification and security settings. ## Roles Member roles dictate access within an organization. ### Admin * Unrestricted access to the organization, its data, and settings. * Can add, modify, and delete panelists and studies. * A Private Panels organization can have more than one Admin. ### User * Can add, modify, and delete studies. * Can add, modify, panelists but can not bulk delete panelists or export the panel. * Can not add, modify, or delete Panel Properties (i.e. Date of Birth, Zip, etc). * Can invite users to the organization. ### View * View-only access to Private Panels. * Can not make any changes besides to their own user profile. ### Limited * Can only view panelists, with emails redacted. ## Global Permissions Find these on the **Settings General** page, and scroll down to **Permissions**. * **Only an Admin user role can pay incentives (default: disabled).** If you'd like to prevent non-admins (e.g. project manager, researcher, recruiter, designer) from paying incentives, turn on this permission. {% hint style="info" %} **Note:** Private Panels was previously managed outside of Dscout, so you may see a different logo and URL in some places. If you have any questions, contact . {% endhint %} --- # 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://help.dscout.com/private-panels/organization-settings/user-management-and-permissions.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.