Business modulesTables

Table access and imports

Configure row access and match import columns to table fields.

Use table Access for permissions and row rules; hidden rows are not merely visual filtering.

Where

Web: Tables · /tables. Desktop: Business → Tables.

Table access and imports
Table access and imports

Step by step

Configure access

Choose people and row rules on the table’s Access surface.

Prepare the import

Match columns to fields and review data types, row limits and the matching key for updates.

Review the result

Export respects access and filters. Clearing all rows is a separate destructive action.

What to know

Map file columns, validate types and limits during import. Upserts need a matching key.

Exports respect access/filter scope. Purging records is distinct from deleting the table.

Actions and permissions

Operation and IDInputsPermissionScreen or flow
Clear a table’s records · data.purge_rowsTable *Delete/archiveRecord/API/visitor flow; no separate screen button mapped
Change who may use a table · data.set_table_permissionTable *, Role *, Permission *, Granted *ManageRecord/API/visitor flow; no separate screen button mapped
Narrow who sees which rows · data.set_row_policyTable *, Rule, Name *, Applies to *, Condition, Who it is for *, ActiveManage/tables/[tableId]/access
Remove a row rule · data.delete_row_policyRule *Manage/tables/[tableId]/access
Import records · data.insert_rowsTable *, Records *, Only check the file, Skip rows with problemsImport/tables/[tableId]
Export records · data.export_rowsTable *, Filter, Search, LimitExport/tables/[tableId]
Add or update records · data.upsert_rowTable *, Match on *, Values, RecordsImport/tables/[tableId]

Ask Era

Prepare a requests table with customer, owner, status and date.

© 2026 Era. Era documentation. Something missing or wrong? Write to us: [email protected]