Administrator — Custom Data hub
For administrators who control access to Custom Data: roles, table permissions, shared Saved views, and safe deletion via Trash.
Table of contents
Goals and scenarios
New Custom Data UI
Goal — enable the updated workspace (off by default).
- Enable Custom Data UI v2 → ./how-to/enable-custom-data-ui-v2.md
Access control
Goal — who can create tables, edit rows, export data.
- Role settings → Roles and access
Table lifecycle
Goal — safe delete and restore without losing row data.
- Trash and restore tables → ./how-to/use-trash-and-restore-records.md
- Edit table (danger zone) → ./how-to/edit-model.md
Shared view settings
Goal — same filters and columns for the team.
- Saved views (shared) → ./how-to/use-saved-views.md
Import and data integrity
Goal — control bulk import and clear-then-import mode.
- Import from file → ./how-to/import-data-from-file.md
- Import from Google Sheets → ./how-to/import-from-google-sheets.md
Large tables and sorting speed-up
Goal — registers with hundreds of thousands of rows stay available; speed-up only after explicit confirmation.
- Speed up sorting → ./how-to/prepare-sort-index-for-large-table.md
- How it works → ./explanation/how-large-custom-data-tables-work.md
Where to work in the UI
- Users and roles module — Custom Data permissions.
- Menu → Custom Data:
- Custom Data models → Trash — restore / Delete permanently
- Save view → Make shared for everyone
- Model editor → Danger zone