Create & Manage Reporting Groups for an Event - Overview | Point-In-Time & Lifecycle

Modified on Tue, 15 Sep at 12:41 PM

Analyze

Survey results do not do much good sitting with one person. Reporting groups are how you get each person the piece that is relevant to them and nothing beyond it.

 

Your human resources partners, your regional leaders, your managers: they all need something different out of the same survey. A reporting group is how you draw those lines. You build a bundle of reporting access once, then hand it to as many people as you like.

You can build as many groups as an event needs, each one shaped for a different role. One group watches response rates while the survey is still open. Another sees one slice of the population. A third gets the numbers but not the comments.

Reporting groups live in Advanced Reporting, under Report Editor in the left navigation panel, on the Permissions tab. That tab lists every group for the event, with the group name, description, how many users are in it, its status, and who created it. You start a new one from + Add New Group at the top right.

Two groups are there before you build anything. Every event ships with Access to reporting only and Administrative privileges, so if you open the tab and find groups you did not create, that is what they are.

One quick clarification

Groups and Permissions in the Admin Portal is a different feature with a similar name. That one controls who can build events and administer the platform. Reporting groups control who can see results.

The three settings that decide what somebody sees

Three settings work together here, and they do not all live in the same place. That is the part people miss.

Two of them belong to the whole group, and they are two of the three tabs you see when you open a group:

  • Reporting permissions control which reports, dashboards, and presentations people can open. That is the Permissions tab.
  • Demographic permissions control which demographics they can filter by. That is the Demographics tab.

The third one is set per person, as you add them:

  • Population access controls which response data that person can view at all. After the fact you find it on the Assigned Users tab, by clicking View details on somebody and opening their Population Access tab.

The one to remember

Population access matters most, because filtering never expands access. Limit somebody to part of the population and they can filter all day, but they only ever see that part.

Two more things before you start

  • Reporting groups belong to one event. Nothing carries over, so you set them up fresh each time.
  • You cannot give away more than you have. Your own visibility is the ceiling for anyone you assign.

One exception to the ceiling

Event Administrators are not bound by reporting groups. They see the full report for the event with no demographic or permission restriction applied.

Two more that are worth knowing once you get going. People can belong to several reporting groups, within the same event or across events, which is normal for somebody who is both a functional leader and a people manager. And minimum response thresholds still apply on top of everything you assign, so a group can have access to a report and still see nothing in it if the population behind those numbers is too small to report on.

The four stages

Setting one up takes four stages, and there is an article for each.

  1. Create the group. A guided four screen setup: group information, permissions, demographics, then a review.
  2. Add your users. Put people in the group and set each person's population access.
  3. Activate them. Nobody gets in until you do this, which is what lets you stage everything ahead of time.
  4. Manage the group as things change.

Where to go next

Work through these in order the first time. After that, jump to whichever one you need.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article