Roles and Access

ImpactGrid access is organization-scoped. A successful identity-provider login does not by itself grant access; the user’s email must also be a member of an ImpactGrid organization.

Role	Intended use
Administrator	Organization configuration, users, incidents, and operations
Incident Commander	Incident creation and command-level changes
Operations	Team, assignment, dispatch, and operational status workflows
Team Leader	Field leadership access where configured
Team Member	Field participation access where configured
Viewer	Read-only situational awareness where configured

Users can hold more than one role. Platform-owner capabilities are separate from ordinary organization roles and include cross-organization administration.

Field-team links and member-intake links are token-based and scoped to one incident. Anyone who receives such a link may be able to access its intended workflow, so treat it as operationally sensitive and revoke or replace it according to local policy if exposed.

Draft permission summary

This table describes the intended role model. A detailed permission matrix will be added after every screen and action is verified against the current application.