Set Up Your Organization

Build the structure that powers your reports, permissions, and comparisons.

Before you begin

Before you can collect feedback, you need to tell Ombea where you're collecting it. That means setting up your organization's structure — the locations, the websites, and the groups that tie them together.

The structure in 30 seconds

Your account has three building blocks, and they nest like this:

Folders hold Locations and Websites. Locations and Websites hold Touchpoints. That's it.

Tip:

You don't need to set up everything at once. Start with one Location, add a Touchpoint, create a Stream, and see data flowing. Add more structure later.

The setup order

  1. Plan your grouping (optional). Multiple sites? Decide how to group them — by region, brand, or department. Each group becomes a Folder. If you only have a few locations, skip folders and put everything at the root.
  2. Create your locations. For each physical site, create a Location with its address, timezone, and opening hours. For each website, create a Website and install the JavaScript snippet.
  3. Add Touchpoints to each location. Inside each Location or Website, add the Touchpoints that match how you collect feedback — a smiley device at the door, a survey link on the receipt, a widget on the checkout page. Your account manager provides the Subscription IDs.
  4. Create a Stream. Now that locations and Touchpoints exist, create a Stream — the actual survey with questions, logic, and design. Assign it to one or more Touchpoints.
  5. Check the Dashboard. Once responses come in, they appear on your Dashboard, automatically grouped by your hierarchy.

→ Full step-by-step: Set Up Your Organization

→ Manage locations: Create Folders, Locations & Websites

Why the structure matters

The hierarchy isn't admin busywork — it directly affects three things:

The Dashboard lets you filter and compare data by any level of your hierarchy. Want to compare Stockholm vs Gothenburg? They need to be separate Locations. Want to see all of Nordics at once? Group them in a Folder.

Access rights are tied to Folders and Locations, not to Streams. Grant someone access to a Folder and they see data from everything inside it. Plan your structure with this in mind.

Leaderboard competitions rank Locations against each other. Your hierarchy determines which Locations compete.

Good to know

Moving a Location to a different Folder doesn't delete its data. Historical responses stay intact — they appear under the new parent in the Dashboard.

A single store might have an ExpressPod by the entrance, an ExpressTab at the service desk, and a QR code survey link on the receipt — three Touchpoints, one Location. Responses from all three flow into the same place in your reports.

You don't need the perfect hierarchy on day one. Start flat, then add Folders when you actually need to group or restrict access. Over-engineering early creates more work than it saves.

Was this helpful?