Skip to content

Same agent Smaller bill. The tools and infrastructure to get more work from your AI. Fewer tokens. Less compute. Lower cost.

docs: add screenshots for enterprise feature pages (#1701)

Aman Agarwal066e2c582c7e
diff --git a/docs/images/enterprise/alert-destinations.png b/docs/images/enterprise/alert-destinations.png
new file mode 100644
index 00000000..62d31f4b
Binary files /dev/null and b/docs/images/enterprise/alert-destinations.png differ
diff --git a/docs/images/enterprise/alerts.png b/docs/images/enterprise/alerts.png
new file mode 100644
index 00000000..d39068a7
Binary files /dev/null and b/docs/images/enterprise/alerts.png differ
diff --git a/docs/images/enterprise/api-key-access.png b/docs/images/enterprise/api-key-access.png
new file mode 100644
index 00000000..40e986ae
Binary files /dev/null and b/docs/images/enterprise/api-key-access.png differ
diff --git a/docs/images/enterprise/audit-log-detail.png b/docs/images/enterprise/audit-log-detail.png
new file mode 100644
index 00000000..b01e6ef9
Binary files /dev/null and b/docs/images/enterprise/audit-log-detail.png differ
diff --git a/docs/images/enterprise/audit-logs.png b/docs/images/enterprise/audit-logs.png
new file mode 100644
index 00000000..0fc54142
Binary files /dev/null and b/docs/images/enterprise/audit-logs.png differ
diff --git a/docs/images/enterprise/connectors-datadog.png b/docs/images/enterprise/connectors-datadog.png
new file mode 100644
index 00000000..0baf7e6c
Binary files /dev/null and b/docs/images/enterprise/connectors-datadog.png differ
diff --git a/docs/images/enterprise/connectors-notification.png b/docs/images/enterprise/connectors-notification.png
new file mode 100644
index 00000000..e8ac2fda
Binary files /dev/null and b/docs/images/enterprise/connectors-notification.png differ
diff --git a/docs/images/enterprise/gpus-fleet.png b/docs/images/enterprise/gpus-fleet.png
new file mode 100644
index 00000000..61c921c3
Binary files /dev/null and b/docs/images/enterprise/gpus-fleet.png differ
diff --git a/docs/images/enterprise/gpus-overview.png b/docs/images/enterprise/gpus-overview.png
new file mode 100644
index 00000000..dd626ea6
Binary files /dev/null and b/docs/images/enterprise/gpus-overview.png differ
diff --git a/docs/images/enterprise/licensing.png b/docs/images/enterprise/licensing.png
new file mode 100644
index 00000000..fec77f8f
Binary files /dev/null and b/docs/images/enterprise/licensing.png differ
diff --git a/docs/images/enterprise/roles-role-groups.png b/docs/images/enterprise/roles-role-groups.png
new file mode 100644
index 00000000..198900a6
Binary files /dev/null and b/docs/images/enterprise/roles-role-groups.png differ
diff --git a/docs/images/enterprise/roles-user-permissions.png b/docs/images/enterprise/roles-user-permissions.png
new file mode 100644
index 00000000..a5bd7564
Binary files /dev/null and b/docs/images/enterprise/roles-user-permissions.png differ
diff --git a/docs/images/enterprise/roles-view-permissions.png b/docs/images/enterprise/roles-view-permissions.png
new file mode 100644
index 00000000..0a7165fa
Binary files /dev/null and b/docs/images/enterprise/roles-view-permissions.png differ
diff --git a/docs/latest/openlit/alerts.mdx b/docs/latest/openlit/alerts.mdx
index 97ac64e8..04e94bdf 100644
--- a/docs/latest/openlit/alerts.mdx
+++ b/docs/latest/openlit/alerts.mdx
@@ -13,6 +13,10 @@ Alerts notify your team when something important changes in OpenLIT, such as a m
Open **Alerts** from the sidebar under **Monitor** (`/alerts`). The page has three tabs: **Alerts**, **Events**, and **Destinations**.
+<Frame>
+ <img src="/images/enterprise/alerts.png" alt="Alerts page listing active alerts with their triggers, severity, and destinations" />
+</Frame>
+
<Note>
Alerts fire on changes made in OpenLIT, when they happen. They don't evaluate telemetry or metric thresholds such as latency or cost.
</Note>
@@ -56,6 +60,10 @@ With [RBAC](/latest/openlit/rbac), you can grant these to custom role groups.
</Step>
</Steps>
+<Frame>
+ <img src="/images/enterprise/alert-destinations.png" alt="Alert destinations page with Slack and Datadog destinations linked to alerts" />
+</Frame>
+
### Conditions
Conditions narrow when a trigger fires. Each trigger has its own condition groups:
diff --git a/docs/latest/openlit/audit-logs.mdx b/docs/latest/openlit/audit-logs.mdx
index 3f3f5e3a..c1f16ac0 100644
--- a/docs/latest/openlit/audit-logs.mdx
+++ b/docs/latest/openlit/audit-logs.mdx
@@ -26,6 +26,10 @@ Viewing audit logs needs the `audit_logs:read` permission. **Owner** and **Admin
## Browse audit logs
+<Frame>
+ <img src="/images/enterprise/audit-logs.png" alt="Audit Logs page with an hourly volume chart and a list of recent events" />
+</Frame>
+
The page shows:
- **Recent volume**: a bar chart of events per hour for the entries on the current page.
@@ -52,6 +56,10 @@ Each list shows values found in the selected time range. Select **Apply filters*
Select an event to open its details. The panel shows the target, the actor, project, and database config by name where possible, the time, and a **Metadata** section with everything captured for the event: the request path and parameters, the request and response bodies, the status, the client user agent, and IP address.
+<Frame>
+ <img src="/images/enterprise/audit-log-detail.png" alt="Audit event detail for a member role change, with the actor, project, and metadata" />
+</Frame>
+
<Note>
Sensitive values are redacted before they're stored. Any field whose name looks like a password, secret, token, API key, license key, authorization header, cookie, session, or secret value is saved as `[REDACTED]`.
</Note>
diff --git a/docs/latest/openlit/connectors/datasource.mdx b/docs/latest/openlit/connectors/datasource.mdx
index 1bd49948..7feb481a 100644
--- a/docs/latest/openlit/connectors/datasource.mdx
+++ b/docs/latest/openlit/connectors/datasource.mdx
@@ -86,6 +86,10 @@ Prometheus-compatible APIs (for example Grafana Mimir's PromQL endpoint) use the
Add them from **Connectors** like any other data source, then bind them per signal in [signal routing](/latest/openlit/organisation/signal-routing). A bound connector must be in the same environment as the binding.
+<Frame>
+ <img src="/images/enterprise/connectors-datadog.png" alt="Connector catalog filtered to Datadog, showing the premium data source and the premium notification connector" />
+</Frame>
+
### Datadog
| Field | Required | Description |
diff --git a/docs/latest/openlit/connectors/notification.mdx b/docs/latest/openlit/connectors/notification.mdx
index 29e7bf4a..35db95f2 100644
--- a/docs/latest/openlit/connectors/notification.mdx
+++ b/docs/latest/openlit/connectors/notification.mdx
@@ -20,6 +20,10 @@ Without the license, the connector catalog shows these types with a **Premium**
## Add a notification connector
+<Frame>
+ <img src="/images/enterprise/connectors-notification.png" alt="Notification connector catalog with Slack, email, PagerDuty, and Opsgenie marked Premium" />
+</Frame>
+
You can add a notification connector in either place; both create the same connector and alert destination:
- **Connectors** (`/connectors`): find the type in the **Notification** group of the catalog and select **Add connector**.
diff --git a/docs/latest/openlit/enterprise.mdx b/docs/latest/openlit/enterprise.mdx
index 45f605c4..618213a4 100644
--- a/docs/latest/openlit/enterprise.mdx
+++ b/docs/latest/openlit/enterprise.mdx
@@ -66,6 +66,10 @@ OpenLIT Enterprise is built from a private repository and unlocked with a licens
Enterprise features are licensed per organisation. A license lists the enterprise features it unlocks and is signed, so it can't be modified.
+<Frame>
+ <img src="/images/enterprise/licensing.png" alt="Organisation Licensing tab with an active enterprise license and the features it unlocks" />
+</Frame>
+
<Steps>
<Step title="Run the enterprise build">
Deploy OpenLIT Enterprise in place of the community edition. Your existing organisations, projects, and data carry over.
diff --git a/docs/latest/openlit/gpus.mdx b/docs/latest/openlit/gpus.mdx
index 0610e95d..d9f811cf 100644
--- a/docs/latest/openlit/gpus.mdx
+++ b/docs/latest/openlit/gpus.mdx
@@ -28,6 +28,14 @@ The GPUs page is part of the [OpenLIT Enterprise](/latest/openlit/enterprise) bu
Use the filters to narrow by **GPU**, **Region**, **Device**, **Cluster**, and **Provider**, and the time picker to change the range. Select a device in a table to open its own view at `/gpus/<device-id>`.
+<Frame>
+ <img src="/images/enterprise/gpus-overview.png" alt="GPUs overview with fleet size, hosts, devices, and allocation" />
+</Frame>
+
+<Frame>
+ <img src="/images/enterprise/gpus-fleet.png" alt="GPUs Fleet tab showing the busiest devices by utilization and memory" />
+</Frame>
+
| Tab | What it shows |
| --- | --- |
| **Overview** | Your fleet at a glance: total, active, and effectively used GPUs, clusters, hosts, and devices; GPU allocation and cloud cost meters; average utilization, memory, power, and temperature, max temperature, and throttled GPUs; utilization, temperature, and power over time; allocation over time; instance type mix; and a breakdown by GPU model. |
diff --git a/docs/latest/openlit/rbac.mdx b/docs/latest/openlit/rbac.mdx
index 2174941f..6d0b0841 100644
--- a/docs/latest/openlit/rbac.mdx
+++ b/docs/latest/openlit/rbac.mdx
@@ -68,6 +68,10 @@ With the RBAC entitlement, each API key can be restricted to specific features f
- **Full access**: the key can use every feature that accepts API keys. All keys created before this feature, and every key in the community edition, have full access.
- **Restricted**: the key can only use the selected features.
+<Frame>
+ <img src="/images/enterprise/api-key-access.png" alt="Create API key dialog with Restricted selected and per-feature access checkboxes" />
+</Frame>
+
| Feature | What it unlocks | Permission needed to grant it |
| --- | --- | --- |
| Telemetry ingestion | Sending traces, metrics and logs over OTLP | `api_key:create` |
@@ -92,6 +96,10 @@ With the RBAC entitlement, each API key can be restricted to specific features f
Open the RBAC management page from **Roles** in the sidebar.
+<Frame>
+ <img src="/images/enterprise/roles-user-permissions.png" alt="Roles page on the User permissions tab, with members assigned Owner or Member" />
+</Frame>
+
The page has two tabs:
- **User permissions**: Assign built-in roles or custom role groups to members, and optionally set direct permissions for a specific user.
@@ -115,6 +123,10 @@ Role groups are reusable custom permission sets.
Use role groups when multiple users need the same access profile, such as support, security reviewer, billing admin, or read-only operator.
+<Frame>
+ <img src="/images/enterprise/roles-role-groups.png" alt="Role Group tab listing the default Admin, Member, and Owner roles" />
+</Frame>
+
From **Roles → Role Group**, you can:
- Create a role group with a name, optional description, and selected permissions.
@@ -124,6 +136,10 @@ From **Roles → Role Group**, you can:
The permission view and assignment modals group permissions by area, feature, and action so reviewers can scan what a role grants before assigning it.
+<Frame>
+ <img src="/images/enterprise/roles-view-permissions.png" alt="Admin permissions dialog grouped by organisation, RBAC and billing, and product features" />
+</Frame>
+
## Direct user permissions
Direct user permissions override the member's assigned role group.