> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/panel-settings/settings/administration.md). # Administration Manage the application, panel access and team structure in Administration: general settings, users, roles and permissions, business units and test devices. **Path:** `Settings > Administration` Use this section to manage application settings, access control, organizational structure, and testing setup.

### What you can manage Use **Administration** to configure your application, control user access, organize teams, and prepare test environments before launch.

What you can manage	Open
Configure application-level settings such as messaging, authentication, language, and uninstall tracking.	General settings
Invite users, update their details, and assign the roles they need.	Panel users
Create roles and define what each user can view, edit, or manage.	Roles and permissions
Organize users and campaigns into separate business units with their own targeting criteria.	Business units
Add and manage tester entries before you send campaigns live.	Test devices

--- # 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://user.netmera.com/netmera-user-guide/panel-settings/settings/administration.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.