Access is how you share an incident without sharing a password. Open it from Admin → Access when an incident is active. Use it to invite people, change groups, remove access, resend invites, and review Join requests from the Dashboard Open list. Admin → Permissions is a separate page for editing the owner’s permission-group library — it only appears if your group allows Edit permission groups. The car icon on a Mapping site card is a different tool — that finds a drive to the pad.

The owner always has full rights and cannot be removed or demoted. Admin (the incident group) can invite, accept join requests, change members, and edit groups. Editor can do the day-to-day ops — map, inventory, frequencies — but does not manage Access by default, and Integrations stay off until you turn them on. Viewer is mostly look, with export where that is allowed. Custom is a clone you reshape. Known emails join immediately. Unknown emails become pending invites and unlock when that person registers or signs in. Anyone who can invite can Resend from the members table.

Someone who is not on the incident yet can tap Join on a Live fire from the Dashboard. That emails the owner and anyone with Accept join requests, and it shows on Access plus a small count on Admin. Approve picks a starting group (Viewer unless you change it). Deny can include a short note that the requestor sees on their Dashboard. They can ask again after a deny.

When you can edit groups, open Admin → Permissions. The matrix is one row per module: Overview, Inventory, Mapping, and so on, with Hide / View / Edit plus a few extra flags (export, publish, secrets, accept join requests). Hover a row if the label is not obvious. Incident Admin is not a platform role. If someone cannot open a page they expected, change the group. If the whole site is locked or a platform tool is missing, contact your system admin.