The Rx Spot user roles and permissions

The Rx Spot roles: three surfaces, three user types

The Rx Spot's B2B telehealth operations platform has three distinct surfaces, each serving a different user type. The patient-facing Storefront is experienced by patients and managed by the operator. The Marketplace Dashboard is the operator cockpit — catalog, pricing, storefront config, and earnings — for owners and business managers. The Staff / Ops Portal is the back-of-house surface for clinical ops teams handling order fulfillment, patient records, provider workflow, and the audit trail. The Rx Spot does not publish a formal role-permission matrix on its public site; confirm the exact permissions per role during onboarding.

This page explains how The Rx Spot's three surfaces map to different user roles, what each surface gives access to, and how Fizy Health handles role-based provisioning in one platform.

Proudly Partnered With

How roles map to surfaces

Each surface has a distinct user. Permissions follow the surface.

The Rx Spot's design separates operator work from clinical ops work by giving each a dedicated portal. Understanding which surface a team member belongs in is more important than a permission checklist — because a user in the wrong portal will not find the actions they need regardless of their role.

What you need first

  • Operator / Owner — Marketplace DashboardOwners and business operators access the Marketplace Dashboard to publish catalog items, set tiered and volume-based retail pricing, configure storefront publishing workflows, and monitor platform earnings and reconciliation. This is the business management surface — not where clinical orders are placed or tracked.
  • Clinical Ops / Provider — Staff / Ops PortalPrescribers and clinical operations staff access the Staff / Ops Portal for the order fulfillment queue, patient and business records, provider workflow coordination, and the audit trail across surfaces. This is where active ordering and patient management happen — not where pricing is set.
  • Patient — Storefront (no backend login)Patients interact with the white-label storefront on the operator's custom domain: catalog, intake, provider review, checkout, and branded communications. Patients do not have a backend login to the Marketplace Dashboard or Staff portal — they are the end customer, not a platform user.

How access works

  1. 01
    Identify which surface each team member belongs inOwners and business managers → Marketplace Dashboard. Prescribers, coordinators, and clinical ops → Staff / Ops Portal. Patients → patient-facing Storefront (no backend login needed).
  2. 02
    Provision the operator account firstThe operator-level Marketplace Dashboard account is the root account. All other access — Staff portal invitations, storefront configuration — flows from the operator account. Set up the operator account during onboarding before inviting the clinical team.
  3. 03
    Invite clinical ops to the Staff portalOnce the operator account is set up, the operator invites prescribers and clinical staff to the Staff / Ops Portal. Each team member gets individual credentials for that surface.
  4. 04
    Confirm permissions per role with The Rx SpotThe Rx Spot does not publish a formal permissions matrix. Ask during the platform demo which specific actions (e.g., approving orders, editing patient records, viewing earnings) each role can perform in each portal.

Common access issues

  • Prescriber provisioned to the Marketplace Dashboard

    A prescriber provisioned as an operator will see catalog and pricing controls instead of the fulfillment queue and patient records. Role and surface must match — confirm which portal each team member is provisioned into.

  • No formal permission matrix for audit or compliance

    If your organization requires a documented permission matrix for HIPAA compliance or internal audit, The Rx Spot's lack of a public one means you will need to confirm and document permissions during onboarding rather than referencing a published spec.

Evaluating The Rx Spot roles — or comparing role-based provisioning?

The Rx Spot fits if

The Rx Spot

Distinct portal surfaces for operators and clinical ops teams.

  • Your organization has a clear separation between business operators (who set pricing and manage storefronts) and clinical ops teams (who work fulfillment queues and patient records).
  • A two-portal model where business management and clinical work stay in separate surfaces fits your team structure.
  • You are launching a new telehealth brand and need a demo-led storefront setup rather than same-day clinic batch checkout.
Consider Fizy Health if

Fizy Health

One platform, role-based access — no surface routing required.

  • You want prescribers, staff, and admins to access the same platform with different permissions scoped by role — not split across separate portals.
  • You want NPI and DEA validated per prescriber at self-serve signup so role-based provisioning is built into onboarding, not a separate step.
  • You want a documented access model with per-line HIPAA audit rather than a platform without a published permission matrix.
FAQ

What operators ask about The Rx Spot user roles and permissions.

  • Definition

    What user roles does The Rx Spot have?

    The Rx Spot does not publish a formal role-permission matrix. Based on its three platform surfaces, user types map to: operators and owners (Marketplace Dashboard), clinical ops and prescribers (Staff / Ops Portal), and patients (patient-facing Storefront, no backend login). Confirm the exact permission list per role during your onboarding.

  • Surfaces

    What can each surface access?

    Marketplace Dashboard: catalog publishing, tiered and volume-based pricing, storefront configuration, platform earnings and reconciliation. Staff / Ops Portal: order fulfillment queue, patient and business records, provider workflow coordination, audit trail. Patient Storefront: catalog, intake, checkout, branded communications — no backend login.

  • Prescribers

    Which surface do prescribers use on The Rx Spot?

    Prescribers and clinical ops teams use the Staff / Ops Portal for order fulfillment, provider workflow, patient records, and the audit trail. They do not use the Marketplace Dashboard, which is the business management surface for owners and operators.

  • Audit

    Does The Rx Spot have an audit trail for permissions and orders?

    The Rx Spot mentions an audit trail across surfaces as a feature of the Staff / Ops Portal. The scope of what is audited — which actions, which roles — is not detailed publicly. Confirm audit trail coverage during onboarding if HIPAA compliance is a requirement.

  • Admin

    Who is the admin on The Rx Spot?

    The operator-level Marketplace Dashboard account is the root admin. This account configures the storefront, sets pricing, and invites clinical ops team members to the Staff portal. The admin role is set at onboarding — confirm with The Rx Spot at join@therxspot.com how admin access is provisioned.

  • Alternative

    How does Fizy Health handle roles and permissions?

    Fizy Health provisions prescribers and staff with role-based access in one platform at self-serve signup. NPI and DEA are validated per prescriber at onboarding. All roles access the same platform — ordering, tracking, and team management — scoped by role without separate portals for clinical ops versus business management.

Sources reviewed June 2026

  • The Rx Spot public website, product pages, and FAQ (therxspot.com), reviewed June 2026.
  • Fizy Health platform capabilities reflect the live product.
Evaluate with real numbers

Role-based access in one platform. No surface routing required.

Fizy Health provisions prescribers and staff with NPI, DEA, and role-based access at self-serve signup. Per-line HIPAA audit from day one. Free to start.