🔐 Admin Tools and Oversight

Admin-level dispatchers are trusted with sensitive tools and major responsibilities. This module covers managing dispatches, adjusting trust levels, setting coverage zones, and maintaining accountability through logs and audits.

---

Core Admin Permissions

Level 4 (Admin) users can:

• ✅ Create and edit dispatches
• 🔐 View and adjust user trust levels
• 📈 Export data and review audit logs
• 🗺️ Set and manage zone coverage
• 📋 Approve or remove reports
• 🧑‍🏫 Assign or revoke user roles and permissions

---

Creating & Editing Dispatches

Admins can manually initiate new dispatches, bypassing normal triage. This is allowed only when:

• The situation is urgent (active raid, medical crisis, imminent threat)
• Another dispatcher requests backup
• A trusted source confirms verified intel

Manual Dispatch Tips

• Use precise location data (cross streets, GPS if safe)
• Clearly flag urgency and timing
• Add internal notes (visible to trusted roles only)
• Avoid overuse; these tools should not replace collective triage

---

Trust Level Management

Each user has a tiered trust level:

Trust Level	Access
Level 0	Viewer only
Level 1	Can respond to dispatch calls
Level 2	Can view maps and accept calls
Level 3	Verified dispatcher (filter, assign roles)
Level 4	Admin dispatcher (full tools access)

Promotions must meet prerequisites:

• Level 1+: Completed Response Training
• Level 3: At least 3 months of activity, Dispatch Certification, 2 peer referrals
• Level 4: Invitation by core team, conflict resolution training

---

Setting and Managing Coverage Zones

Zone Leads manage regional coverage through:

• 🗺️ Zone radii (map click → set distance)
• 🌐 Assigned counties, cities, or neighborhoods
• 📍 Dynamic zones for marches, vigils, or emergency deployments

Best practices:

• Avoid overlapping zones without coordination — designate a primary lead and backup
• Tag zones for language capacity (e.g., "Spanish-speaking leads available")
• Adjust alert radius during off-hours (reduce after 10 PM unless critical)

---

Report Approvals and Removal

Admins can:

• Review flagged or duplicate reports
• Approve valid submissions
• Remove spam, harmful, or false data

Always:

• Document why a report was rejected in the audit log
• Use transparent reasoning to maintain trust
• Refer disputes to the Accountability Team (never resolve alone if contested)

---

Logs, Exports, and Audits

From the Admin Dashboard, you can:

• 📊 Export CSV logs for dispatch stats (avoid storing sensitive personal data)
• 🕓 Review timestamped logs for edits, approvals, and trust changes
• 🔍 Conduct audits to review major responses and identify gaps

---

Compromised Accounts

If you suspect a breach:

1. Revoke access immediately (via Admin Panel)
2. Notify the core team and affected leads
3. Audit recent logs for misuse
4. Reset passwords
5. File a brief report in the Admin SOS channel (Signal)

---

Accountability & Community Standards

Admin roles are about stewardship, not control. You must:

• Avoid editing dispatches except for accuracy or emergency reasons
• Never promote or demote without full review
• Join the Monthly Admin Sync to share updates and resolve tool issues
• Report tool bugs or access friction via this form

---

Summary

Admins hold the keys to critical infrastructure. Use this access to support your teams, protect the network, and uphold trust.