Vanilla Medplum, single-location derm clinic: one project, three apps — Medplum App for admin, the reference Provider app for staff, a patient app. Clinicians and patients work fine; we're adding front desk, MA and biller. What we've pieced together: a role is an AccessPolicy on ProjectMembership (no role resource), staff are Practitioners, the default policy from projectinit.ts is too broad so every invite names one, one clinic so no criteria, tools are readonly/interaction/readonlyFields/writeConstraint. Queues: Task.performerType + SNOMED Care Team Member Function. What we couldn't find: the Provider app doesn't vary by role (nav fixed in App.tsx; only switches are billing and DoseSpot/ScriptSure), nothing gives a role queue (sidebar Tasks hardcoded to owner=signed-in user, page offers only My/All Tasks), and no reference AccessPolicies for these roles anywhere. 1. Is the Provider app the intended home for front desk, MA and billing? A front desk user currently gets the full clinical menu, with screens that error or come back empty. Is role-aware nav on the roadmap, or do people fork here? 2. Who should use the Medplum App in a single-clinic project — the practice admin inviting staff, or only the technical team? If the former, admin: true plus a narrower clinical policy? 3. One AccessPolicy per role on ProjectMembership, or a shared base policy plus one per role? 4. Any reference policy set or permission matrix for provider/front desk/MA/biller? Even an informal one from another customer would help. 5. How do you handle someone covering two roles (an MA who also works front desk) — combined policy, both attached, or separate logins? 6. How should a role queue work in the vanilla Provider app — performerType and filter All Tasks, or a shared owner (Practitioner/front-desk) like the post-intake example? And is 224608005 the code you'd use? The receptionist concepts (159561009, 56551004, 159562002) aren't in it.

Keshav - this is generally business logic, and Medplum is agnostic on how to approach these, as different organizations have different functional roles. The way to think about it is which key workflows will front desk play a role in? We see a wide variety and there is no "one size" model. 1. Scheduling? 2. Revenue cycle related (insurance verification, billing related tasks, collection of payments) 3. Medications related workflows? 4. Labs/diagnostics related workflows? 5. Messaging responses/inbox? 6. Fax inbox management? Once the design is in place the AccessPolicies are derived from the design. One AccessPolicy per ProjectMembership is the right approach