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

# Atlas Overview

> Clubs, registered organizations, and Atlas reporting

Atlas is Meridian’s surface for **clubs and registered organizations**: recognition, directory, membership, roles, governance documents, budgets where configured, messaging, and the admin tooling campus staff use to oversee the org ecosystem. It is intertwined with **Beacon** (org-hosted events and approvals) and **Compass** (rooms and scheduling when org life touches space), but **Atlas is framed around the org as the unit of work**, not around utilization curves or the global event approval graph.

Atlas ships **its own reporting**—org health, membership, engagement-style org metrics, finance queues where enabled, and event analytics scoped to an organization’s programming. Those are conceptually separate from **Compass** utilization reports and **Beacon** cross-campus event and approval analytics.

## Key features

<CardGroup cols={2}>
  <Card title="Organization directory" icon="users">
    Recognition status, profiles, search, and the institutional view of clubs and orgs
  </Card>

  <Card title="Membership & roles" icon="user-group">
    Join flows, applications, officer permissions, and lifecycle of membership
  </Card>

  <Card title="Governance & policy" icon="shield-halved">
    Permissions, verification tiers, and org-side rules enforced in Atlas routes and UI
  </Card>

  <Card title="Atlas reporting" icon="chart-bar">
    Org-scoped dashboards and exports—distinct product intent from Compass utilization or Beacon approval funnel reporting
  </Card>
</CardGroup>

## Core capabilities

### Organization operations

* Admin and self-service flows for org leaders (rosters, messaging, announcements)
* Platform-admin views for compliance, recognition, and risk (see [Atlas admin](/atlas/admin))
* Finance and budget workflows where the tenant has enabled them ([finance & budgets](/atlas/finance-budgets))

### How Atlas meets Beacon and Compass

* **Beacon** carries the **event approval graph and stakeholder routing**; Atlas supplies **which org** is acting and **who in that org** may create or sponsor events under policy.
* **Compass** carries **scheduling and utilization**; Atlas does not replace that framing—orgs consume space through the same shared backend and UI patterns.

### Reporting

* Org-level analytics and templates (for example event analytics under org management where documented in deeper pages)
* Membership and participation signals for student-affairs operations
* Separate from Compass “how hard are rooms running?” and from Beacon “how fast do approvals move across campus?”

## Architecture

Atlas is implemented as **routes, models, and React surfaces inside the monolith** (not a separate microservice). See [Atlas architecture](/atlas/architecture) for how `getModels(req, …)`, org-scoped permissions, and admin entrypoints fit together.

Integrations with other products:

* **Backend API**: org management, membership, messaging, finance, configuration ([Atlas backend](/atlas/backend))
* **Beacon**: org-owned events and policy alignment
* **Compass**: org context when booking or events touch rooms and schedules

## Who uses it

* **Student org leaders**: run the org day-to-day within policy
* **Student affairs / org advisors**: recognition, oversight, reporting
* **Students**: discover and join organizations
* **Platform admins**: global configuration and exception handling

## Getting started

<CardGroup cols={2}>
  <Card title="Admin dashboard" icon="dashboard" href="/atlas/admin">
    Operator-facing org management and reporting entrypoints
  </Card>

  <Card title="Atlas backend" icon="server" href="/atlas/backend">
    REST map, auth gates, and multi-tenant access patterns
  </Card>

  <Card title="Permissions" icon="key" href="/atlas/permissions">
    Org-scoped roles and enforcement
  </Card>

  <Card title="Data model" icon="database" href="/atlas/data-model">
    Core collections and invariants for organizations
  </Card>
</CardGroup>

## Deep dives (internal)

<CardGroup cols={2}>
  <Card title="Architecture" icon="diagram-project" href="/atlas/architecture">
    How Atlas is wired end-to-end (routes, UIs, model access)
  </Card>

  <Card title="Backend APIs" icon="server" href="/atlas/backend">
    Endpoint map and request shapes
  </Card>

  <Card title="Frontend" icon="code" href="/atlas/frontend">
    React entrypoints and API usage
  </Card>

  <Card title="Membership" icon="user-group" href="/atlas/membership">
    Join flows, applications, and member management
  </Card>

  <Card title="Messaging" icon="messages" href="/atlas/messaging">
    Org messages, visibility, and API endpoints
  </Card>

  <Card title="Event analytics" icon="chart-column" href="/atlas/event-analytics">
    Org-scoped event analytics where implemented
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/atlas/troubleshooting">
    Common failure modes
  </Card>
</CardGroup>