Where to start
Pick the path that matches what you are doing this week. Each path links to the articles in the order most teams need them.
How this knowledge base is organized
Castlewatch is built around explicit operational state: reports are submitted, reviewers make recorded decisions, trusted partners are connected through deliberate workflows, and organization settings define who can do what. The articles below mirror those workflows. Each article opens with an at-a-glance summary (who it is for, what to read first, what comes next), followed by structured reference material, common scenarios, frequently asked questions, and links to related work.
- Administrators should begin with onboarding, organization settings, access, and trusted partners.
- Reporters should focus on incident reporting and the incident record page.
- Reviewers should focus on the review workflow, incident records, and notifications.
- All roles benefit from the glossary, the notifications & access reference, and the troubleshooting checklist.
For Administrators Configuration & trust
Stand up the workspace, define who can do what, and decide how reports are shared by default.
Onboarding & workspace activation
Create the workspace, complete the organization profile, choose a region, and understand what must be active before live operations begin.
Organization settings
Manage members, roles, mapped sites, notification defaults, policy thresholds, sharing defaults, and organization profile details.
Trusted partners & trust groups
Request relationships, sign template MOU/NDA records, accept or decline partners, send secure messages, and group connected organizations.
For Reporters Capturing what happened
Submit complete, scoped, searchable reports that reviewers can act on without rebuilding context.
Incident reporting
Use structured fields, saved sites, severity, visibility, tags, summary, and narrative details to submit reports that reviewers can act on.
Incident records, comments, sightings & attachments
Understand the incident detail page, issue-style comments, timeline sightings, supporting files, and how records evolve after submission.
For Reviewers Moderation & verification
Claim reports, verify facts, narrow visibility, and preserve the decision context for the next reviewer.
Review queue & moderation
Claim reports, verify facts, request changes, reject submissions, return records to review, and preserve decision context.
Incident records, comments, sightings & attachments
How the incident detail page combines narrative, comments, sightings, attachments, and structured metadata after review.
For Everyone Reference & troubleshooting
Cross-cutting material used by every role: alert routing, access posture, common problems, and shared vocabulary.
Notifications, roles, billing & access
Understand personal alert preferences, organization notification defaults, role thresholds, subscription gates, and account security settings.
Troubleshooting common issues
Resolve onboarding loops, missing buttons, blocked reports, map placement problems, partner workflow blockers, and notification issues.
Glossary
Shared definitions for severity, visibility, moderation states, connection states, trust groups, policy thresholds, and other operating terms.
Prefer a guided walkthrough?
The user guide covers the same workflows in the order a new team usually configures and operates Castlewatch — from signup through the first verified report.