Team & Organization Management
Configure multi-tenant organizations, teams, roles, notification matrices, and country-level deployment settings in TerraGuard.
Overview
TerraGuard supports multi-tenant organizations, each with their own teams, notification rules, and operational configurations. The team management system controls who sees what, who gets notified about which events, and how the platform behaves for each organizational context.
Organizations
An organization is the top-level entity in TerraGuard. Each organization operates independently with its own:
- Member roster and role assignments
- Teams and team memberships
- Notification matrices
- Country configurations
- Report templates and settings
Screenshot: Organization settings page showing the org name, description, member count, creation date, and navigation tabs for Teams, Matrix, Countries, and Settings
Creating an Organization
Organization creation is available to any authenticated user. The creator becomes the organization's first administrator. Additional members are invited via email — they must have or create a TerraGuard account (authenticated through Clerk with Google sign-in).
Member Roles
| Role | Permissions |
|---|---|
| Admin | Full access: manage members, teams, matrices, settings, and all platform features |
| Manager | Manage teams, configure matrices, generate reports, send notifications |
| Member | View events, access knowledge base, use AI features, receive notifications |
| Viewer | Read-only access to events and reports |
Roles are assigned at the organization level. A user can belong to multiple organizations with different roles in each.
Teams
Teams are groups within an organization that share notification preferences and operational focus.
Screenshot: Team list view showing three teams (Emergency Response, Regional Monitoring, Logistics) with member counts, notification channel indicators, and status badges
Team Configuration
Each team has:
- Name and description — Identifying the team's purpose
- Members — Users assigned to this team
- Notification channels — Email list and/or Telegram chat
- Alert level preferences — Which severity levels trigger notifications
- Event type filters — Which disaster types the team monitors
Example Team Structure
A typical humanitarian organization might configure:
| Team | Focus | Alert Threshold | Event Types |
|---|---|---|---|
| Emergency Response | Rapid deployment decisions | RED only | All types |
| Situation Monitoring | Ongoing event tracking | RED + ORANGE | All types |
| Regional - Asia Pacific | Asia-Pacific events | All levels | All types |
| Logistics & Supply Chain | Pre-positioning planning | RED + ORANGE | EQ, TC, FL |
Organization Matrix
The organization matrix is the core configuration that determines how events are routed to teams. It maps combinations of alert levels and event types to specific handling rules.
Screenshot: Organization matrix configuration showing a grid with event types on rows (EQ, TC, FL, VO, DR, WF) and alert levels on columns (RED, ORANGE, GREEN), with cells containing team assignments and action indicators
Matrix Structure
The matrix is a two-dimensional grid:
- Rows — Event types (Earthquake, Tropical Cyclone, Flood, Volcano, Drought, Wildfire)
- Columns — Alert levels (RED, ORANGE, GREEN)
Each cell in the matrix specifies:
| Setting | Description |
|---|---|
| Assigned Teams | Which teams receive notifications for this combination |
| Auto-Report | Whether to automatically generate a report |
| Notification Priority | Immediate, standard, or digest |
| Follow-up Schedule | Custom follow-up intervals (default: +2h, +12h, +24h) |
How the Matrix Works
When a new event is ingested or an existing event changes alert level:
- The notification engine looks up the event's type and alert level in the matrix
- It identifies which teams are assigned to that cell
- It checks country configurations to see if the event location is relevant
- It filters by each team's individual preferences
- Matching teams receive notifications through their configured channels
Country Configuration
Country configurations define your organization's operational presence and deployment likelihood for each country. This determines which events are relevant based on where they occur.
Screenshot: Country configuration table showing a list of countries with columns for country name, region, VF Entity status (Y/P/N), deployment likelihood, and active team assignments
Deployment Likelihood
Each country is assigned a deployment likelihood indicator:
| Code | Meaning | Description |
|---|---|---|
| Y | Yes | Organization has active presence; high relevance for all events |
| P | Possible | Organization may deploy; moderate relevance for significant events |
| N | No | Organization does not operate here; low relevance, RED alerts only |
How Country Config Affects Notifications
The deployment likelihood combines with the alert level to determine notification behavior:
| Alert Level | Y (Active) | P (Possible) | N (Not Present) |
|---|---|---|---|
| RED | Immediate notification to all assigned teams | Immediate notification to assigned teams | Notification to monitoring teams only |
| ORANGE | Standard notification to assigned teams | Digest notification | No notification |
| GREEN | Digest notification | No notification | No notification |
This prevents notification fatigue by ensuring teams only hear about events that are operationally relevant to their organization.
Bulk Configuration
Countries can be configured individually or in bulk:
- By region — Set all countries in a region to the same deployment likelihood
- Import/Export — Upload a CSV of country configurations
- Template — Apply a predefined template based on organization type
Authentication
TerraGuard uses Clerk for authentication, supporting:
- Google Sign-In — Primary authentication method
- Email/Password — Fallback option
- Multi-Factor Authentication — Optional MFA for enhanced security
User accounts are linked to organization memberships. A single Clerk account can belong to multiple TerraGuard organizations.
Audit Trail
All administrative actions are logged:
- Member additions and role changes
- Matrix modifications
- Country configuration updates
- Team creation and deletion
- Notification settings changes
The audit log is accessible to organization administrators and helps maintain accountability for configuration changes.
Next Steps
- Reports & Notifications — How notifications reach your teams
- Labels & Contacts — Organize events with labels and manage contacts
- Notification Engine (Architecture) — Technical deep dive
Reports & Notifications
TerraGuard generates AI-powered structured reports and delivers multi-channel notifications to keep response teams informed about disaster events.
Labels, Contacts & Filtering
Use labels to categorize and organize disaster events, and manage contact organizations and emergency contacts extracted from knowledge base content.