This article is designed for schools who do not require a migration due to being a brand new school and details what should be completed on Arbor before your planned go live.
Go Live Checklist
Complete your site setup
Whether you're taking the 'standard' or 'extended' onboarding journey, you should ensure by the end of week four that your site setup is completed. This includes
- Year groups and registration forms
- Term dates and holidays
- Students
- Guardians
- Staff
You should use your implementation workbook to track progress throughout your implementation.
Check business roles and permissions
Every staff member who is planning to log onto Arbor should have a business role and correct permissions so they only access and view data that is applicable to their role. If staff members do not have a business role, navigate to the staff profile, find the 'current business roles' table and click add.
More information on business roles can be found here.
Note: You can see all business roles and permissions associated to them by going to School > Users and Security > Download
Ensure all staff have their work email address set as 'default'
Every staff member should have their work email address set as default. If this has not been set, users will not be able to log into Arbor with their work email address.
Share your Arbor URL with the team
Once you are happy that staff have the correct business roles and their email addresses are set correctly as 'default', you can share the Arbor URL with them so they can get logged in.
Note: Their username will be their email address and they will be forced to set a new password when they first log in. Please contact the onboarding team if you need help or follow this guide to troubleshoot logging in issues.
Approve your third party applications
You should have already notified any third party systems of your move to Arbor. Once you are live, you'll be able to approve and test these connections. To manage API connections on your Arbor site, you'll need the School: User Accounts: Administer permission.
To set up a new API connection, please follow the steps for approving a third-party connection here.
If you don't see the app you're expecting listed in your pending requests, it means they haven't yet asked for access to your Arbor site. You should contact them directly and ask them to do so.
Note: It is really important that you check that the data pulling through to your third party systems is correct and accurate. This is especially important if you're using third party applications to send any communications to guardians or external agencies.
Confirm that your registers are available
Check that the registers are available for day one by going to Students > Attendance > Registers by date then change the date to the first day that you plan to take attendance. This will show you all the registers scheduled for that day.
Make sure teachers know how to take a register
Share this guide with teachers ahead of your first day taking attendance so they know how to take a register in Arbor.
Set up any priority operations (e.g. behaviour, communications etc
Arbor has several areas of functionality that require some customisation before you can start using them e.g. Behaviour, Parent Portal. If you are planning to use any of these areas take a look at the setup guides in the Help Centre to guide you through the process.
Note: It is recommended that you go live with only the basic, statutory day to day operations before looking to implement further modules.
If you need support with any of these steps, please contact the onboarding team at myonboarding@arbor-education.com.
Comments
Article is closed for comments.