> For the complete documentation index, see [llms.txt](https://docs.aohwv.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aohwv.dev/administration/system-settings.md).

# System Settings

Review your license, monitor overall system health, and manage integration and display configuration for your AOH Sync instance.

![The System Settings screen showing the Maintenance tab. A License card displays the license type (standard), a License ID, active user count (1,531 of 19,999 entitled), max users (19,999), utilization percentage (8%), expiry (Never), and an Upload button. Below, an Event Health — 30 days chart shows 28% Success (17 events), 0% Failed (0 events), and 72% Info (43 events) across 60 total events. A System Overview section is visible at the bottom, showing a Service health card (All running), a Health check card (Passing), a Disk usage card (60% used), a Restart Service card for restarting individual containers, and an Update Images card for force re-pulling all container images.](/files/pVNFcDNWBXfhDoLeggGi)

*System Settings — Maintenance tab. The License card and Event Health chart give a quick read on capacity and operational health.*

## Tabs

| Tab              | What it shows                                                            |
| ---------------- | ------------------------------------------------------------------------ |
| **Maintenance**  | License details, event health over the last 30 days, and system overview |
| **Integrations** | Configuration for connected integrations                                 |
| **SSL**          | SSL certificate settings                                                 |
| **Branding**     | Display and branding customization                                       |

## Maintenance tab

### License

The License card shows:

* **License type** — for example, **standard**
* **License ID** — a unique identifier you can copy to share with support
* **Active users** — how many users are currently active against your entitlement
* **Max users** — the maximum number of users your license permits
* **Utilization** — the percentage of your licensed capacity in use
* **Expires** — the license expiry date (**Never** for perpetual licenses)
* **Features** — any additional licensed feature flags
* **Upload** — replace or update your license file

### Event Health — 30 days

This chart summarizes all sync events over the past 30 days across your organization:

| Category    | Meaning                                       |
| ----------- | --------------------------------------------- |
| **Success** | Events that completed without error           |
| **Failed**  | Events that encountered an error              |
| **Info**    | Informational events, such as skipped records |

The total event count and percentage breakdown are shown alongside a horizontal bar chart for quick visual reference.

### System Overview

The System Overview section below the Event Health chart displays real-time health indicators for key components of your instance. It includes the following cards:

| Card                | What it shows                                                                                          |
| ------------------- | ------------------------------------------------------------------------------------------------------ |
| **Service health**  | Status of each internal component — shows **All running** when everything is operational               |
| **Health check**    | Result of automated health checks — shows **Passing** when all checks succeed                          |
| **Disk usage**      | Current disk utilization on your instance (for example, 60% used)                                      |
| **Restart Service** | Lets you restart a single container — select the target from the dropdown and confirm                  |
| **Update Images**   | Forces a re-pull of all container images to their latest versions — click **Update Images** to trigger |

## How to use it

{% stepper %}
{% step %}
**Check license utilization**

Open **System Settings** and confirm the active user count is within your entitled limit. If utilization is approaching capacity, contact your account team before onboarding additional users.
{% endstep %}

{% step %}
**Copy your License ID for support requests**

Click **Copy** next to the License ID to copy it to your clipboard. Include it in any support request so the team can identify your instance quickly.
{% endstep %}

{% step %}
**Upload a new license**

If you have received an updated license file, click **Upload** in the License card and select the file. The new entitlements take effect immediately.
{% endstep %}
{% endstepper %}

## Related

* [Audit & Status Logs](/administration/audit-and-status-logs.md) — live operational status for your pipelines
* [User Management](/administration/user-management.md) — manage the users counted against your license
* [Getting Started — Managing Your Instance](/getting-started/11-managing-your-instance.md) — update and maintenance procedures for your AOH Sync instance


---

# 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://docs.aohwv.dev/administration/system-settings.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.
