Settings
The Settings area of the Satori console is where you manage access and instance-wide configuration: console users and their permissions, API and server keys, general settings, and the audit log. Most of these actions require elevated permissions. This guide goes into more detail about the different settings you can configure from the dashboard.
Users #
Create new users, manage fine-grained permissions for each user, reset user passwords and multi-factor authentication (MFA), and delete users.
When creating a user, select from the following role archetypes:
| Role | Description |
|---|---|
| Admin | Full read/write/delete permissions for all entities. |
| Debugger | Read/Write permissions for all entities except users. |
| Developer | Full read/write/delete permissions for all entities except users. Can’t delete server keys. |
| Game Designer | Full read/write/delete permissions for all entities except users, API keys, and server keys. |
| Support | Read only access to core data entities (e.g. audience, identity, flag, etc.). |
Edit user #
Edit fine-grained permissions for an individual user from the console.
These permissions also affect what each user can see on the analytics dashboard.
General #
General settings control the view and behavior of the console, such as choosing the displayed timezone for all users.
API keys #
Create and manage API keys to interact with the Satori Client API. From the console, you can also rotate and delete keys.
Server keys #
Server Keys authenticate the Satori Console API, the management API used to configure and operate your instance programmatically from your backend or tooling. Each key has its own editable permissions and you can also rotate keys as needed.
Satori exposes two APIs, and each uses its own key:
- The Client API is the runtime API your game uses during play. Game clients and trusted servers call it to authenticate players, update properties, publish events (including server-side telemetry), and read the flags, experiments, live events, and messages assigned to a player. It authenticates with an API key.
- The Console API is the programmatic equivalent of the Satori console: the management API for your instance. Use it from your backend or tooling to manage flags, audiences, experiments, live events, message schedules, metrics, integrations, and more, and to send messages directly. It’s a privileged, server-side API authenticated with a Server key.
In short, use an API key for runtime and telemetry operations, and a Server key for managing your instance from a backend with fine-grained access control. A server sending server events, for example, uses an API key, since that’s a runtime operation.
Configuration #
The Configuration tab displays the current configurations for Satori, which you may also Export.
Audit log #
The Audit Log displays a log of all actions taken within your Satori instance, including user logins, data imports, and more. When selecting a log, a new view will open showing the before and after of the changes made.
Undo an action #
The Audit Log has a Undo button, which lets you rollback specific actions from the Log.
Upon selecting Undo, a new window will appear, showing a diff of the changes. Select Confirm to rollback the values to the ones shown on the left (before).
Undo is useful for correcting mistakes, such as restoring an accidentally deleted API key, recovering a removed flag variant, or reverting an audience that was changed with the wrong parameters.
Supported undo actions #
The following domains support undo actions:
| Domain | Description |
|---|---|
| API Key | Create/update/delete API credentials |
| Server Key | Manage server-side access tokens |
| Event Configuration | Event schema or handler modifications |
| Flag | Create/update/delete feature flags |
| Flag Variant | Manage variants of feature flags |
| Experiment | Modify experiment setups or status |
| Experiment Phase | Changes to phase timing or rules |
| Live Event | Edits to scheduled live events |
| Live Event Flag | Feature flag associations in live events |
| Live Event Flag Variant | Variants used in live event feature flags |
| Live Event Message Schedule | Message scheduling in live events |
| Template | Modifications to reusable templates |
| Message Schedule | Changes to message delivery plans |
| Audience | Create/update/delete audience segments |
| Schema | Database or event schema changes |
| Category | Reorganization of tagging or classification systems |
| Metric | Metric definitions for dashboards and reports |
| Datalake | Configurations related to external datalake connections |
| Advertisement Measurement Partner Integration | Edits to third-party ad partner integrations |
| Webhook | Create/update/delete webhook endpoints |
| User | Admin-level user creation or permission changes |
| Property Configuration | Updates to app/environment-specific settings |
| Setting | General settings across the workspace |
| Data Management | Data privacy or retention configurations |
