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 staff entry; public storyboard is not staff access.

Access boundary

Only assigned, consented support tasks after provisioning.

Unavailable: Unassigned youth, private reflections, donor financial detail or broad clinical records.

CHI NavigatorProposed / fictional storyboard
01

STEP 1 OF 8

Verify staff access

Establish verified provisioning and MFA before work.

What the participant sees

Role storyboard: verify staff access. This is not an operational queue.

What happens next

Continue to receive assignment after the stated approval.

Decision owner: CHI provisioning authority

Information shared

Verified staff identity

Approval required

Trust permission, MFA and launch review

If something goes wrong

If trust permission, mfa and launch review is missing or invalid, stop this step. The responsible chi provisioning authority 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.