Xporter: MIS Permissions
Summary
Clarification on why set permissions are required when connecting Xporter to your MIS.
Answer
Scope
- Guidance on why certain MIS permissions are requested when you are asked to set up a connection between your MIS and Xporter.
- VenturEd Solutions has no access to your data in transit, and all personal and potentially sensitive data is always encrypted to industry standards.
Why can’t I choose to remove certain permissions?
- If you have one of the following MIS’, you won’t be able to customise the permission set that you are being asked to authorise when you attempt to set up Xporter:
- Arbor
- PupilAsset/Juniper Horizons
- Integris
- ScholarPack
- SchoolPod
- WCBS PASS
- Xporter has been configured in your MIS’ portal to request all available permissions, this means Xporter is able to support data items for any linked 3rd party application data feeds that the school are using.
- The authorisation request has been set up in this way in accordance with the method by which your MIS is able to share data with Xporter.
- Xporter works best when all available permissions are enabled, this means Xporter is able to support data items for any linked applications’ data feeds.
What will happen if I untick/ choose not to include the recommended permissions?
- If you are using one of the following MIS, you will be asked to tick choose a number of permissions and data areas:
- Bromcom
- SIMS
- iSAMS/edGen
- Schoolbase (API)
- We strongly recommend that you include all the data areas and/or permissions that you have been asked to share.
- Xporter works best when all available permissions are enabled, this means Xporter is able to support data items for any linked applications’ data feeds.
- If there are certain permissions you do not wish to grant access to, you are welcome to configure the account as required.
- Note: this may impact the synchronisation of data between your MIS and the third-party applications your school uses.
- If you encounter any errors when attempting to send data to your 3rd party application, we will ask you to ensure that all the recommended permissions for Xporter have been selected.
Creating a SQL account
- You may have an MIS that requires a SQL account to be created in order for a connection with Xporter to be setup. These include:
- Engage
- Schoolbase (Local)
- WCBS PASS
- The db_datareader permission will need to be mapped to the SQL account you create for Xporter.
Additional authorisation procedures
- For Xporter on Demand feeds, schools must authorise the 3rd party application for the specific data areas needed in Xporter On Demand, providing an additional layer of audit and protection for the school’s data.
- The Xporter On Demand data sharing agreement can be found here.
- For Xporter Bespoke data feeds, we will only request data from the endpoints that are specifically required for that feed. We will only provide the specific information to a 3rd party application in a data feed that has been requested by the partner, which the school will have agreed in their data sharing agreement.
- Schools should also refer to the data sharing agreements provided to them by their 3rd party applications.
