# Administration Overview

{% hint style="info" %}
**Who is this for?** Engineering Managers, IT Administrators, and VPs of Engineering configuring team access, authentication, and enterprise security controls.
{% endhint %}

This section covers everything a ContextQA workspace administrator needs to configure and maintain the platform: user management, authentication, storage, backups, and system auditing.

***

## In This Section

| Page                                                            | What you'll learn                                         |
| --------------------------------------------------------------- | --------------------------------------------------------- |
| [Roles & Permissions](/administration/roles-and-permissions.md) | User roles, permission scopes, and access control         |
| [Team Management](/administration/team-management.md)           | Inviting users, managing seats, and organization settings |

***

## Settings Navigation

All administration settings are accessible under the **Settings** menu:

| Setting               | Route                             | Purpose                                          |
| --------------------- | --------------------------------- | ------------------------------------------------ |
| User Management       | `/settings/user-managemant`       | Invite users, assign roles, deactivate accounts  |
| Organization Settings | `/settings/organization_setting`  | Org name, logo, default preferences              |
| SSO / Authentication  | `/settings/auth`                  | SAML 2.0 and OAuth SSO configuration             |
| Storage               | `/settings/storage`               | File and artifact storage configuration          |
| Backups               | `/settings/backups`               | Backup schedules and restore points              |
| System Audit Logs     | `/settings/system-audits`         | Platform-wide activity audit trail               |
| Provisioning Profiles | `/settings/provisioning_profiles` | iOS code signing certificates for mobile testing |

***

## Key Administrative Tasks

### Inviting a new user

1. Go to **Settings → User Management**.
2. Click **+ Invite User**.
3. Enter the user's email address and select their role.
4. Click **Send Invitation**.

The user receives an email with an activation link. They must activate within 7 days before the invitation expires.

### Configuring SSO

ContextQA supports SAML 2.0 for enterprise SSO with providers such as Okta, Azure Active Directory, and Google Workspace.

1. Go to **Settings → Authentication**.
2. Enter your IdP metadata URL or upload the XML metadata file.
3. Configure attribute mappings (email, first name, last name).
4. Enable SSO and test with a single user before rolling out to the team.

See your IdP documentation for the ContextQA entity ID and ACS URL needed to complete the IdP-side configuration.

### Reviewing audit logs

The system audit log records all significant platform events: user logins, permission changes, test case creation/deletion, integration configuration changes, and API key generation.

1. Go to **Settings → System Audits**.
2. Filter by user, event type, or date range.
3. Export to CSV for compliance reporting.

***

## Related Pages

* [Team Management](/administration/team-management.md)
* [Roles & Permissions](/administration/roles-and-permissions.md)
* [Integrations Overview](/integrations/integrations.md)

{% hint style="info" %}
**Enterprise-ready: SSO, RBAC, and centralized access management.** [**Book an Enterprise Demo →**](https://contextqa.com/book-a-demo/) — Get a walkthrough of enterprise controls, SSO setup, and compliance features for your organization.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://learning.contextqa.com/administration/administration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.