Share One Team's Poll Results Without Sharing the Poll

Good to know

A slice link shows a fixed, aggregate-only picture of one group. It never carries the ability to see the rest of the poll, or to look again later; that is what makes it safe to hand to the manager the group reports to.

Two people usually want to see results: the admin who ran the poll, and the manager whose team answered it. Until now the only way to show the manager was to give them the whole poll or a screenshot; share a slice is the third option: a read-only link that shows one cohort's aggregate as of a moment in time.

#Creating a slice

On an unlocked poll's results tab, open Share a slice. It sits beside the result filters, so it appears on polls that ask demographic questions or carry roster attributes, for the poll's owner.

Note

Groups unlock at close

While a poll is collecting, the dialog shares the whole result only, because comparing a group before and after new answers arrive could reveal one person's answers. Groups become available once the poll closes; closing early counts. Polls that never close, the Exit pool and the speak-up channel, only ever share the whole result.

Pick the group. Under Group by, choose one of the poll's demographic questions (department, region, role, tenure, experience level, or work mode), then a value under Group, or All responses for a whole-poll snapshot. The dialog starts on whatever demographic filter the results tab is currently showing. A roster filter isn't carried over yet, so the dialog says so and starts from all responses.

Check the floor. The dialog shows how many responses are in that group. Below five, or the poll's minimum group size if that's higher, it says so and the button stays disabled: no numbers are shown and no link can be made. The same happens for a group that could be worked out by subtraction from the rest of the poll; the dialog says it can't be shared on its own, without saying which group is small.

Choose an expiry. 7, 30, or 90 days. The default is 30.

Create the link. Copy it and send it to the one person it is for.

If your workspace encryption is open on this device, the slice is signed by your workspace, and whoever opens it can check the numbers came from you and haven't been edited since. A signed slice also offers an Evidence packet download.

The link looks like invizipoll.com/r/<id>#k=…. Everything after the # is the decryption key. The dialog says it plainly: the key is in the link, and we cannot recover it. A link pasted without its #k= part opens to an explanation, not to numbers.

#What the manager sees

Opening the link shows the poll title, the cohort label (for example Department: Engineering), the response count in that group, the date it was taken, and, for a series wave, which wave. Below that are the same charts the admin sees for that group, read-only, with a Download PDF button that produces the report with its Aggregate data only footer.

What they do not see:

Any other cohort, or the poll as a whole.
Written answers. Open-text questions appear as recurring-word themes and counts only.
Any live view. The snapshot is what the numbers were when the link was made; a manager who wants a fresh view asks you for a new link.
Anything below the five-response floor. The viewer refuses to render a snapshot that small even if one somehow reached it.

A slice is computed from the answers released to you. A whole-poll slice made while the poll is open leaves out the few answers held in reserve; a group slice is only made after close, when everything has been released. How batched release works.

#Why it is a snapshot and not a key

Handing a manager the poll key would be wrong for a cohort share: a viewer holding it could decrypt every response and run any filter they liked, and the cohort floor would then be enforced only by software they are free not to use. The poll-wide public results link avoids the same problem the same way: it serves one published summary, never the poll key or any response.

So a slice is a snapshot:

Your browser computes the group's aggregate with the same code the results tab uses, which already refuses to produce anything below the floor.
It serialises only aggregate fields: buckets, counts, percentages, scale statistics, eNPS, and open-text themes. Verbatim text and per-response data are not in the format at all, so they cannot ride along by mistake.
It encrypts that snapshot with a fresh random 256-bit key and stores only the ciphertext with us, along with the expiry.
The key goes into the URL fragment. Fragments are not sent to servers, do not appear in our logs or in CloudFront's, and are not seen by link previewers.

The server can tell you a snapshot exists and when it expires. It cannot read it, and neither can anyone who intercepts the request without the link itself.

#Managing links

Under Links for this poll, the dialog lists every snapshot with its created date, expiry, and state, a count of live links against your cap, and a Revoke button on each live one. Revoked and expired links open to This link was closed with a suggestion to ask for a fresh one.

Live links per poll are capped, and expired or revoked links free their slot:

Workspace	Live slices per poll
Business, Enterprise, or a trial with Business features enabled	20
Pro, or a standard trial	3
Free after trial	Not available

Snapshots are deleted with the poll.

See also Running an engagement. Each page covers the adjacent settings and workflow steps.

#Creating a slice

#What the manager sees

#Why it is a snapshot and not a key

#Managing links

#Related