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

# Use the member directory

> Find identities, roles, history, attendance, and related community work.

Open **Community Management → Members** to search the workspace's member records and connected identities.

## What a member record contains

Depending on your permissions and available data, a member view can include:

* Discord and Roblox identities and verification state.
* Current recorded roles and mapped rank context.
* Restrictions and moderation history.
* Support tickets and related reports/cases.
* Event attendance and confirmed results.
* Rank requests and provider outcomes.
* An audited activity timeline.

Restricted records remain filtered even when the same person appears elsewhere in the workspace.

## Search and pagination

Search by the visible identity fields supported by the workspace. The directory uses cursor pagination so it remains stable as records change. Clear filters before assuming a member is absent.

## Start work from a member

Authorized staff can use the member context to:

* Start a rank request.
* Add a member to a report or case.
* Review ticket context.
* Record an event result.
* Inspect identity conflicts before a provider action.

## Batch rank preparation

Each eligible member row can hold a target rank selection. Draft selections persist for the current staff member across filtering, pagination, and reloads. One shared reason submits up to 100 rows; each row still retains its own approval policy and stale-state checks.

<Warning>
  Do not use a similar display name as identity proof. Confirm the exact Discord and Roblox IDs, especially before moderation, discharge, or cross-community work.
</Warning>

## Guided walkthrough

<Frame caption="The member directory is the starting point for identity-aware community work.">
  <img src="https://mintcdn.com/rodyne/3VLEvtRzxXCeXuB_/assets/screenshots/members-detail.png?fit=max&auto=format&n=3VLEvtRzxXCeXuB_&q=85&s=e72ec321917fa70e7679d7ad21c65748" alt="Rodyne member directory with identity and operational context" width="990" height="650" data-path="assets/screenshots/members-detail.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="Search exact identifiers">
    Prefer Discord and Roblox IDs over display names when consequences matter.
  </Step>

  <Step title="Confirm link state">
    Review first-party verification and any identity conflict before action.
  </Step>

  <Step title="Read relevant history">
    Inspect rank, ticket, case, event, and restriction context allowed by your role.
  </Step>

  <Step title="Start scoped work">
    Create the request or record from the verified member context.
  </Step>

  <Step title="Return to the timeline">
    Confirm the new record and its final outcome appear on the same member.
  </Step>
</Steps>

## Acceptance checks

| Check    | Ready when                                              | If it is not ready              |
| -------- | ------------------------------------------------------- | ------------------------------- |
| Identity | Exact provider IDs match the intended person            | Stop and resolve the identity   |
| Scope    | The active workspace owns the record                    | Switch to the correct workspace |
| History  | Restricted details are only visible to authorized staff | Review capabilities             |

## Failure recovery

If search finds multiple similar people, do not merge records or proceed from display names. Compare provider IDs, first-party ownership, guild membership, and audited links.

## Continue the workflow

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

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