Atlas project production

Raptor SSO and Security Group Sync

Tracks the district safety-platform identity path for Raptor, with continuity-level production evidence and explicit validation debt.

Internal-only entry. Do not publish externally without review.

Type: System
Lifecycle: Active
Last touched: 2026-03-26
Visibility: Internal

Purpose

Synchronize district identity and security-group context into Raptor-related SSO or access structures.

Current state

The connector is inventory-confirmed and operationally important, but Atlas still lacks concrete implementation artifacts. Current posture should be treated as production continuity coverage with validation-needed runtime detail.

Next step

Document the IdP, group source, scheduler/event model, and real use cases before expanding this page into a richer runbook.

Interfaces

Inputs

district identity data
security-group context

Outputs

Raptor SSO or access-group state

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Contributes in this stage.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

District identity and approved security-group rules should govern access state.
Raptor is the downstream safety-system target.

Safe handling

Restrict safety-system access details and group membership data.
Keep SSO configuration and admin access internal.

Operational notes

Reliability posture

The business purpose is clear, but technical implementation and observability are still inventory-only validation debt.

Observability

Inventory-only evidence today; implementation-level logs are not yet documented.

Security and privacy

Confidential staff access and safety-platform data; internal only.

Dependencies

Upstream

identity provider
security-group definitions
Raptor configuration

Downstream

safety-platform access

Ownership

Owners

Technology Services

Users

Technology Services, district safety stakeholders

Raptor SSO and Security Group Sync

Operational Notes

The registry keeps this visible because safety-platform access is too important to leave as an undocumented inventory line.
Behavior classification: SSO and group-based access governance surface; account provisioning scope is not yet documented.
Current Atlas evidence is intentionally conservative and does not invent the technical path.
Failure or misconfiguration affects staff access to safety workflows.

Registry Alignment

Mapped registry entry: INT-048
Registry clarified: the connector is important enough to track now even though technical documentation remains thin.
Validation gaps: Document the IdP, group source, specific use cases, and operational ownership path.