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
Control access, evidence and exports.
Your team signs in to access the workspace. User roles control permissions, sources stay visible and exports require authentication.
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.
Access stays within your workspace.
The workspace checks the user, customer, role and permission to view each record before showing protected data.
Downloads require authentication.
Prepared exports use protected routes. Access and export activity are 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
See sources and evidence dates
Store records retain source, evidence-date and freshness information so an operator can distinguish current evidence from fields that need checking.
Export rules protect restricted data
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 suitability remains a separate review
A Store Priority ranking does not establish that an RVM is operationally suitable. Site survey, store evidence and team judgement still decide machine fit.
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.
Review with your team
Discuss your security and data requirements.
Explore sample data yourself, or book a demo tailored to your team's territory and sales process.