Check agenda packets before posting
Agendas published in CivicCA are scanned, and only those without critical findings go to the Sentra CMS website.
SentraCheck scans documents for accessibility problems and personal data, such as Social Security numbers, before they're posted publicly. It is made by the same company family as SentraBridge and is used by clerks, web teams and records staff.
The pre-built connector creates scans and reads their findings by severity. A flow can check every agenda packet or report on its way to the website or records system and hold back the ones with critical findings. Documents are not stored by SentraBridge.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Scans | list, read one | create | — | ID, Document, Scan type, Findings, Critical, High… |
Agendas published in CivicCA are scanned, and only those without critical findings go to the Sentra CMS website.
Documents bound for a public Laserfiche folder are scanned for personal data first.
Scans from the past week are counted by severity and emailed to the ADA coordinator.
New files in a department's SharePoint library are scanned and high findings posted to a Teams channel.
Systems cities commonly connect with SentraCheck, each with its own connector page.
Accessibility problems in documents and personal data, such as Social Security or account numbers, reported as findings by severity.
Yes. An if/else step after the scan sends documents with critical findings to staff and lets the rest through.
Not in this connector. Flows create a scan and read its result in the same run or a later one.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.