In this guide
List roles before creating logins
A dispatcher may need current locations and history. An owner may need broader oversight. An installer may only need temporary access during setup. Write down those roles, then check which permission controls the selected platform supports rather than assuming every role can be configured.
Use identifiable accounts
Where supported, give users their own accounts instead of passing around a shared password. This makes access easier to change when someone’s responsibilities change. Enable the platform’s available account security features and keep recovery details under the business’s control.
Limit exported data too
A report downloaded to a spreadsheet can remain accessible after a platform login is removed. Decide where exports belong, who can share them, and how long the business needs to retain them. Include those files in the same access conversation as the dashboard.
Review after organizational changes
When a staff member leaves, a contractor finishes, or a business changes ownership, review permissions and notification recipients. Confirm that the right people can still receive alerts and that former users no longer retain unnecessary access. A short recurring access review is easier than reconstructing a long history of shared logins.
PUT IT TO WORK
Your planning checklist
- Assign an account administrator.
- Map each user to a business role.
- Confirm available security and permission controls.
- Review logins, exports, and alert recipients after changes.
Planning archive: August 2024 topic. Written and first published September 26, 2026 as part of a retrospective collection, not published in August 2024. About the library.