> For the complete documentation index, see [llms.txt](https://mozarkdocs.gitbook.io/appx_documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mozarkdocs.gitbook.io/appx_documentation/administration-control-plane/frequently-asked-questions.md).

# Frequently asked questions

The Administration Control Plane gives enterprise teams one place to manage structure, access, infrastructure, integrations, and usage.

Use this page for quick answers during evaluation, onboarding, and rollout.

<details>

<summary>What is the Administration Control Plane?</summary>

It is the centralized admin workspace for Mozark Enterprise.

You use it to manage organizations, applications, projects, users, infrastructure, integrations, and plan usage from one place.

</details>

<details>

<summary>Who should use it?</summary>

It is designed for teams that need centralized control and clear governance.

Typical users include platform owners, IT administrators, QA leaders, and operations teams.

</details>

<details>

<summary>How is the hierarchy structured?</summary>

The model has three levels:

* organizations define business ownership
* applications group products under test
* projects isolate execution and collaboration

See [Organizations](/appx_documentation/administration-control-plane/organizations.md), [Applications](/appx_documentation/administration-control-plane/applications.md), and [Projects](/appx_documentation/administration-control-plane/projects.md).

</details>

<details>

<summary>How does access control work?</summary>

Access is controlled through roles and scoped assignments.

Admins manage invitations, roles, and access across the Control Plane.

See [User management and roles](/appx_documentation/administration-control-plane/user-management-and-roles.md) and [Security and governance](/appx_documentation/administration-control-plane/security-and-governance.md).

</details>

<details>

<summary>Do users get device access automatically?</summary>

No.

Device access is assigned explicitly through devices, pools, and project mappings.

This keeps shared test environments controlled and auditable.

See [Infrastructure](/appx_documentation/administration-control-plane/infrastructure.md).

</details>

<details>

<summary>Can it support multiple teams or business units?</summary>

Yes.

You can separate ownership at the organization level while keeping governance centralized.

This works well for multi-team and multi-organization environments.

</details>

<details>

<summary>Where do I track plan usage and limits?</summary>

Use [Dashboard and usage](/appx_documentation/administration-control-plane/dashboard-and-usage.md).

It shows subscription status, metered usage, and plan limits in one view.

</details>

<details>

<summary>Does it support integrations and API access?</summary>

Yes.

You can manage API keys, webhooks, identity connections, and external integrations from the Control Plane.

See [Integrations and API access](/appx_documentation/administration-control-plane/integrations-and-api-access.md).

</details>


---

# 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://mozarkdocs.gitbook.io/appx_documentation/administration-control-plane/frequently-asked-questions.md?ask=<question>&goal=<endgoal>
```

`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.