Version 7 is on its way, and with it comes some changes. This help article is provided to help you understand two actions you need to take to ensure the smooth transition of your database to V7.
Perhaps the most notable of the changes we have made relates to the way we handle the management of staff in V7 when compared to V6.
Note:
If you are a solo company, this is unlikely to affect you and can be ignored.
Dealing with Staff (non-admins)
In Version 7, you no longer (as an administrator) have to manage or create passwords for your staff. Instead, your staff will manage and maintain their own password using a password reset function which is common practice in today’s software world.
To effect this change, we have removed the functionality that you currently find in Admin > Users and access is now managed (by you) in a Permissions Module found on each staff account in V7. If this makes no sense at all, do not worry, all will all become apparent when the upgrade goes ahead. For now, all you need to do is follow the simple instructions (before the upgrade).
ACTIONS FOR YOU TO TAKE (before the upgrade) regarding your field-based staff (non-admins)
Navigation: Admin > All Users (Version 6)
Step 1
- First navigate to ADMIN > All Users (in Version 6).
- Make a note of every non-admin field-based staff user that you see here and their email address as shown in the example below.
Step 2
Navigation: Admin > Staff > Staff Details (Version 6)
- Find the staff record that corresponds to this user (in Admin > Staff > Staff Details.)
- Ensure that the email address listed (in STEP 1 Admin > Users) matches the work email address for the corresponding staff member (see example below).
Important:
This email account will be used to login to Pet Sitter Plus, so if the "work email address" field is empty, it is essential that an email address is entered here.
That’s it - that is all you need to do for your staff to ensure a trouble-free transition to version 7.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article