Table of Contents
Overview
Quick Guides:
- Beanstack Rostering Guidelines for New Partners
- Beanstack Back to School 24-25 Rostering Guidelines
- Beanstack Summer Reading Challenge & Rostering Guide
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 |
| No | Yes |
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.
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 only imports sections or classes (and all associated data) with the subjects: Homeroom/Advisory and English Language Arts.
We filter sections to make reporting easier and cleaner for school and district administrators.
In many cases, you may want to change or remove this subject filter. Read on to determine any changes you’d like to make and ensure you adjust your sharing settings accordingly.
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.
Default Section Filters
Clever: Beanstack imports classes with the following Clever subject field values:
- English/language arts
- Homeroom/advisory
For sections shared via ClassLink, Skyward, and other solutions using the OneRoster standard, Beanstack creates a subject field based on the class name, using these terms:
- Homeroom/Advisory = ['homeroom', 'advisory', 'hr', 'attendance', 'advisement', 'kindergarten', 'first grade']
- ELA = ['eng', 'english', 'language', 'read', 'writing', 'lit', 'ela', 'spell']
Adjusting or Removing Beanstack’s Section Filter
Common reasons to change or remove this filter include:
- You want all teachers—from gym to social studies to ELA—to encourage and/or track independent student reading, and to log reading sessions for their classes.
- You want secondary teachers of a range of subjects to encourage and track independent reading with their classes.
- Your homeroom or ELA classes will be filtered out because of your school or district’s naming conventions (e.g. you use the “Other” subject field for homeroom classes in Clever).
If you choose to remove the section filter altogether, it’s critical to share only the section or class data you want Beanstack to ingest.
Before requesting that Beanstack disable or change your sections filter:
- Know that this filter and adjustments to it can only be applied district-wide.
- Keep in mind that many elementary teachers will have the same group of students rostered to them for multiple classes, like homeroom, math, social studies, and science.
- We highly recommend fine-tuning the sharing settings for classes and sections before removing this filter.
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 “metadata.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
- Teacher endpoint:
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.
SSO
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.
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
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.
Additional Resources
Find more information at:
- Our Rostering FAQs
- Clever documentation on adding apps and sharing settings
- ClassLink help center