OnboardingDepartmentsSystemsStatusSecurityReports

Start with the problem you are trying to solve.

ASRP support works best when the request starts in the correct place. Choose the route below instead of guessing which system owns the issue or sending unsolicited messages to individual leaders.

Open ASRP Main Community Hub

Choose a support route

Put the request where it can be handled.

Ticket names, forms, and channels can change. This page routes you to the stable public destination that owns the workflow.

New member

Joining & onboarding

Use the joining guide for entry, pathway selection, and first-step questions.

Open joining guide → Agency question

Department support

Choose the agency and use its official department page or Discord for membership, training, rank, scheduling, and command questions.

Choose a department → Access & systems

Nexus / CAD / member tools

Identify the current system first, then use the official ASRP support workflow for access or permission problems.

Open member tools → Availability

Service unavailable?

Check the public status directory and maintenance guidance before opening a duplicate outage report. Measured uptime will appear there only when real monitoring is connected.

Check service status → Technical issue

Server, script, voice, or access problem

Use the current support or development workflow exposed in ASRP Main. Include what happened, what you expected, and useful evidence.

Open ASRP Main → Security & privacy

Sensitive website or data concern

Review the public data boundary, then use the current private support workflow in ASRP Main. Never post credentials, tokens, private member data, or exploit details in a public channel.

Review privacy & reporting guidance → Conduct concern

Report a member or incident

Review the public reporting baseline, preserve relevant evidence, and use the current private report or complaint workflow.

Review reporting guidance → Review request

Appeal or formal complaint

Use the designated appeal or complaint process available in ASRP Main rather than bypassing the process through individual DMs.

Open official workflow →

Useful reports

Give the team enough context to reproduce the problem.

For technical or access issues, include the system involved, approximate time, what action you took, what you expected, what actually happened, and screenshots, clips, or exact error text when useful.

One issue per request

Keep unrelated development, access, department, and conduct matters separate so each can be routed and resolved independently.

Evidence over speculation

Logs, screenshots, clips, exact messages, and reproduction steps are more useful than guessing at the cause.

Protect sensitive evidence

Do not place passwords, bot tokens, API keys, private member information, or exploit details in public channels. Use the current private support/reporting workflow for sensitive material.

Use the current workflow

ASRP Main is the stable place to find the current authorized ticket, form, report, or escalation process.

Important

ASRP is not an emergency service.

This website, ASRP Discords, Nexus, and the ASRP CAD are fictional roleplay resources. They are not monitored or operated as real police, fire, EMS, rescue, or emergency-service contact points.

For a real emergency, use the emergency-services system applicable to your real-world location.

Still not sure?

Start in ASRP Main.

The main community Discord is the stable public entry point for current support panels, announcements, and direction when you do not yet know which department or system owns the issue.

Open ASRP Main