First Steps (WIP)

This guide will walk you through some basic initial configuration of your SENSE Orchestrator deployment after it has made it through deployment and is finally online.

Prerequisites

• The SENSE Portal (SENSE-P) is reachable through the deployment’s configured Keycloak authentication.
• You have an account with the SYSTEM_ADMIN role.

Establish Deployment Settings

1. Login to the SENSE Portal.
2. Navigate to the Admin Settings page, using either the spotlight (/) or the top-left menu bar.
3. Review or set the Deployment Name. This is the value represented by global.deployment, and is used in the portal header and in system messaging.
4. Review or set the Deployment Host. This is the domain that the orchestrator is accessible at, such as sense.example.com. This is used primarily for references in system messaging or potential redirect suggestions.
5. Review the services you’d like to make available to users. This is represented by global.services.
6. Save your changes using the button below.

Review Secondary Settings

Logging Filters

The global settings panel also includes a section for logging filters. This allows operators to elevate or obfuscate logging from certain system packages, which can be invaluable for debugging error cases or tracing operations in greater detail. By default, the orchestrator starts with a handful of standard INFO levels that cover broad packages. You can add additional filters as needed with this panel.

Slack Agent (Optional)

If you want the deployment to use our pilot Slack notification agent, you can enable it here. You will need to supply the full webhook URL you established with Slack; for more information on creating Slack Apps, see the Slack documentation.

Treat the webhook as a sensitive configuration. This guide does not provide a webhook configuration or verification procedure.

Driver Initialization

TODO: Flesh out initial stub driver configuration.

Verify the Credential Store (Optional)

Before enabling a workflow that uses stored tokens, configure its runtime key, then:

1. Open Admin Settings → Credentials.
2. Confirm Store Active and the expected Key Version.
3. Check that any needed previous keys are LOADED, and resolve key or verification warnings using credential-store diagnostics.

An unavailable store affects participating workflows; normal portal access alone does not prove it is ready. To configure the current token consumer, see Configure an External Project Provider.

Download a baseline backup

1. Confirm that the intended configuration has been reviewed.
2. In Admin Settings → Backup & Restore, select Download Backup.
3. Store the resulting archive securely.

Archives may include credentials and must be handled as sensitive material. A downloaded archive is a configuration baseline, not disaster recovery. This step is separate from first-boot archive seeding; do not use it as that workflow.