> ## 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.

# Member Dash

> Release reviewed personal records through a separate member-safe portal.

Rodyne Dash is the separate member portal at [dash.rodyne.xyz](https://dash.rodyne.xyz). Members sign in through Cnect without receiving staff access.

## Disclosure is off by default

Existing workspaces begin with Dash disabled, and source records are not automatically published. Owners configure sections, allowed fields, eligible statuses, ordering, labels, and former-member policy.

Each record release requires:

* `dash.disclose` authority.
* Permission to read the source record.
* Reviewed member-safe text.
* An eligible, verified identity relationship.
* An enabled section and current settings revision.

## What is excluded

Member responses exclude internal reasons, private notes, evidence, ticket transcripts, raw provider payloads, and other fields outside the approved contract. Restricted releases keep their original authorization requirements.

Reports **about** a member and reports **submitted by** a member are independent sections and releases. Submitted in-game reports require the signed connector's real Roblox submitter proof.

## Exact preview

Use **Workspace settings → Member Dash** to preview a specific member. Exact preview calls the same eligibility and serialization logic as the member API; it cannot bypass restricted-record or network controls.

## Release and withdrawal

<Steps>
  <Step title="Configure the section">
    Choose allowed fields, labels, eligible statuses, order, and former-member behavior.
  </Step>

  <Step title="Verify the relationship">
    Current OAuth ownership, first-party Cnect proof, conflicts, membership policy, and audited relationship must agree.
  </Step>

  <Step title="Write member-safe text">
    Summarize only what should be shown to the member. Do not copy internal notes automatically.
  </Step>

  <Step title="Preview">
    Inspect the exact member view before release.
  </Step>

  <Step title="Release or withdraw">
    Release creates the member-visible record. Withdrawal removes active disclosure while retaining the audit history.
  </Step>
</Steps>

## Session separation

Dash, staff, and Cnect sessions are separate. A staff session does not grant Dash access, and a Cnect session does not grant staff access. Personal responses are private and non-cacheable.

## Guided walkthrough

<Frame caption="Member-facing disclosure begins with owner-controlled workspace settings and explicit releases.">
  <img src="https://mintcdn.com/rodyne/3VLEvtRzxXCeXuB_/assets/screenshots/workspace-settings-main.png?fit=max&auto=format&n=3VLEvtRzxXCeXuB_&q=85&s=a6d7ddca2620ba42b070ac3606ade903" alt="Rodyne workspace settings used to configure member-facing access" width="990" height="742" data-path="assets/screenshots/workspace-settings-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="Keep disclosure disabled">
    Design sections and eligibility before enabling the portal.
  </Step>

  <Step title="Choose fields">
    Allow only the fields necessary for the member-facing purpose.
  </Step>

  <Step title="Write safe summaries">
    Create member-safe text independently of private notes and evidence.
  </Step>

  <Step title="Preview the exact member">
    Use the real eligibility and serializer path rather than a generic mock-up.
  </Step>

  <Step title="Release and review">
    Publish deliberately, verify in Dash, and withdraw when disclosure should end.
  </Step>
</Steps>

## Acceptance checks

| Check       | Ready when                                      | If it is not ready                      |
| ----------- | ----------------------------------------------- | --------------------------------------- |
| Eligibility | Verified identity and current policy agree      | Resolve the relationship before release |
| Content     | No notes, evidence, or raw payloads are exposed | Rewrite the member-safe summary         |
| Revision    | Preview uses current settings                   | Preview again after settings change     |

## Failure recovery

If a member cannot see a release, check the Dash session, identity relationship, workspace policy, section eligibility, and release revision. Do not grant staff access as a workaround.

## Continue the workflow

<CardGroup cols={2}>
  <Card title="Security and privacy" href="/administration/security-and-privacy" icon="shield-check" />

  <Card title="Cnect identity linking" href="/cnect/identity-linking" icon="link" />
</CardGroup>