Castlewatch User Guide

A starter guide for administrators, reviewers, and reporters using Castlewatch to run private incident coordination for a church security team.

Create or access your workspace

Use the signup page to create a new organization workspace, or log in if your account already belongs to an organization.

  • Use an email address your organization can recognize and support.
  • Keep the first administrator account limited to trusted operators.

Complete organization onboarding

Confirm the organization name and primary region. Onboarding activates the workspace profile before the team begins live operations.

  • Use a region label that your partner organizations will understand.
  • Review billing after onboarding when the workspace is ready for reporting and review.

Configure settings

Organization settings control members, notification defaults, mapped sites, policy thresholds, sharing defaults, and organization profile details.

  • Add mapped sites for common reporting locations.
  • Keep member roles aligned with actual duties.
  • Set notification recipients before high-volume reporting begins.

Submit incidents

Reporters should capture the operational facts: what happened, when it happened, where it happened, how severe it was, and who should be able to see it.

  • Use concise titles and factual summaries.
  • Add tags that support search and pattern recognition.
  • Select a visibility mode intentionally.

Review and moderate reports

Reviewers claim reports and move them through explicit moderation actions. Use comments to preserve decision context and follow-up needs.

  • Claim reports before detailed review.
  • Request changes when facts are missing or unclear.
  • Verify reports only when ready for the selected audience.

Coordinate trusted partners

Use trusted partner workflows to request organization connections, review relationship status, and track template MOU/NDA signing details.

  • Confirm relationship intent before sending a partner request.
  • Keep signing metadata accurate for each template document.
  • Review sharing defaults after partner connections are active.

Maintain the operating record

Use comments, sightings, attachments, audit views, and organization reports to keep decisions traceable over time.

  • Attach supporting files when they materially help review.
  • Log follow-up sightings when a pattern continues.
  • Review audit trails after sensitive workflow changes.