Goal: each manager signs in and goes straight to their own results, with no settings or filters to apply, and receives their report every month.
Who it's for, and before you start
Who it's for | The administrator rolling out Feedier across a network (stores, branches, regions) |
Prerequisites | An attribute that identifies each manager's scope (for example |
Time | One to two hours for 10 managers, less with SSO |
Choose the right method
Method | When to choose it | Effect |
One team per manager | Few managers, each with their own sources | The team's data is fully isolated |
A filtered team view | One team per region, with its default filter | Members land directly on their scope |
A locked segment | Many managers in the same team | The filter applies automatically at sign-in |
The steps
1. Check the scope attribute
Each feedback must carry the store or region value, spelled identically everywhere. A referential can add the region and the manager's name from the store code. See Attributes and referentials.
2. Create the structure
Depending on the method chosen: create the sub-teams, or set each team's default filter and period in Settings → Teams → View, or create one locked segment per manager. See Filters, periods, segments and FQL.
3. Invite managers with the right role
Manager's need | Role |
View their results and reports | Viewer |
Handle only the feedback assigned to them | Restricted Viewer |
Create their own reports and alerts | Editor |
With SSO, team provisioning places each user in the right spot automatically. See Security: SSO, MFA and GDPR.
4. Only enable the useful modules
In Settings → Access management, turn off for the Viewer role the modules managers don't need: their interface stays simple.
5. Send each manager their report
Declare managers as owners of the attribute's values, then create a recurring automation that generates one report per value. See Create a recurring report for leadership.
6. Test with a manager account
Sign in with a test account in each role and check what's visible and what isn't.
Example
A retailer with 60 stores across 6 regions:
Level | Setup |
Headquarters | Root team, Editor role, sees everything |
Regional directors | One team per region, default filter on the region, Viewer role |
Store managers | Owners of the |
Common mistakes
Mistake | Consequence | What to do |
Misspelled attribute values | Feedback missing from the manager's scope | Normalize values at the source, or use a referential |
Placing sources in the root team only | Sub-teams see nothing | Place sources at the lowest level |
Giving everyone the Editor role | Reports and segments changed by mistake | Viewer by default |
Going further
Last reviewed: November 11, 2026, version 4.23.5.
