Departments & ranks

Structure your community.

Departments are how AwareCAD groups members and routes calls. Ranks live inside departments and drive callsigns, command structure, and the ladders auto-enroll bindings map into.

Admin → Departments — the four seed departments (DOT, Fire/EMS, PD, Sheriff's Office) with edit affordances and a New department form on the right.
Admin → Departments. PD / SO / FD / DOT are seeded on community create.

Default departments seeded on community create

Every new community gets four departments with realistic rank ladders:

  • Police Department (short code PD) — Recruit → Officer → Senior Officer → Sergeant → Lieutenant → Captain → Chief
  • Sheriff's Office (SO) — Recruit → Deputy → Senior Deputy → Sergeant → Lieutenant → Captain → Sheriff
  • Fire / EMS (FD) — Probationary → Firefighter → Senior Firefighter → Lieutenant → Captain → Battalion Chief → Chief
  • Department of Transportation (DOT) — Trainee → Trooper → Senior Trooper → Sergeant → Lieutenant → Captain → Superintendent

Delete what you don't need. The seeding is a one-time convenience, not a hard schema — your community can have one department or ten.

Department fields

  • Name + short code — short code shows on call rows and unit callsigns (e.g. PD-12). Keep it 2–4 chars.
  • Callsign format — template like {unit}-{number}. Used as a hint when admins set unit callsigns; not auto-generated.
  • Specialty — one of: regular, K9, SWAT, Detective, Air, Marine, Traffic, Narcotics, Special Operations, EMS, Fire, Other. Used by the multi-agency routing to suggest team→department mappings and by the MDT to badge specialty units distinctly.

Ranks

Each rank belongs to a department (or is "general" — applies across all). The pay grade order determines who outranks who: higher number = higher rank. Multi-step gaps (5, 10, 15, 25, 35, 45, 60) are intentional — leave room to insert new ranks without renumbering.

Ranks are referenced by auto-enroll bindings: a Roblox group rank maps to an AwareCAD rank, which determines the member's effective rank field. Don't delete a rank that's actively mapped — you'll get a friendly error from the binding editor.

Tier caps (member counts)

Every community member counts toward the tier cap, regardless of their role. A free-tier community can have 50 members; a member is a member whether they're an admin, officer, dispatcher, or civilian. See Billing & subscriptions for the per-tier caps.

Multiple Roblox characters per user do not multiply the count — one person on one Roblox account counts as one member, even if they spin up several civilian characters.

Permissions

Roles are coarse-grained (owner / admin / moderator / dispatcher / officer / civilian / pending). Fine-grained permissions are derived from the role + per-member overrides in admin/members.

Permission overrides are per-member, not per-department. If you need to grant Alice a single elevated permission without changing her role, use overrides. If a whole department needs a different default, ask in support — per-department permission scope is a deferred follow-up.

Last updated May 18, 2026.