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

# Core concepts

> The model behind every Splendor endpoint: tenancy, datasets, search, handles, views, and provenance.

A handful of concepts recur across the entire API. Understanding them once makes every endpoint predictable.

They fit together in a line: your data lives in a **tenant**, organized into **datasets** that **sources** feed. You query a dataset through the **search model**, then page or export the results with **handles**, save them as **views**, and trace any result back through **provenance**.

<Columns cols={2}>
  <Card title="Tenancy & isolation" icon="building" href="/concepts/tenancy">
    Every request acts within one tenant, and data never crosses tenant boundaries.
  </Card>

  <Card title="Datasets & schema" icon="table" href="/concepts/datasets">
    Datasets hold your records and expose a queryable schema and readiness state.
  </Card>

  <Card title="Sources & images" icon="images" href="/concepts/sources-and-assets">
    Add JSONL, CSV, or images to a source — records and the images they reference become one searchable thing.
  </Card>

  <Card title="Search model" icon="layer-group" href="/concepts/search-model">
    One envelope spanning text, SQL, and semantic search.
  </Card>

  <Card title="Handles & cursors" icon="link" href="/concepts/handles-and-cursors">
    Page, export, and re-run queries from a handle instead of copying results.
  </Card>

  <Card title="Views" icon="bookmark" href="/concepts/views">
    Save a query or freeze a result set for repeatable analysis.
  </Card>

  <Card title="Provenance" icon="fingerprint" href="/concepts/provenance">
    Trace every result back to the source object and line it came from.
  </Card>
</Columns>

## Roles at a glance

Access within a tenant is role-based. The same tenant header selects the workspace; the token's role within that workspace decides what it can do.

| Role       | Who                | What they can do                                                                                                                                                                            |
| ---------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Member** | Any tenant member  | Read and query: search, list datasets and runs, read schemas, create and read views, run exports, upload to a source.                                                                       |
| **Admin**  | Tenant admins      | Everything members can, plus create, change, and delete data: sources, connectors, detections, datasets, ingest tokens, reindex and DLQ operations — and mint tenant and platform API keys. |
| **Staff**  | Splendor employees | Internal operations endpoints, separate from everything in this API.                                                                                                                        |

Read endpoints are open to any member; operations that mutate or delete require an admin role. See [Roles & permissions](/roles/permissions) for the full breakdown and [Plans & RBAC](/roles/plans) for how enforcement is enabled.