> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rodyne.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Run events

> Schedule sessions, track attendance, confirm results, and create follow-up rank requests.

Open **Community Management → Events** to schedule and host trainings, sessions, and other community activity.

## Create an event

Define:

* Title and description.
* Start and end time with the intended timezone.
* Optional Roblox experience.
* Minimum attendance guideline.

If Discord event delivery or reminders are enabled, follow their job outcomes separately from the saved Rodyne event.

## Host on mobile or desktop

The event host view keeps roster actions, attendance, and results available on small screens. Staff can add manual attendance when policy allows. Studio connector attendance is server-observed and appears separately.

## Attendance is not a result

Attendance records presence. It does not prove pass, completion, promotion eligibility, or staff performance.

* Overlapping Studio intervals are merged.
* The minimum duration is a guideline.
* Staff explicitly confirm pass/fail or another result.
* A result can support a separate rank request; it does not bypass rank approvals.

## Follow-up rank requests

After a confirmed result, an authorized host can start a rank request with the event link attached. The request still checks the member's current rank, target protection, approver separation, and provider outcome.

## Discord commands

`/event list`, `/event create`, `/event view`, and `/event attendance` use the same event records as the dashboard. Permissions and current workspace scope apply to both surfaces.

<Tip>
  Before ending the session, reconcile manual and connector attendance, confirm results, and review any follow-up requests that remain drafts or waiting for approval.
</Tip>

## Guided walkthrough

<Frame caption="Events separates scheduling, observed attendance, confirmed results, and follow-up work.">
  <img src="https://mintcdn.com/rodyne/3VLEvtRzxXCeXuB_/assets/screenshots/events-main.png?fit=max&auto=format&n=3VLEvtRzxXCeXuB_&q=85&s=d1374949c1bbfc72bae4a52fcc37d9ec" alt="Rodyne Events page for schedules, attendance, and results" width="990" height="742" data-path="assets/screenshots/events-main.png" />
</Frame>

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

<Steps>
  <Step title="Create the schedule">
    Set title, time, timezone, host, and optional experience.
  </Step>

  <Step title="Brief the host">
    Confirm roster responsibilities and how manual and Studio attendance will be reconciled.
  </Step>

  <Step title="Track presence">
    Record attendance without treating duration as a pass or performance result.
  </Step>

  <Step title="Confirm results">
    Have authorized staff explicitly record pass, fail, or other outcomes.
  </Step>

  <Step title="Create follow-up work">
    Start any rank request from the event context and follow its normal approval policy.
  </Step>
</Steps>

## Acceptance checks

| Check      | Ready when                                   | If it is not ready                     |
| ---------- | -------------------------------------------- | -------------------------------------- |
| Time       | Stored timezone and visible time are correct | Edit before reminders run              |
| Attendance | Intervals are attributable and de-duplicated | Reconcile manual and connector records |
| Result     | A human-confirmed result is present          | Do not create automatic promotion      |

## Failure recovery

If connector attendance is missing, preserve manual notes and diagnose the heartbeat, universe, event ID, and server interval. Do not reconstruct exact attendance from memory when the evidence is incomplete.

## Continue the workflow

<CardGroup cols={2}>
  <Card title="Install the Studio connector" href="/setup/studio-connector" icon="plug" />

  <Card title="Review rank requests" href="/guides/rank-requests" icon="user-round-check" />
</CardGroup>