Skip to content
A.
Deck
Operator manual // Documentation

Every control needs
a clear operating path.

These guides give operators a safe, repeatable path from release verification to routine maintenance. Release-specific instructions will be added with each published package.

The guide deliberately avoids asking for passwords, one-time codes, QR data, or account tokens. Do not place those details in a support request.
See how it worksOpen Download Center
Section // 01

Operator guides

Guide // 01

Prepare your operator workspace

Confirm Windows compatibility, select the right release package, and keep a clean record of the version you install.

  1. 01Review the system requirements and current release notes before downloading.
  2. 02Use only a package linked from the Artemis Download Center.
  3. 03Record the installed version before opening a support request.
Guide // 02

Connect a group deliberately

Treat VRChat and Discord connection flows as account security actions, not a one-time setup checkbox.

  1. 01Confirm the group and connected account are ones you are authorized to administer.
  2. 02Sign in only through the provider flow shown inside a verified Artemis release.
  3. 03Do not send passwords, one-time codes, QR data, or account tokens to support.
  4. 04Review account access and remove it through the relevant provider if you no longer use Artemis.
Guide // 03

Start with one automation

Use a controlled first rule, observe its output, and expand only after an operator has reviewed the behavior.

  1. 01Choose one low-risk workflow and define its operator owner.
  2. 02Set review points before enabling broader routing or moderation behavior.
  3. 03Keep a manual rollback path for every recurring action.
Guide // 04

Back up and recover

Treat roster and configuration backups as an operational record. Test recovery before it is urgent.

  1. 01Keep restore media in a controlled location with access limited to approved operators.
  2. 02Confirm a backup can be read before replacing an existing install.
  3. 03Document the version and the date of every test restore.
Guide // 05

Configure Discord permissions

The optional Discord companion is a networked integration. Give it only the permissions and channels your workflow needs.

  1. 01Start with a dedicated test channel and a named operator owner for every alert route.
  2. 02Use the minimum Discord permissions needed for the commands and notifications you enable.
  3. 03Document how to pause the integration and remove its access if a workflow needs review.
Guide // 06

Set thresholds and recovery paths

Begin in a review-oriented posture. Expand automation only after its effects, alert routing, and pause controls have been tested.

  1. 01Define what a signal means, who reviews it, and when an automatic action must stop.
  2. 02Test the pause or kill-switch path before enabling a higher-impact workflow.
  3. 03Keep a dated record of threshold changes, approvals, and any recovery decision.
Guide // 07

Transfer devices or operators

Use account-level controls for billing and access, then follow the release-specific migration steps when they are published.

  1. 01Review your subscription and account status in the Command Deck.
  2. 02Do not share an account password or a device-specific credential during a handoff.
  3. 03Capture version, operating system, and error details before asking for help.
Section // 02

Documentation standards

Release-aware

Instructions that depend on a software build must identify the version they apply to. The Download Center and Changelog are the source for that reference once a canonical release record is configured.

Security-aware

A legitimate Artemis guide will never ask an operator to disclose a password, recovery code, QR data, or platform token.

Get support routingWhat leaves your PCCheck public service status