NDIS support coordinator platform

What support coordinators can do

• See participant relationships that have been explicitly delegated.
• Work with profile summaries, support needs, jobs, sessions, messages, notes or billing only when that area is authorised.
• Track open coordination tasks, evidence records and unread messages.
• Communicate with managed participants inside the correct relationship context.
• Request additional scoped access with a reason and expiry instead of relying on broad standing access.

How the experience should feel

The coordinator is a distinct actor, not a worker mode and not a substitute participant account. The Dashboard is compact and relationship-led. Each participant view makes visible, private and not-authorised areas unmistakable, so an unavailable control does not look like missing data or a system fault.

The interface should show whose decision is required, what scope has been granted and when that access ends. Participant preferences and permissions remain visible at the point where an action is attempted.

Permission boundaries

Shadowing a participant profile never transfers ownership. Messages, billing, private notes and My Manual fields may each have different permissions. Support access does not imply permission to inspect unrelated personal information. Every sensitive access request needs a named scope, purpose, participant decision and expiry.

A typical flow

1. Open a participant relationship that has been delegated.
2. Review the approved scope and current coordination tasks.
3. Act only within visible authorised areas.
4. Request a specific additional permission when genuinely needed.
5. Return control to the participant and let temporary access expire.

Current stage

The support-coordinator workspace demonstrates participant-controlled shadow relationships and scoped access concepts. Production authorisation, consent evidence, expiry enforcement and persistent audit workflows still require hardened identity and data services.