Guide

Invite a partner agency

Program administrators who are adding a new partner agency to the network

Who can do this

Only administrators add a partner

Program administrators and supervisors with admin access add and verify agencies. Staff get the minimum access their role needs. Partner staff get referral access only for their agency.

  • Multifactor sign-in is required for staff and administrators
  • Deactivation takes effect at once and past entries stay attributed
  • Every add, verify, invite, and status change is logged with no survivor detail in the log entry
Steps

Add, verify, publish, and invite

Do the steps in order. The agency cannot receive referrals until verification is done.

  1. Add the agency

    Enter the legal name, service types, counties, and contact route. The record starts as pending. A pending agency cannot receive referrals.

  2. Verify the agency

    Check the agency details against the record you have on file, then set verification to verified. Suspending an agency later does not delete history.

  3. Publish its services

    Publish service types, hours, and languages. Supported languages and interpreter access are stated before a visit, with separate costs identified by the program.

  4. Invite its staff

    Invite each staff member by work email, set the partner role, and confirm multifactor setup. Invite links carry no survivor detail.

  5. Set backup coverage

    Name a backup staff member or coverage team and the response time. When the primary contact is unavailable, routing can move by rule or by hand.

  6. Run a test referral

    Send one test referral with current consent, confirm the partner can accept it, then mark the test record so it is excluded from grant counts.

Scope

What a partner can and cannot see

Scope is enforced on the server for lists, detail, and exports. Hidden buttons are not a control.

  • Can see: only referrals sent to that agency, with status from sent to closed
  • Can do: accept, decline with a reason, or request more information
  • Can record: first connection date, handoff steps, and follow-up
  • Cannot see: referrals sent to another agency, full case records, or notes and messages for other cases
Illustration of a partner inbox with referral cards for one agency
Referral flow

How referrals move after the invite

Send is blocked when consent is missing, expired, revoked, or does not cover that agency and those data types. Status changes are new dated entries. A referral is closed and never deleted.

Sending side

Only the sending advocate or supervisor marks connected and closed. Sent is never counted as a service connection.

Receiving side

Only the receiving partner moves sent to received, accepted, declined, or needs information.

Warm handoff

Record first connection date, handoff steps, and follow-up, then close with an outcome.

Test records are flagged as test and excluded from grant counts. Demonstration alone is not acceptance. The program records written approval before live use.

Test before live use

Run a test referral with current consent and confirm the partner inbox shows only that test referral.

Send a referral guide
Related guides

Read next

Guides the partner and the sending team use together.

Send a referral

Check consent first, choose the partner and scope, send, and track to closure.

Read the guide

Check consent

View scope and expiry, confirm the agency, and record a revocation.

Read the guide

For partner agencies

How an agency receives, accepts, and tracks referrals addressed to it.

Read the page