Invite a housing officer or support worker

Where to invite from

1. Open Support Cases in the left nav (Enterprise only).
2. Click the tenant's case.
3. Go to the Team tab.
4. Click + Invite a support worker.

The three participation modes

Per Decision 092, every collaborator falls into one of three modes. Pick the one that matches their role:

1. Full

The default for active case-workers. They become a full PropFlow user with magic-link access.

• Required fields: email, full name.
• Access: read + write on the tenant's welfare workspace. Notes (Shared), Goals, Sessions, Documents.
• Restrictions: cannot see Professional notes (operator-side only); cannot invite other collaborators.
• Login: receives a magic-link email; sign in at /login; lands at /support/tenants.

2. Context-only

For housing officers and supervisors who need visibility without case-work involvement. They're a PropFlow user but with a redacted, read-mostly view.

• Required fields: email, full name.
• Access: read on Goals, Shared notes, the tenant's context summary. Can record their own sessions.
• Restrictions: cannot write notes; cannot see Professional notes; cannot invite others.
• Login: receives a magic-link email; sign in; lands in a context-only case view at /support/cases/{id}.

3. Reference-only

For external contacts you need to record on the case but who don't get a PropFlow account. Examples: probation officer, family contact, GP, school SENCO.

• Required fields: contact name + (contact email OR contact phone). Optional: contact_organisation_name, contact_role_label.
• No invite sent — stored as a contact card only.
• Visibility: visible to your operator team in the Team tab. Not in any digest, not exported in HOM digests.
• Use when you need to record "here's the probation officer if anyone needs them" without creating a PropFlow account for them.

What gets created in PropFlow

For Full / Context-only invites:

• If the email doesn't yet exist on PropFlow: a Supabase auth user is created, a lightweight support_provider organisation is created as their identity container, and a tenant_collaborators row links them to this specific tenant.
• If the email exists already: a new tenant_collaborators row is added linking them to this tenant. They sign in with their existing credentials.
• The magic-link email goes out (Decision 019 invite flow).

For Reference-only:

• A tenant_collaborators row is added with participation = "reference_only" and the contact fields filled in.
• No auth user, no email sent.

The collaborator's experience (Full + Context-only)

1. Receives an email: "You've been invited to PropFlow as a support worker."
2. Clicks the magic link → signs in.
3. Lands on /support/tenants — their caseload across every tenant they're assigned to (potentially across multiple orgs).
4. Clicks a tenant to open the case detail.
5. Sees the welfare workspace scoped to what their participation mode allows.

Ending a collaborator's assignment

1. In the Team tab, find the collaborator.
2. Click End.
3. PropFlow sets ended_at on their tenant_collaborators row.
4. RLS removes their visibility immediately — they won't see this tenant in their caseload from the next page refresh.

Their historical contributions (notes, sessions) stay in the case with their authorship. Their account is unaffected — they still see other tenants they're assigned to.

Common gotchas

• Worker can't see the tenant after accepting the invite. Check the participation mode and the assignment date — Reference-only contacts don't get accounts at all. Full / Context-only need to have clicked the magic link.
• Worker can't write notes. Check their mode — Context-only is read-mostly (Sessions can be recorded; Notes cannot).
• Wrong participation mode picked. End the current assignment and re-invite with the right mode. Their historical contributions stay.
• Reference-only contact's details need updating. Edit the contact card on the Team tab. No invite re-sent (none was sent originally).

Next steps

• The per-tenant welfare workspace — what your collaborators see once they're in.
• Collaborate with an RSL — for the bigger picture of cross-org collaboration.