So you are excited to roll out Blazemark to your department!
But where to start?
While an article cannot possibly understand the intricacies of your actual situation, we can present some common practices we see folks doing with Blazemark.
In general, we recommend starting with an approach/process, trying it out on a small scale, testing, probing, getting feedback. Once you think you have a good approach, broaden the scope to more users, more vehicles, etc!
We recommend providing individual logins for users (using their unique email).
Control Sign-ups
We strongly advise you follow the tips here: Simplifying User Sign-up Control
User Roles
User -- Read-only. Able to access and see the preplan info. Useful for apparatus "users" for onboard tablets in your rigs.
Author -- Able to turn Edit Mode "on" to create, edit, and delete preplans.
Org Admin -- Author rights, plus able to invite users, adjust system-wide settings, import hydrants, help out their fellow users, etc.
Read more about User Roles here.
How should we set up logins for in-vehicle apparatus?
The best approach is the one that is the easiest. Typically apparatus are known by their own "name."
Engine 71 -- engine71@pltwfd.org
Ladder 3 -- ladder3@pltwfd.org
Or, maybe you want all vehicles to use a single login so that there is only one thing everyone needs to remember (might not work if you have many stations).
Timeout Due to Inactivity
We also recommend you increase the timeout for logins that will be on scene or in an apparatus to suit your needs.
Read More about Controlling Timeout
Inviting Users
You can have an open period where you tell folks to sign up -- and then remove the sign-up button (edit your org settings).
You can also add individual user emails to send them invites.
Read More Adding Users.
Audit Trail
Blazemark provides an Activity Log, so Org Admins can see what users are up to. And users can see what they have been doing in the system.