A customer feedback workspace without rebuilding the survey stack
Reference pattern, not a customer story: Northstar and Acme Logistics are fictional and the screens use sample data. The capabilities described are implemented in ResponseDock.
A SaaS product gives every customer account its own survey workspace, with per-user permissions, native theming, and lifecycle events.
Host
Northstar (fictional reference)
Industry
B2B SaaS with many customer accounts
Surfaces
Manage · Results · Inline, modal, hosted
Isolation
Per customer account and per user
app.northstar.example/acme-logistics/surveys
Acme Logistics
Surveys
+ New questionnaire
Create & ManageResults
QuestionnaireStatusResponses
Q3 customer onboardingUpdated today
Published
318 / 400
⋯
Driver app usabilityUpdated 3 days ago
Published
112 / 250
⋯
Warehouse safety checkUpdated yesterday
Draft
0 / 90
⋯
Carrier partner reviewUpdated Sep 2
Closed
74 / 75
⋯
9:41●●● ▮
Napp.northstar.example
Acme Logistics · 90 seconds
How smooth was your first shipment setup?
Secured by Northstar
The phone is live — tap an answer to try the member flow.
How it works
From a manager’s idea to answers, in five screens
Every screen below lives inside Northstar. ResponseDock renders the survey engine; Northstar owns identity, navigation, brand, and domain.
“Choosing between carriers took longer than the whole rest of setup.”
Open-text answers · filter, read, export
Each account admin opens a focused survey list inside Northstar. The host signs the account, user, and permissions, so admins only see their own account’s surveys.
Illustrative screens with sample data.
Challenge
Keep ownership in the host
A SaaS product with many customer accounts wants account admins to run their own surveys, while keeping each customer’s data separate, the design consistent, and navigation inside the product. A plain iframe or a shared survey account would not give enough control over who can do what.
Solution
Embed the engine, not another product
The host backend keeps identity and account ownership. It signs the current user, account, and permissions into a short-lived embed session, passes a version-controlled theme, and grants only what the current screen needs. ResponseDock supplies survey management, answering, shared results, exports, and lifecycle events.
Trust boundary
Who is responsible for what
Identity starts in Northstar. Every request is re-checked by ResponseDock before anything renders.
01Identity
The host signs the account ID, user ID, role, and permissions on its server.
02Authorization
ResponseDock checks the signed session on every protected request.
03Reconciliation
Server-side lifecycle events keep host mappings current after create and publish actions.
04Operations
Retries, audit records, export status, and diagnostic endpoints make the embed supportable.
Capabilities
Capabilities in this reference pattern
Account-scoped Create & Manage and read-only Results views
Capability-level authorization for create, publish, export, share, and results
Inline, modal, or hosted respondent presentation from the same survey definition
Theme-file support for colors, fonts, logo, radii, shadows, controls, and loading state
Auto-height messages so the host page owns vertical scrolling
Stable browser SDK events for analytics, reconciliation, and host workflows
Implementation outcome
What this pattern delivers
A survey feature that feels owned by the SaaS product
Clear account and permission boundaries without duplicating survey infrastructure
A reusable pattern for customer portals, associations, education, and vertical SaaS
This case study documents implemented product capabilities and architecture. It does not claim customer adoption, revenue, or response-rate uplift without measured evidence. Product screens are illustrative and use sample data.