Skip to content
Prototype · fictional data & simulated workflows · not a live crisis service
Covenant House doveCovCareSeen. Heard. Helped.
Youth home ↗

Roles, responsibilities & connections

How CovCare works.

Every participant has a different path. Each proposed handoff has a decision-maker, a purpose and a privacy boundary.

Entry & authentication

Proposed verified privileged provisioning, independent approvals and MFA.

Access boundary

Only specifically authorized Trust functions and scoped audit evidence.

Unavailable: Self-approval, youth-table staff overrides and public privilege activation.

Governance and Security AdministratorProposed / fictional storyboard
01

STEP 1 OF 8

Verify privileged provisioning

Initial CHI bootstrap is out-of-band, never automatic.

What the participant sees

Role storyboard: verify privileged provisioning. This is not an operational queue.

What happens next

Continue to define scope after the stated approval.

Decision owner: Independent CHI authorities

Information shared

Verified privileged identity

Approval required

Two independent approvals, MFA and launch review

If something goes wrong

If two independent approvals, mfa and launch review is missing or invalid, stop this step. The responsible independent chi authorities would review an appropriate alternative; the prototype sends no escalation or notification.

Actual current functionality

These controls navigate public documentation only. Operational review, notification, assignment, finance and service fulfillment are not activated. Existing public practice remains separate. This step describes intended design, not a completed operational task.

1/8

Explore the CovCare Vision

Discover how CovCare could connect young people, Covenant House teams, supporters, and community partners through one coordinated network of support.