Share a slice: one team's results for one manager

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:

1. Pick the group. Choose a demographic dimension (department, region, role, tenure, experience level, or work mode) and a value, or All responses for a whole-poll snapshot. The dialog starts on whatever cohort filter the results tab is currently showing.
2. Check the floor. The dialog shows how many responses are in that group. Below five it says so and the button stays disabled: no numbers are shown and no link can be made.
3. Choose an expiry. 7, 30, or 90 days. The default is 30.
4. Create the link. Copy it and send it to the one person it is for.

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.

Why it is a snapshot and not a key

The poll-wide public results link works by wrapping the poll's decryption material for viewers. That is fine for a poll-wide audience, and wrong for a cohort share: a viewer holding the poll key could decrypt every response and run any filter they liked, and the five-response cohort floor would then be enforced only by software they are free not to use.

So a slice is a snapshot instead:

• 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

The dialog lists every snapshot for the poll with its cohort, created date, expiry, and state, and a Revoke button. 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.

Related

• Demographic cohorts and thresholds
• Public results link
• You said, we did: publishing actions after a poll
• Aggregate results and anti-inference