What this module is for
Surveys lets you publish a short survey, a rating request, or a policy agreement once, and have it appear inside ERPat for the people it targets — across every tenant on the installation. Answers come back to one place you can read, filter and export.
It replaces the old read-only App Rating report. That report could show you what people had already said through the mobile app. It had no way to ask anyone anything. This module keeps all of that reporting and adds the asking.
The one decision that matters
Every survey is either Optional or Required. That single setting changes everything about how it behaves, so it is worth understanding before you create anything.
| Optional | Required | |
|---|---|---|
| Looks like | A card the user can close | A modal that cannot be closed |
| Buttons | Submit · Not now · Don’t ask again | I Agree · I Disagree |
| Escape / clicking away | Closes it (counts as “Not now”) | Does nothing |
| Stops appearing when | Answered, snoozed, opted out, or the cap is reached | Answered — either way |
| Records | The answers | The decision, plus time, IP, browser and a hash of the text |
| Use it for | Ratings, feedback, quick polls | Terms, policies, mandatory acknowledgements |
Who uses it
- Platform operators publish across tenants, and set what tenants may publish themselves.
- Tenant administrators run their own surveys for their own staff, within those limits.
- Compliance and legal staff read the ledger to show who accepted which version, and when.
- Everyone else simply answers a prompt when it appears.
Where to go next
- Getting started — switch it on, grant access, publish your first survey.
- Daily operations — writing good prompts, versioning, reading responses.
- Administration — permissions, targeting, pacing, the audit trail.
- Reference — every screen, field, table and endpoint.
- Research — the evidence behind how the prompts behave.
- FAQ & troubleshooting — when something is not appearing.