> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/administration-control-plane/security-and-governance.md).

# Security and governance

Apply enterprise controls for authentication, authorization, auditability, and operating model design.

The Control Plane includes enterprise controls for authentication, authorization, and auditing.

Use this page to define a safe operating model for large teams.

### Authentication

Supported sign-in methods include:

* email and password
* SSO
* SAML
* OAuth

### Authorization

Role-based access is enforced at the:

* organization level
* application level
* project level
* infrastructure level

### Audit trail

Administrative actions are logged for review and compliance.

Common events include:

* user invitations
* role changes
* infrastructure assignments
* API key creation
* resource archival

### Recommended operating model

#### Structure resources clearly

Use a predictable hierarchy for ownership and reporting.

```
Organization
├── Application
│   ├── Project A
│   ├── Project B
│   └── Project C
└── Application
    ├── Project X
    └── Project Y
```

#### Limit admin access

Keep admin roles limited to governance owners.

Assign contributors at the project level.

Use member access for stakeholders who only need visibility.

#### Map infrastructure explicitly

Use shared pools for common testing.

Reserve dedicated devices for regulated or high-priority workloads.

Keep project mappings explicit for auditability.


---

# 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.mozark.ai/administration-control-plane/security-and-governance.md?ask=<question>&goal=<user_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.