Administration

Administration is where an instance owner manages provider connections, operational history, access policy, and release compatibility. Estate Scope is limited to deciding which discovered organizations, groups, and repositories are actively monitored.

Connections

The Connections list shows each GitHub App or GitLab token/instance separately: credential source, authentication type, status and capabilities, monitored scope, last discovery and billing synchronization, last safe error, and pending work. Open a connection to:

• reconcile it now and inspect visible workspaces and repositories;
• add or detach organizations and groups;
• monitor or ignore discovered scope;
• rotate stored credentials or reconnect a GitHub App;
• disable or history-preservingly disconnect it; and
• understand environment-provided credentials that the application cannot delete from the external secret source.

Discovery, billing, usage, credentials, and webhooks resolve the owning connection. Multiple connections for the same provider do not share an implicit “first” credential.

Operations

Operations separates enqueued, running, completed, and failed jobs. Each entry can include timestamps, duration, request use, pagination/checkpoints, connection and workspace scope, correlation ID, safe errors, and retry eligibility. Completed discovery records summarize additions, renames, moves, permission loss, removals, and no-change runs.

Only a complete successful discovery scope can transition unseen resources to inaccessible or removed. A failed or interrupted pass preserves the last known state.

Updates

Updates evaluates available immutable releases and application, database, target, controller, and provenance compatibility. In-app execution exists only where an administrator has configured a trusted external deployment controller with its own approval and safety gates. Other targets receive manual upgrade and rollback instructions.

Session policy

Owners and administrators can keep authenticated access valid until the browser session closes or select a fixed lifetime from five minutes through 365 days. The policy is audited and applies consistently across supported hosts. Explicit sign-out and disabling the identity provider still reject the session.