Skip to main content
Reports and cases are for investigation and decisions. Tickets remain support conversations. Open Community Management → Reports & cases.

​
Create a case

A case records a title, kind, priority, description, optional member, restricted status, and optional related case. Cases can originate in the dashboard, a Discord ticket, a bot command, or a signed in-game report.

​
Investigation workflow

1

Confirm the subject

Verify the exact Discord and Roblox IDs. Unknown in-game subjects can receive a basic member record without inheriting a linked Discord identity or privilege.
2

Preserve the source

Keep the original ticket or in-game submission separate from staff interpretation. Record source links and timestamps.
3

Assign and investigate

Add allegations, evidence references, messages, and private notes according to workspace policy. Restricted content remains capability-checked.
4

Record a decision

Capture the decision and reason before executing any moderation. A report never performs moderation automatically.
5

Execute explicitly

Select the exact scope, confirm the action, and follow the durable provider job to its terminal result.

​
Moderation scopes

Rodyne supports the configured Discord and experience actions exposed by the workspace, plus a No action decision. Duration is required for temporary actions such as timeouts where applicable. At execution, Rodyne rechecks:
  • Staff capability and current workspace access.
  • Discord membership, native permission, and hierarchy.
  • Target identity and tenant scope.
  • Provider availability and entitlement.

​
Member notification

After a confirmed moderation action, Rodyne queues one DM with the community, action, case number, reason, and review guidance. Closed DMs are recorded as undelivered without failing the moderation. An interrupted result can remain unknown instead of being duplicated.

​
Restricted cases

Restricted access is separate from ordinary case read/write permission. Do not paste restricted notes into tickets, announcements, public Discord replies, or Member Dash summaries.
Provider signals and Scout results are investigation inputs, not automatic findings. Confirm the evidence and record a human decision.

​
Guided walkthrough

Rodyne reports and cases queue for investigations

Reports and cases keep source, evidence, assignment, restrictions, and decisions together.

The screenshot above is from the live Rodyne product. Use it to orient yourself, but rely on the current record state and live provider checks when operating the workspace.

​
Operating procedure

1

Preserve the report

Retain the original statement, source, and timestamp before adding interpretation.
2

Confirm subjects

Resolve exact Discord and Roblox identities; leave unknown subjects explicitly unknown.
3

Control access

Mark sensitive work restricted and avoid copying it into broader surfaces.
4

Record findings

Separate evidence, staff notes, allegations, and the final human decision.
5

Execute and verify

Run moderation only after the decision, then follow each provider target to completion.

​
Acceptance checks

​
Failure recovery

If a moderation target is unknown, keep the case open and inspect the live provider state. A missing DM is not the same as failed moderation; read the target outcomes separately.

​
Continue the workflow

Handle support tickets

Security and privacy