Skip to content
  • There are no suggestions because the search field is empty.

Rostering & SSO Integrations

Table of Contents

Overview

Quick Guides:

Beanstack integrates with these rostering and single sign on tools for schools:

Service Rostering? SSO?
Clever Yes Yes (see restrictions below)
ClassLink Yes Yes (see restrictions below)
Skyward Yes No
RapidIdentity Yes Yes (web app only)
Aeries Yes No; can be used with Google SSO
Google No Yes
Microsoft No Yes
Wonde Yes No

These integrations allow us to import classes and users from these student information systems to set up readers, classes, and staff with the correct roles in Beanstack.

Schools can also import rosters via our CSV rostering tool.

Back to top

Rostering Guidelines

What to Share

Fine-tuning the rostering data that you share with Beanstack creates the best experience for  your staff and students. 

We recommend sharing: 

  • All students, staff, and teachers
  • All sections or classes for which teachers should be able to view reading log data and log group reading sessions. Generally: 
    • Elementary grades: sections with Homeroom/Advisory and/or ELA subjects only 
    • Secondary grades: all academic sections

The documentation below details best practices for sharing user and section or class data. 

Sharing Sections or Classes

By default, Beanstack imports all classes. We strongly encourage administrators to only share Homeroom or ELA classes for elementary students. 

How Beanstack Uses Section and Class Data

When Beanstack imports section or class data, this allows that class’s teacher or teachers to: 

  • Log reading for an entire class at once
  • View reading logs for the students rostered to their class or section

Beanstack also uses class and section data to provide classroom-based reporting for school administrators. 

Sharing recommendations for Classes

We strongly recommend limiting the classes you share with Beanstack: 

  • Elementary grades: sections with Homeroom/Advisory and/or ELA subjects only 
  • Secondary grades: all academic sections

Beanstack can apply filters to classes in cases where schools or districts  cannot filter data. 

To remove or change Beanstack’s subject filter, contact your implementation specialist or client success manager, or submit a ticket to https://landing.beanstack.com/support

Setting Staff User Permissions

Role Types Data Access Reading Challenge Permissions
District Administrator All Schools Publishing for all schools
Media Specialist Plus All staff and students in their school Publishing for their school
Media Specialist All staff and students in their school Challenge publishing for their rostered students
Media Clerk All staff and students in their school Challenge publishing for their rostered students
Teacher Their rostered students Challenge publishing for their rostered students

View more details on roles and permissions here.

Setting Staff Roles via Rostering Metadata

To set administrator roles in Beanstack, supply an additional metadata field for users named “beanstack_role”. The value provided should match one of the following:

  • Media Specialist Plus
  • Media Specialist
  • Media Clerk
  • Teacher

This metadata field is not required for all administrators. It can be provided only for those whom you wish to assign roles other than the default.

In Clever, please be sure to toggle the “Extension Fields” option on. 

* District administrator roles are created by the Beanstack team rather than via rostering data. 

District implementations: We highly recommend automating role assignment via metadata.

Default Role Assignments

If Beanstack does not receive information via metadata about a user’s role, we create the following roles and permissions by default: 

  • OneRoster solutions (includes ClassLink, Skyward, RapidIdentity, and Aeries): 
    • All users sent through the teacher and user endpoints default to the Teacher role type
    • In addition to teachers, we only import administrator and aide roles (we do not, e.g. import guardians)
  • Clever: 
    • Teacher endpoint: 
      • If a user’s title includes “Media Specialist” we set assign the Media Specialist role
      • If a user’s title includes “Media Clerk” we assign the Media Clerk Role
      • Otherwise, users are assigned the Teacher role
    • School admin endpoint:
      • If a user’s title includes any of the following strings, we set their role to media specialist: media, specialist, reading, librar, teacher, spec, instructional, counselor, coach, social, parapro, principal
      • If a user’s title includes “media clerk” we set their role to media clerk
      • Otherwise, we set their role to teacher

Two key staff access notes for district implementations: 

  • Note that we do not automatically assign any users to the media specialist plus role. 
  • District administrator roles are created by the Beanstack team rather than via rostering data. 

Back to top

SSO

Services

Contact the Beanstack team to activate one of the following SSO options. 

Clever, ClassLink, and RapidIdentity: if you use one of these rostering services, we highly recommend using their SSO solution for Beanstack as well. 

Google: Google SSO can be combined with Skylink and CSV rostering. Google admins should verify Beanstack as an approved app. 

Microsoft: Microsoft SSO can be combined with Wonde and CSV rostering. 

Mobile restrictions

Currently, we support the following SSO solutions in the Beanstack mobile app:

  • ClassLink
  • Clever
  • Google SSO

The mobile app does not currently support:

  • Clever or ClassLink badges
  • Google SSO implemented within Clever 

Back to top

Troubleshooting

When troubleshooting rostering and related SSO issues, timing is everything. Changes may take 24-48 hours to sync, and in some cases up to a week. This is because rostering changes may take up to 24 hours to populate in your shared data, and Beanstack performs rostering syncs once a day. 

Beanstack runs two types of rostering syncs:

  • Daily syncs (overnight) that check for information flagged as new or changed
  • Weekly syncs (over the weekend) that import all shared rostering data

When troubleshooting login or other rostering issues:

  • Check your own rostering data first. Were changes recently made? Are sharing settings correct? 
  • Wait 24 hours, then check again. Most issues will resolve in this timeframe. 
  • Then, you can reach out to your rostering service for support, or submit a ticket with Benastack’s support team. 

Back to top

Additional Resources

Find more information at:

Need more help?
Submit a ticket