One of the first decisions your institution will make when rolling out Steppingblocks is who gets access and how that access is managed. The right structure depends on your campus size, your team's capacity, and how your institution typically handles data requests. Graduate Insights supports four access models, described below, so you can match the platform to your existing workflows.
Before you decide: questions to ask
Getting your access structure right from the start saves time and avoids confusion later. Consider the following before choosing a model:
Who needs access to alumni names and contact information for their specific projects, goals, or use cases?
What is the capacity of the staff who will be managing the data? Can one person realistically handle the volume of requests, or do you need distributed support?
Do you have upcoming projects or reports that will require multiple people involved at the same time?
What processes does your campus already have in place for data access and data governance?
Option 1: Full access for everyone
The simplest model. Everyone on campus who wants access to the data receives it. This works well for institutions with a culture of open data sharing and teams that are comfortable working directly in the platform. There is no bottleneck for access requests, but it does require that users are trained and ready to work with the data responsibly.
Option 2A: Access managed by one central administrator
One appointed administrator handles all access requests from staff and faculty across campus and controls who gets access. This model provides centralized oversight and is a good fit for institutions that prefer a single point of contact for data governance. It works best when the volume of requests is manageable for one person.
Option 2B: Access managed by a unit or college-level administrator
One appointed administrator per unit or college manages access for staff and faculty within their area. This distributes the administrative workload while keeping oversight close to the teams using the data. It is a practical choice for larger institutions with distinct colleges or departments that operate independently.
Option 2C: One data reporter per unit or college
A designated individual per unit or college has full access to the data and the ability to download it. Staff and faculty in that unit submit data requests to that person, while everyone gains access to Graduate Outcomes. This model works well when most users need reports rather than direct platform access, and when you want to limit who handles raw alumni contact information.
Which model is right for your campus?
There is no single right answer. Institutions with smaller teams or centralized data governance often start with Option 1 or 2A. Larger, decentralized institutions typically find 2B or 2C a better fit. Your Steppingblocks Partner Success Associate can walk through the options with you and help you configure whichever structure makes the most sense for your institution!