Dashboard & Navigation

Published Date: May 1, 2026 | Last Updated: October 9, 2026

Overview

The Dashboard is the default landing page in Seasoft Identity and the recommended starting point for routine platform review. It provides a real-time summary of the platform's current state — surfacing failed operations, detected anomalies, and access activity that requires Administrator attention without requiring a full review of individual User records or integration logs.

Navigate to Dashboard in the left navigation to access it at any time.

What the Dashboard shows

The Dashboard aggregates activity and status information from across all connected integrations and User records. Key areas include:

Failed operations — provisioning or deprovisioning actions that did not complete successfully. Each entry identifies the affected User, the integration, and the nature of the failure. Select an entry to navigate to the full detail in Change History.
Anomalies — drift events and access discrepancies that have been flagged for review. These represent permission changes that occurred in a connected application outside of Seasoft Identity. Select an entry to navigate to the affected User record and resolve the anomaly.
Recent activity — a summary of recent provisioning operations across the platform, providing a quick view of what Seasoft Identity has executed.

Using the Dashboard for routine monitoring

The Dashboard is designed to answer one question at a glance: does anything require attention right now? The recommended monitoring practice is to review the Dashboard regularly — daily for active environments — and address any failed operations or anomalies before they accumulate.

A clean Dashboard indicates that all recent operations completed successfully and no drift has been detected across connected integrations. Any items surfaced on the Dashboard should be investigated and resolved before they are considered closed.

Responding to failed operations

A failed operation on the Dashboard means Seasoft Identity attempted a provisioning or deprovisioning action and did not succeed. Common causes include an integration that has lost authorization, a misconfigured permission in a Role Template, or a User record with missing required attributes.

To investigate: select the failed operation to open the full entry in Change History. Review the error detail, address the underlying cause, and retrigger the operation or resync the affected integration.

Responding to anomalies

An anomaly on the Dashboard indicates that a User's permissions changed in a connected application outside of Seasoft Identity — a drift event. Left unresolved, drift means the actual state of access in the connected application no longer matches what Seasoft Identity has configured.

To investigate: select the anomaly to navigate to the affected User record. Review the issue detail and resolve it by choosing whether to enforce the Seasoft Identity configuration or accept the change from the source application. See Monitoring: Drift Detection for full resolution steps.

Monitoring: Drift Detection — how drift is detected and how to resolve anomalies
Monitoring: Change History — full log of all platform operations
Managing Users — resolve access issues on User records