People & roles
A person’s role decides what they can run, approve, and see. The engine never sends; every list and every message goes out through a person.
What each role can do
Admin · sees everything
Starts runs, approves in any market, and assigns roles once Microsoft sign-in is live.
BD Rep · market-scoped
Reviews and approves every touch in their markets, exports the CSV, sends from HubSpot, and owns the replies.
Data owner · product-scoped
Drops the weekly files for their products, watches freshness, and can start runs. Cannot approve.
On this device
Nobody has picked a name on this device yet.
Decisions are logged as rep until someone does. Say who you are
Before Microsoft sign-in
Today, everyone chooses their own name and role on the sign-in page and the app trusts the choice: nothing is enforced, and the audit trail names whoever was picked. That still beats the alternative; without a name, every decision is logged as an anonymous “rep”. With Microsoft sign-in, people appear here automatically, an admin assigns each role, and the app enforces it. SSO + role assignment wired later