Now that your first ClassLink Roster Server is set up and populated with data, you can now share that data with vendors who have developed Roster Server integrations.
In order to share the data in your ClassLink Roster Server, you need to add the vendor's Roster Server app to your Roster Server Console.
How to add Roster Server Applications
2. From the Dashboard, navigate to Applications
3. Click the "Add Applications" button
4. Here you can search for vendors that you want to make your data accessible to that have created a Roster Server Application. Click the + Add button next to their application.
5. After Adding an Application, you will be prompted to define what kind of Permissions you want to give the app for access to your data.
Roster Server Application Permissions
You can define how much data you want to expose or allow vendors access to through Permissions. You can always change, add, or remove permissions to any particular app by clicking on the Actions menu > Permissions.
The different Permissions define what kind or how much data a vendor has access.
Full: A vendor is sent or has access to all of the data that is hosted in your Roster Server.
Custom: A vendor is sent or has access to the data that is related to both the Organizations AND Courses that is defined by the App Permissions. This means, the vendor will not have access to any user data that is not part of both lists of approved Orgs and Courses as defined in the App Permissions.
None: The vendor has no access to the data hosted in your Roster Server.
How to Share Data with the Vendor
After you have added the Roster Server Application and set the App's Permissions in your Console, the vendor will receive an email notifying them that your district added their app in Roster Server. The email will contain your REST API url and a unique API key and secret.
You can also view the API key and secret for each vendor application under actions.
The 2 ways to share data with a Vendor is by REST API and/or by SFTP. Both can be found in the Actions Menu next to any particular Application.
If you know your Vendor can access your Roster Server data through REST API, after you've added their Roster Server Application, an email will automatically be sent to the vendor with the relevant Endpoint URL, API Key and Secret for your district. Once the Vendor has access to that information, they can access the Roster Server data that you have set through the App Permissions whenever they need it.
If your Vendor requests CSVs or does not use REST API to access your Roster Server data, they will give your SFTP credentials and details that you can populate in the App's SFTP Settings to schedule automated exports with the data that is defined by your App's Permissions.
Once you've populated the supplied SFTP details into the application, you also need to specify the Export Template that is being sent to the Vendor. Some Vendors will require a particular template or version of the Roster Server specification be sent to them. If they don't, send the latest Roster Server specification (OneRoster v1p1 as of when this article was published).