Skip to main content
A native Database stores structured records in your Erstan workspace. Use it for working sets such as collections cases, document review queues, or operational trackers. Tables define the fields; records hold the values; saved views control how you see them. Choose a Sheet for workbook calculations and a Database for records that need defined field types, relationships, and repeatable views.

​
Create and organise a Database

Open Content from your profile menu, choose a team and folder, then select New → Database. Give it a name and create a table. Define fields for the information you need, then add records. Agents can also create Databases and open them in chat Canvas; Agent-created Databases appear in Artifacts. Use the table’s search, filters, sorting, and display controls to focus the list. Save a view to return to that configuration. Where a grouping field is suitable, use a board to organise records visually. Saved views do not grant additional data access. Database permissions continue to apply to the underlying records.

​
Edit records and fields

Open a record to view and edit its fields, follow relationships, and inspect its history. Save your changes and check the result. If someone else has changed the record, reload and reconcile the changes before saving again. Changing a table’s field definitions can affect records, saved views, and Apps that depend on it. Review a schema change before applying it, and update affected App bindings before continuing to edit through those Apps.

​
Import and export

Choose Import records to import a CSV. Match its columns to existing table fields, then choose whether to add new records or update matching records and add new ones. Updating needs a suitable unique match field. Imports report progress and any remaining batches. If interrupted, use the offered retry controls rather than starting the whole import again. Export matching records as CSV or Excel. The download respects the selected filters, sorting, and fields; it includes the matching records beyond the currently displayed page.

​
History and storage

Record history lets you inspect earlier values and restore an eligible saved version. Restores must still satisfy the current table definition and permissions. Database data and retained history count toward account storage. Owners can review storage and retention settings. Enabling cleanup can remove older history and recovery information, so review the displayed impact before applying a policy.

​
Apps, Agents, and triggers

Apps can read a table or display it as a native page. An App’s binding limits the allowed operations and fields, and the current user also needs Database access. Draft App previews are read-only for production records. Agents can query and maintain records through Database tools. Published Agents can also use supported record-created, record-updated, and record-deleted triggers. Configure the Database, table, and authorized Run As identity before relying on an event-triggered process. See Agent triggers. For a named read that several Apps or Agents should reuse, create a Data Source.