Pass-through integration for local government · records are never stored System status1-559-251-7767Sentra familySign in
SentraBridgeIntegration platform
Multi-clientPlatform

One platform.
Every agency kept apart.

Each city, county or district is its own workspace with its own connections, flows, code tables, people and history. Shared templates are published once and rolled out to many.

One platform, separate workspacesA shared template library rolls out to three client workspaces, each with its own connections, flows, code tables, people and history.Shared templatespublished once · update noticesCity of Demo• Sentra 311 + Accela• 12 flows• Board folder map• 9 peopleDemo County• SQL Server + ArcGIS• 7 flows• Status code map• 5 peopleDemo Water District• SFTP bank files• 3 flows• Fund code map• 3 peopleNothing crosses between workspaces: connections, records, history and people stay apart.
Each agency is its own workspace; templates are shared, data never is.
§ 01 / Workspaces

Separate by default.

A workspace holds a client's connections, flows, value maps, people and run history. Nothing is visible across workspaces. Staff who support several agencies switch between them without anything crossing over.

  • Viewer, builder and admin roles per workspace
  • Only admins change connections
  • Suspended clients stop running
Roles in a workspaceper workspace
rolecan seecan doalso
ViewerSee flows, runs and history——
BuilderEverything a viewer canBuild, preview and run flows—
AdminEverything a builder canManage people and value mapsChange connections and secrets
CSP staffPlatform adminsManage clients and shared templatesSuspend or restore a client
Each workspace has its own people and roles.
§ 02 / Shared templates

Publish once. Roll out to many.

Build a flow once, publish it as a shared template, and roll it out to many clients. When the template improves, clients get an update notice instead of a silent change. Each client keeps its own connections and value maps.

  • Update notices, not surprise changes
  • Per-client value maps fill in local codes
  • 20 ready-made templates to start from
The template gallery in SentraBridge.
§ 03 / Sign-in

Your identity provider, or two-step sign-in.

People sign in with Microsoft or Google, through your own identity provider (SAML) with SCIM keeping the list of people in step, or with a password and an authenticator code. Each workspace can require two-step sign-in and limit sign-in to its networks.

  • SAML single sign-on and SCIM
  • Two-step sign-in, required if you choose
  • Departments and network allow-lists
Status · Demo Countyper-client page
statedetail
● FlowsOperationalAll scheduled runs on time
● WebhooksOperationalReceiving and verifying
● Sentra 311 connectionHealthyLast good run 4 min ago
● Accela connectionNeeds attentionSign-in expired
Illustration: each client can have its own status page.
§ FAQ

Questions, answered

Can one client see another's flows?

No. Connections, flows, code tables, people and history belong to one workspace.

Who is SentraBridge for, the agency or its vendor?

Both. Agencies run their own workspace; IT providers and vendors who serve several agencies use one workspace per client.

See your own systems connected.

We'll set up a workspace with your systems in a sandbox and build your first flow with you.