---
orphan: false
---

# Reference

The Reference section brings together information about this domain's purpose, core capabilities, product entry points, and documentation topics.

## Purpose

- Reference pages provide quick access to stable enumerations, compatibility ranges, permissions, and error-handling conventions.
- Feature visibility is determined jointly by the version, deployment, permissions, and feature flags.
- If a reference page differs from your runtime environment, follow the API contract and product interface for your deployed version.

## Product entry and core objects

| Item | Current implementation |
|---|---|
| Page entry | Reference pages do not map to a single runtime entry. |
| Service contract | Enumerations come from the current frontend registration, Core IAM actions, backend routes, and MatrixOne SQL capabilities; the deployment contract takes precedence over the documentation snapshot. |
| Core objects | Enum, Feature flag, Permission action, HTTP status, Connector type, Operator |

## Topics

::::{grid} 1 2 2 2
:gutter: 3

:::{grid-item-card} SQL reference
:link: sql/index
:link-type: doc
:class-card: mo-product-card

Read the SQL reference to understand its use cases, core objects, procedures, and capability boundaries.
:::

:::{grid-item-card} API reference
:link: api/index
:link-type: doc
:class-card: mo-product-card

Read the API reference to understand its use cases, core objects, procedures, and capability boundaries.
:::

:::{grid-item-card} Permission reference
:link: permissions/index
:link-type: doc
:class-card: mo-product-card

Read the permission reference to understand its use cases, core objects, procedures, and capability boundaries.
:::

:::{grid-item-card} General reference
:link: general/index
:link-type: doc
:class-card: mo-product-card

Read the general reference to understand its use cases, core objects, procedures, and capability boundaries.
:::

::::

## Recommended path

1. If you are a new user, start with the concept or overview pages to understand the relationships between objects.
2. Follow the how-to guides to complete a minimal verifiable flow; do not use production data at the outset.
3. If you encounter permission, status, or compatibility issues, consult the reference and troubleshooting pages.

## Authorization and limitations

:::{note}
Reference information does not replace the change history. Before you upgrade, also check the release notes and compatibility guidance.
:::

## Documentation tree

```{toctree}
:hidden:
:maxdepth: 2

SQL reference <sql/index>
API reference <api/index>
Permission reference <permissions/index>
General reference <general/index>
```