Workspace access is invitation-first.
Unknown accounts are not placed into a customer workspace. When optional Google sign-in is enabled, it links to invited users by default.
Workspace security and governance
Know how access, evidence and exports are controlled.
StoreScoutAI is a login-protected workspace with role-aware access, source context on store records and authenticated export routes.
Discuss security requirementsOperating principles
Current controls in the product workspace.
These statements describe implemented product behaviour, not planned certifications or generic security promises.
Permissions follow the user's job.
Admin, analyst, sales representative and viewer roles separate user management, research, follow-up and read-only work.
Store access is customer and entitlement scoped.
Workspace routes check the signed-in user, customer context, role and record entitlement before returning protected data.
Downloads stay behind workspace authentication.
Prepared exports are served through protected routes, with access and release activity available for review.
Product boundaries
What your team stays in control of.
Follow how your team accesses store records, reviews evidence and chooses what to export.
- 01 Access
Signed-in team access, with roles that match the job.
- 02 Workspace
Stores, priority and evidence review in one commercial workspace.
- 03 Protected storage
Customer workspace data stays under access controls.
- 04 Reviewed export
The team chooses what leaves — export or HubSpot where enabled.
Access → Workspace → Protected storage → Reviewed export
Source and freshness context stays visible
Store records retain source, evidence-date and freshness information so an operator can distinguish current evidence from fields that need checking.
Customer-safe export rules are applied
The product applies field and source export policies before a record is included in a customer-facing file. Restricted source data is not treated as freely exportable.
Rankings support attention, not eligibility
Store Priority orders sales research using available evidence. It is not a legal, credit, compliance or fully automated eligibility decision.
RVM Decision remains a separate review
A Store Priority ranking does not establish that an RVM is operationally suitable. RVM Decision follows practical store evidence, survey input and team judgement.
Clear product boundaries
Decisions that stay with your team.
Official guidance and the retailer’s circumstances — not the product.
Ranking focuses attention; it does not guarantee a sale.
Site survey and practical review still decide RVM fit.
Evidence can go stale; teams refresh and check before acting.
Evaluate with the right people
Bring your security and data-flow questions into the plan review.
We will tailor the demo around how your team finds, researches and qualifies convenience stores today.