> For the complete documentation index, see [llms.txt](https://learning.contextqa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.contextqa.com/administration-and-reference/administration.md).

# Administration Overview

Guide to managing users, roles, workspace settings, SSO configuration, storage, backups, and audit logs in ContextQA.

> **Documentation owner:** [Deep Barot](https://contextqa.com/academy/) · **Last updated:** October 22, 2026

{% 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 the user-facing controls a ContextQA workspace administrator uses to configure and maintain the platform: user management, authentication, storage, imports, billing and usage, licensing, and system auditing.

## Quick answer

ContextQA administration centralizes workspace access, roles, authentication, API tokens, organization defaults, storage, imports, provisioning profiles, licensing, and audit records under **Settings**. Administrators should use least-privilege roles, test authentication changes in a separate session, protect all displayed credentials, and confirm the visible result after every configuration change.

## Key takeaways

* ContextQA administration centralizes workspace access, roles, authentication, API tokens, organization defaults, storage, imports, provisioning profiles, licensing, and audit records under Settings.
* Use this four-screen tour to review the administrative surfaces for roles, team membership, audit activity, and organization settings.
* Go to Settings → User Management.

## Interactive demo: access and system governance

Use this four-screen tour to review the administrative surfaces for roles, team membership, audit activity, and organization settings. It shows where governance work happens without exposing a live workspace or credentials.

{% embed url="<https://app.storylane.io/share/qxtuxv9exime>" %}

### What to notice

* Roles define reusable access boundaries before users are assigned.
* User management and audit activity support accountable workspace operation.
* Organization settings centralize approved defaults that affect the team.

***

## In This Section

| Page                                                                                                                       | What you'll learn                                                                         |
| -------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| [Roles & Permissions](https://learning.contextqa.com/administration-and-reference/administration/roles-and-permissions.md) | User roles, permission scopes, and access control                                         |
| [Team Management](https://learning.contextqa.com/administration-and-reference/administration/team-management.md)           | Inviting users, managing seats, and organization settings                                 |
| [System Configuration](https://learning.contextqa.com/administration-and-reference/administration/system-configuration.md) | Organization defaults, AI behavior, viewports, storage, imports, and configuration safety |
| [API Tokens](https://learning.contextqa.com/administration-and-reference/administration/api-tokens.md)                     | Creating and managing scoped API tokens for scripts and integrations                      |
| [Billing & Usage](https://learning.contextqa.com/administration-and-reference/administration/billing-and-usage.md)         | Reviewing plans, credits, usage trends, and available Stripe billing actions              |
| [License Status and Expiry](https://learning.contextqa.com/administration-and-reference/administration/license-status.md)  | Reading the license badge and expiry banner on self-hosted deployments                    |

***

## 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                                                   |
| Authentication Configuration | `/settings/auth`                  | Available login modes and API credential management                                   |
| API Tokens                   | `/settings/api-tokens`            | Create and manage scoped API tokens for scripts and integrations                      |
| Billing & Usage              | `/settings/billing`               | Review the plan, credits, usage, and available billing actions in eligible workspaces |
| Storage                      | `/settings/storage`               | File and artifact storage configuration                                               |
| Imports and Exports          | `/settings/backups`               | View available packages and start an approved import                                  |
| System Audit Logs            | `/settings/system-audits`         | Platform-wide activity audit trail                                                    |
| Provisioning Profiles        | `/settings/provisioning_profiles` | iOS code signing certificates for mobile testing                                      |

![ContextQA Organization Setting page showing company information, execution defaults, AI configuration, notifications, and viewport navigation](https://4255556216-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKlyaXxb76z3Dn47TrZkU%2Fuploads%2Fgit-blob-5aaece880cd762d91b07ee289e0102a4f9fe7edb%2Fcontextqa-organization-settings.png?alt=media)

Use [System Configuration](https://learning.contextqa.com/administration-and-reference/administration/system-configuration.md) for a screenshot-backed walkthrough of the organization settings, AI defaults, storage providers, and imports/exports pages.

***

## Key Administrative Tasks

### Inviting a new user

1. Go to **Settings → User Management**.
2. Click **+ Invite User**.
3. Enter the user's name and email address, optionally add a phone number, and select a role.
4. Click **Save**.

The invitation dialog does not ask an administrator to create or share the user's password. Authentication is governed separately under **Settings → Authentication Configuration**.

### Configuring SSO

The observed Authentication Configuration page offers **No Auth**, **User Name and Password**, and **Google SSO**. Available enterprise identity-provider options can vary by deployment or subscription.

1. Go to **Settings → Authentication Configuration**.
2. Review the enabled login method and open **View Details** for the intended option.
3. Test a new method in a separate private browser session before disabling the known-good method.
4. Confirm that the test user receives the correct role and workspace access.

See [Authentication and SSO](https://learning.contextqa.com/administration-and-reference/administration/sso-and-authentication.md) for the safe-change procedure and API credential guidance.

### Reviewing audit logs

The System Audits page presents recorded platform activity in a read-only table with **Date**, **Module & ID**, and **Details** columns.

1. Go to **Settings → System Audits**.
2. Use the filter control to narrow the visible entries when available.
3. Open the relevant record and preserve approved evidence according to your organization's retention process.

## Frequently asked questions

<details>

<summary>Where is user management in ContextQA?</summary>

Open **Settings → User Management**. From there, an authorized administrator can invite users, select roles, and manage account access. Available actions depend on the current user's permissions and deployment.

</details>

<details>

<summary>What is the difference between a role and a user assignment?</summary>

A role defines a reusable set of permissions. A user assignment connects a person to one of those roles. Design the least-privilege role first, then assign it to the appropriate users rather than configuring access ad hoc.

</details>

<details>

<summary>Where are organization and system defaults configured?</summary>

Use **Settings → Organization Settings** for the user-facing organization, execution, AI, notification, viewport, storage, and import settings exposed by the current deployment. See [System Configuration](https://learning.contextqa.com/administration-and-reference/administration/system-configuration.md) for the screenshot-backed guide.

</details>

<details>

<summary>How should I change authentication without locking everyone out?</summary>

Keep an existing administrator session open, apply the intended method, and test it in a separate private browser session with a non-owner account. Confirm role and workspace access before disabling the known-good method.

</details>

<details>

<summary>Are API tokens the same as a user's interactive login?</summary>

No. API tokens are scoped credentials for approved scripts and integrations. Use the minimum required scopes and expiry, copy the value only through an approved secret workflow, and revoke it when it is no longer needed. See [API Tokens](https://learning.contextqa.com/administration-and-reference/administration/api-tokens.md).

</details>

<details>

<summary>Who can see Billing &#x26; Usage?</summary>

The page is currently available to super administrators in eligible workspaces. See [Billing & Usage](https://learning.contextqa.com/administration-and-reference/administration/billing-and-usage.md) for plan, credit, Stripe, and usage guidance.

</details>

***

## Related Pages

* [Team Management](https://learning.contextqa.com/administration-and-reference/administration/team-management.md)
* [Roles & Permissions](https://learning.contextqa.com/administration-and-reference/administration/roles-and-permissions.md)
* [Billing & Usage](https://learning.contextqa.com/administration-and-reference/administration/billing-and-usage.md)
* [Integrations Overview](https://learning.contextqa.com/integrations-and-developer-tools/integrations.md)

{% hint style="info" %}
**Enterprise-ready: SSO, RBAC, and centralized access management.** [**Book an Enterprise Demo →**](https://contextqa.com/book-a-demo/?utm_source=learning.contextqa.com\&utm_medium=referral\&utm_campaign=docs_demand_gen\&utm_content=administration_overview) — Get a walkthrough of enterprise controls, SSO setup, and compliance features for your organization.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learning.contextqa.com/administration-and-reference/administration.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.
