School safety is a team job. The IT director installs the agents, the safety coordinator writes the alert templates, the principal needs to see what's connected in their building, and someone in the business office pays the bill. Until this week, an AlertIO organization had exactly one login, so all of that work went through one person's Google account.
This update fixes that, and it also fixes a campus-targeting problem we've been hearing about from districts whose buildings share one internet connection.
- Multi-user organizations: invite your whole school safety team by email, each with their own login and an Owner, Admin, or Member role.
- Org switcher: people who work across several AlertIO organizations, such as a district office and its individual schools, can switch between them from the sidebar.
- Billing belongs to the organization and can be handed to a new Owner with an ownership transfer, so it no longer depends on one staff member's account.
- Campus pinning for computers: pin devices to a campus when several sites share one public IP, so a lockdown at Site A stays at Site A.
- Campus pinning for phones: phones on Android app 2.5.0 or later can be pinned too, so Site A staff never get Site B's alerts.
Multi-User Access for Your School Safety Team
Why one login wasn't enough
An emergency alert system is only as dependable as the people who maintain it. A single shared login causes the usual problems: a password passed around by email, no record of who changed a webhook, and a gap when the one person who had access changes roles or leaves the district. For a system that delivers lockdown alerts, that gap is a real risk.
Every AlertIO organization can now have as many users as it needs, and each one signs in with their own Google account. As always, there are no per-user fees: adding your team doesn't change what you pay.
Owner, Admin, and Member roles
Each person in an organization has one of three roles. Everyone can do the day-to-day safety work, and only the right people can change who has access or how the account is paid for.
Owner
The person responsible for the account. Owners can do everything an Admin can, plus manage billing: choose a plan, update the payment method, or cancel. Each organization has exactly one Owner.
Admin
For IT directors and safety coordinators. Admins can invite people, change roles, and remove users, rename the organization, and manage alerts, webhooks, devices, and campuses. Admins can view billing but not change it.
Member
For principals, building leads, and support staff. Members can manage alerts, webhooks, devices, and campuses and see who else is on the team. They can't invite users or change billing.
Every role can build alert templates, wire up webhooks, check Device Logs, and set up Campus Fencing, because those are the tasks a safety team shares. Roles only restrict access management and billing. The server checks every role on every request, so a hidden button is never the only thing stopping a change.
Inviting your team
Owners and Admins invite people from Settings → Users by entering an email address and choosing Admin or Member.
-
1Step 1
Send the invite
The invitee receives an email with a link that's valid for 7 days. You can resend it (the old link stops working) or revoke it from the Users page at any time.
-
2Step 2
They sign in with Google
The invite only works with the Google account that matches the invited email address. If someone tries to use it with a different account, nothing is created and they're asked to sign in with the right one.
-
3Step 3
They're on the team
The new user joins your organization with the role you chose, and you get an email when they accept. Someone who is new to AlertIO starts directly in your organization, with no empty organization of their own to clean up.
Invite links are single-use. Owners and Admins can see recent changes to the team (invites sent, accepted, and revoked, role changes, and removals) in the activity list on the Users page.
Make sure at least two people at your district can manage users. If your safety coordinator is the only Admin and they're out during an incident review, nobody else can add the people who need to see what happened.
Working across several organizations
Some districts run one AlertIO organization for the whole district. Others run one per school, with the district IT team supporting all of them. Anyone who belongs to more than one organization now gets:
- An organization picker at sign-in, which lists each organization with your role and plan status and puts the last one you used first.
- An org switcher at the top of the sidebar: click it to move between organizations without signing out.
If you have the dashboard open in two browser tabs and switch organizations in one of them, the other tab shows a banner asking you to reload instead of saving changes to the wrong organization.
Billing belongs to the organization
A district's subscription now belongs to the organization, not to the person who first entered a card:
- Each organization has its own Stripe billing account, so an IT contractor who supports two districts never has their billing mixed together.
- Billing emails such as payment notices and trial reminders go to the organization's current Owner.
- Ownership transfer: the Owner can make another team member the Owner from Settings → Users. The previous Owner becomes an Admin, so they keep their access. This works even if the subscription has lapsed, so the account can be handed to whoever is going to renew it.
When a staff member who set up AlertIO moves on, transfer ownership before their Google account is closed, and the account stays with the district.
Campus Pinning: When Several Schools Share One Internet Connection
Campus Fencing sends each alert only to the buildings that need it. It works out which campus a device is on from the public IP address it connects from. That works well when every building has its own internet connection.
Many districts don't work that way. An elementary and a middle school on one property, or a district that routes every building through one central internet connection, show the same public IP address for every site. Before this update, IP-based detection put every device in those buildings on the same campus, so an alert targeted at Site A also reached Site B, and there was no setting a customer could change to fix it.
Shared IP, no pinning
A lockdown webhook targeted at the elementary school also reaches every classroom in the middle school next door, because both buildings show the same public IP. Staff at the second site receive an alert that doesn't apply to them.
Shared IP, devices pinned
Each building's devices are pinned to their own campus. The elementary lockdown reaches the elementary school's screens, and the middle school is left alone.
Pinning computers and Chromebooks
Anyone on your team can now pin a device to a campus from Device Logs:
- Pin one device using the pin action on its row.
- Pin many at once: tick the checkboxes (or select every device on the page) and use Assign campus in the bulk bar.
- Unpin by choosing Detect by IP, which goes back to IP-based detection.
The change takes effect immediately on connected devices, with no restart or reconnect. Pinned devices show a pin badge in the Campus column.
A pin only applies while the device is on one of your campus networks. A pinned laptop taken home is still off-network, so an All Campuses lockdown doesn't reach a teacher's kitchen table. One result of this is that the shared IP still has to be listed under one of your campuses, but it doesn't matter which one, because the pin decides the campus for every pinned device.
A campus can't be deleted while devices are still pinned to it. AlertIO asks you to move or unpin those devices first, the same way it does for campuses that still have networks or webhooks attached.
Pinning phones
Phones don't connect from a campus network the way a classroom computer does. They receive alerts by push notification wherever they are, so pinning works differently for them:
| Webhook delivery mode | Unpinned phone | Phone pinned to Site A |
|---|---|---|
| Off / All Campuses | Receives the alert | Receives the alert |
| Selected Campuses, including Site A | Receives the alert | Receives the alert |
| Selected Campuses, not including Site A | Receives the alert | Skipped |
An unpinned phone receives every alert, which was already the case. A pinned phone receives its own campus's alerts wherever it is, and is only skipped for alerts aimed at other campuses. The goal is that staff at one site never receive another site's lockdown.
Phone pinning requires the AlertIO Android app 2.5.0 or later. Phones on older versions show All campuses in Device Logs and can't be pinned until they update. They keep receiving every alert in the meantime.
How to Get Started
Invite your team
Go to Settings → Users, invite your safety coordinator, principals, and IT staff, and choose a role for each.
Confirm your Owner
Check that the Owner is the person who should control billing. If not, use Make owner on the Users page.
Pin devices at shared-IP sites
If any of your buildings share an internet connection, open Device Logs, select each building's devices, and assign them to the right campus.
Update your phones
Make sure staff phones are on Android app 2.5.0 or later, then pin them in Device Logs the same way.
None of these features require new hardware, a reinstall on Windows, Mac, or Linux computers, or a new contract. They're available on every AlertIO plan now.
AlertIO delivers full-screen emergency alerts to every computer, Chromebook, phone, and display in your district, targeted to the buildings that need them and managed by your whole safety team. Start a free trial →