> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to use unique IDs to protect public forms and avoid data import errors
- URL: https://blog.jestor.com/unique-id-protect-public-form-data-import/
- Published: 2026-07-10T14:57:04.000Z
- Updated: 2026-07-10T14:57:04.000Z
- Author: Bruno Bannach

Using a random ID field instead of the title field as an identifier makes it harder for someone to guess or accidentally access another record's link in a **Jestor** public form, and it also solves a recurring problem for anyone who tried to use the title as a key to bulk-import records.

## Why does using a unique ID on public forms matter?

Public forms that use a predictable identifier in the link make it easier for someone to try to guess the link to a record that isn't theirs. And anyone working with spreadsheet imports runs into a similar problem: the title field isn't accepted as a key by Jestor's importer.

## How does a unique ID protect forms and improve imports?

- Instead of the title, the random ID field generates a code with no predictable pattern.
- This doesn't replace other security layers, but it closes a gap that existed when using a visible, sequential identifier.
- For bulk record import and update, the ID field, unlike the title, is accepted as a key by the importer.
- The same field also works to identify records within automations.

| Field used as key | Accepted for bulk import? |
| ----------------- | ------------------------- |
| Title             | No                        |
| Unique ID         | Yes                       |

To use the ID as a secure key:

1. Add a random ID field to the table.
2. Use that field — not the title — as the reference in public form links.
3. Use the same field as the key column in import or update spreadsheets.

## Why choose Jestor to protect data and imports?

Having a field specifically designed to serve as a secure, reliable key means the company doesn't need to repurpose the title field, which was built for display, for a use it wasn't meant for.

## Frequently asked questions

### Does a random ID completely prevent unauthorized access to a public form?

Not by itself — it makes guessing harder, but doesn't replace other security practices.

### Why doesn't the title field work for imports?

Because Jestor's importer doesn't accept title as a key; you need to use the ID field.

### Can this ID be used in automations?

Yes, it reliably identifies a specific record.

### Do I need to change the identifier on tables that already exist?

It's not required, but it's recommended for anyone using public forms or bulk imports.

## Reference video

Check out the [Jestor YouTube channel](https://www.youtube.com/@jestorbr?ref=blog.jestor.com) for more content like this.

## Discover Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.