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

# Auto Number

> Generate increasing numbers when records are created. Useful for ticket numbers, order sequences, and internal IDs.

An **Auto Number** field automatically generates an increasing number for each record. After the field is created, Teable fills existing records and future records with numbers, so users do not need to maintain them by hand.

## Use Cases

| Scenario                     | Good for                                                                |
| ---------------------------- | ----------------------------------------------------------------------- |
| Ticket numbers               | Generate short IDs for issues, feedback, or support requests            |
| Order and contract sequences | Create internal sequence numbers for orders, contracts, or applications |
| Member or candidate IDs      | Assign base IDs to members, candidates, or employees                    |
| Conversation references      | Refer to records with numbers such as `#45` in messages or comments     |

## Create and Configure

<Steps>
  <Step title="Choose the field type">
    Click the `+` icon on the right side of the table header, then choose **Auto Number** from the field type list.
  </Step>

  <Step title="Name the field">
    Enter a field name, such as "Order ID", "Member ID", or "Ticket Number".
  </Step>

  <Step title="Save the field">
    After the field is created, Teable fills sequence numbers for existing records and future records.
  </Step>
</Steps>

## Field Behavior

* **Auto-incrementing**: Each new record receives the next number in the sequence.
* **Read-only**: Auto numbers are record metadata. Users cannot edit specific values by hand.
* **Stable across views**: After a number is generated, it stays with the record. Sorting, filtering, and switching views do not change it.

## Notes

* Auto numbers only move forward. If record `3` is deleted, Teable does not reuse that number. The next new record continues with a later number. Gaps can appear in the sequence so references to historical records stay stable.