Other Settings¶
This section contains configuration for various scenarios at the individual account level.
Workspace Management¶
For more details, see Manage Workspaces.
Personal API Key¶
A Personal API Key is an access credential bound to a user account. Its permissions remain consistent in real time with all functional permissions of that account on the platform (including dashboards, data queries, etc.). It is used to access OWL and MCP Server.
Free Plan workspaces also support Personal API Keys.
Differences from the workspace-level API Key
-
Personal API Key: Bound to a personal account; permissions take effect automatically following the account's permissions. Suitable for personal scripts or third-party platform integrations.
-
Workspace-level API Key: Bound to a workspace role; you must manually specify role permissions when creating it. Mainly used for service-to-service communication such as DataKit data reporting.
Click to open the window and copy the Personal API Key (❗️This key represents your personal identity; do not disclose it).
- Supports "Regenerate";
- Supports generating a "temporary authorization code", which can be temporarily exchanged for an API Key during auto-installation using the Owl CLI or AI tools. The code is valid for 30 minutes after generation and becomes invalid immediately after use.
System Notifications¶
After you subscribe to system notifications, the system triggers events in the following key scenarios and sends notifications to the subscriber's email address:
1. Alert Volume Approaching the Limit
When the number of monitoring targets of a monitor reaches {80%} of the system limit, the system sends an email notification (at most once per day). This might happen because the monitor aggregates on high-cardinality fields, causing the number of monitoring targets to keep growing. We recommend that you promptly review the query conditions and grouping settings. If the system limit {alert cache limit} is reached, the monitor is automatically paused.
2. Monitor Automatically Paused (Cache Limit Exceeded)
When the number of monitoring targets cached by a monitor reaches the system limit of {100,000}, the system automatically pauses the monitor and sends an email notification. While paused, the monitor stops running. To avoid continually generating too many monitoring targets and affecting system stability, check and adjust the query conditions and grouping settings. You can also modify and re-save the monitor to resume it immediately.
3. Monitor Automatically Paused (High-Cardinality Field Intercepted)
When the system detects high-cardinality risk in the grouping fields of a monitor's monitoring targets (for example, values longer than 32 characters appear in a field), it automatically pauses the monitor and sends an email notification. Such fields usually generate a large number of discrete groups, causing the number of monitoring targets to grow rapidly. Adjust the monitor's query and then retry.
Go to Monitoring > Notification Targets and click "Subscribe to System Notifications" to check whether any notification targets have failed to send or have been disabled by the system.
Or go to the create/edit page of a notification target and click "Subscribe to System Notifications".
Go to Manage > Cloud Account and click "Subscribe to System Notifications" to check whether the cloud account configuration is valid.
If data reported by a workspace triggers the configured upper limit, the system sends an email notification.
Once Obsy AI credits are exhausted, the system sends an email notification.
After clicking the "Subscribe" button above, the system automatically sends relevant notification emails to your mailbox when new messages are available.
After system notifications are triggered, you can view all notification events in the notification list and manage them with the following operations:
- Filter notification types by scenario type;
- Filter based on the notification title or content;
- View unread only;
- Mark all as read.



