Skip to main content
All CollectionsAccounts and PermissionsAdmin Workflows
Demographic Information in KickUp: Attributes & Groups
Demographic Information in KickUp: Attributes & Groups

How "Groups" and "Attributes" affect the user experience

Victoria Kinzig avatar
Written by Victoria Kinzig
Updated over a week ago

Demographic information about staff can be loaded into KickUp in numerous ways, including via integration with a staff information system or through CSV uploads. Please discuss with your Client Success Manager to determine the best set of options for your organization.

Once demographic information has been loaded into KickUp, there are two distinct ways in which demographic information are represented and used: Attributes and Groups. This article explains the differences between the two and how they can help streamline your experience throughout the KickUp app.

Both Attributes and Groups

Certain capabilities in the KickUp app can be accomplished using either attributes or groups. There may be reasons for choosing to use one over the other - please consult with your Client Success Manager for guidance specific to your organization.

  • Assign access lists / rosters on a walks, coaching, or evaluation instance. This can be done based on both attribute values (e.g. assign everyone with the "Role" attribute value of "Math Teacher" to a math coach's access list) and groups (e.g. assign everyone in the "Math Teacher" group to a math coach's access list)

  • Filter the KickUp Directory - e.g. show only individuals with Role = "Principal", or show only staff who are in the "Year 1 Teachers" group. Once you have filtered down the directory based on either attributes values or group membership, you can use bulk actions to update permissions or groups.

Attributes Only

Attributes, but not groups, allow you to: 

  • Filter and compare data within reports and data visualizations - e.g. compare report data by school by displaying each school's data side-by-side in a heat map. 

  • Use data restrictions to restrict data access to specific value(s) of an attribute - e.g. allow principals to see only data about staff at their building.

As users' attribute values change, their data will be included or excluded automatically in the above ways based on the configurations that have been set. For example, if a user previously had the value of "Douglass" for the School attribute but then changed to "Allegheny" as their school attribute, then their submissions would be filtered in a report using their up-to-date attribute value.

Groups Only

Groups, but not attributes, allow you to: 

  • Share report access -- e.g. set up a PD Feedback report to be shared with the "Facilitators" and "Principals" groups. Read more about report sharing here.

  • Restrict the visibility of a learning opportunity to a group -- e.g. set an event to only be visible for those in the "Douglass High School" group.

  • Filter the "By staff member" Learning attendance table - e.g. view and export total PD hours and credits for teachers in the "Douglass High School" group. Note that the "Records" Learning attendance table can be filtered by either attribute or group.

As individuals are added or removed from groups, access in the above ways will adjust automatically.

Permissions are not directly tied to groups or attributes. They can be assigned individually or can be assigned in bulk. 

Did this answer your question?