How Polzy recognises people
Say who your managers, newcomers or business customers are with your own fields, so the questions meant for them reach them — and ask a team question once for each project, store or session a person is in.
On this page
Some questions are meant for some people only: one for managers, one for people who started recently, one for business customers. Recognising people is where you say who those people are in your workspace, using the fields you already keep. Each one is a condition with a name — Managers, Newcomers — and rules that read your fields. The same page names the field a team question is asked once per value of, so somebody in two projects answers about each of them.
Every plan has it. Only Admins can open it, under Settings → People → Recognising people.
Open the page
Open Settings in the sidebar, then Recognising people under People in the left menu. The page lists your conditions under Who is who, then the group field under Per group. Nothing changes until you choose Save, and a condition that is not finished — no name, or a rule with nothing to compare with — cannot be saved.
Read a condition
Each row is one condition. Its name comes first, then what it picks in one sentence — Has direct reports, Start date within the last 90 days — and below it what it stands for:
- For Managers, For Newcomers: the question bank's audiences. Questions written for that audience go to the people this condition picks.
- A theme name, such as Onboarding: the theme's bank questions are asked of the people this condition picks, and of nobody else.
A condition with neither still names a group of people, in the same rules a pulse uses to ask one of its own questions of some people only.
Add or change a condition
- Choose Add condition, or the pencil beside a condition to change it. It opens in place.
- Give it a Name — the word you use for these people.
- Under Who it picks, each rule is one sentence on one row: Department is Sales, Support. Choose one of your fields, then how it is read in the small menu beside it, then what it is compared with:
- a list field: is or is not, then the values in the menu beside — each one you pick stands under it as a chip, with × to take it out; for a text field you type the words;
- a yes/no field: is yes or no, from a small menu;
- a date: within the last a number of days, or more than a number of days ago;
- a number: is at least or is at most a value.
- Choose Add a rule for another one. It can be chosen once every rule says enough, and starts on a field you have not used yet. Rules are joined by and, and every one must hold: Department is Sales and Start date within the last 90 days picks newcomers in Sales. The × at the end of a row removes it. A rule that cannot be saved yet says what it needs under it: Choose at least one value. or Enter a number.
- Under Question bank audiences, choose who this condition is for the bank. Under Themes only for them, pick themes to keep to these people.
- Choose Done, then Save.
Has direct reports reads your reporting lines rather than a field. It is offered beside your fields only when the workspace keeps managers (Reporting lines, a capability in workspace settings). Remove a condition with the bin beside it.
Suggest from my fields
Choose Suggest from my fields and Polzy reads your fields — their names and their values, in any of the six languages — and proposes the conditions it recognises: Managers from a role field or your reporting lines, New joiners from a start date, Business customers from a segment or plan field, Mobile users, Online attendees and In-person attendees. Each one is shown as Suggested. Choose Add to keep it, or Dismiss; then Save. Nothing is proposed for an audience a saved condition already stands for.
Suggestions are read from your fields, not written by AI: the same fields always give the same suggestions.
Ask team questions per group
Under Per group, choose a Group field: a multi-choice list field of your people, such as projects, stores, accounts or sessions. Team questions from the question bank — the ones about "my team", "my manager", a product or a session — are then asked once for each value a person holds, and each answer counts for that value. Questions about the whole organization, such as eNPS and the safety questions, are still asked once. A new pulse starts with this field as its split, and can choose another.
Choose None — ask once to ask every question once. If none of your fields is a multi-choice list, add one under Settings → People → Sync & fields.
What people answering see
Conditions change nothing in the builder: a survey keeps all its questions. When somebody opens their invitation, Polzy leaves out the bank questions that are not for them, and repeats each team question once per group, with About Atlas above it. A required question they are not asked is not required of them.
- Only questions still in the bank's words follow the conditions. A question you reworded is asked of everyone, once.
- A public link has nobody to recognise, so it shows the survey as written.
- Somebody with no value in a field is never picked by a rule on it — not even by is not.
- An anonymous answer — a campaign that promises anonymity, or somebody who answers anonymously by choice — is asked every question, whoever they are: a condition that picks one person would otherwise make their anonymous answer the only one with, or without, its questions. Team questions are still repeated per group.
Read results per group
When you group theme results by your group field — on the heatmap, for example — a team question's answers count for the value they were about, not for every group the person is in. The privacy floor applies to each value on its own: a project with fewer people than your minimum group size stays hidden. Settings → People → Groups shows each value, its people and who is answering: see Groups.
Ask Polzy follows the same rules. When it searches the question bank it says who each question goes to here, and for "a survey for the Sales team" it suggests only questions those people would be asked. Setting up a workspace with Polzy proposes conditions from your fields.
Troubleshooting
- The page is not in my menu. Only Admins see it, and only while contacts are switched on for the workspace.
- Has direct reports is not offered. The workspace keeps no reporting lines: switch on Reporting lines in workspace settings.
- I cannot choose a group field. None of your fields is a multi-choice list. Add one under Sync & fields.
- Save stays grey. A condition has no name, or a rule has no value or no number yet — the rule says which under it. Finish it, or remove the rule.
- A rule disappeared. Its field was removed, or changed type, under Sync & fields. A rule that can no longer be read is dropped, and a condition left with no rule goes with it.
- Everyone got the managers' question. It was reworded in the survey, so it no longer follows the conditions — or the person answered through a public link.
Related articles
Signed-in members can ask Polzy or message the team from Support. How fast we reply depends on your plan.