Datasets

​

What is a dataset?

A dataset is a named, structured data object stored in TextQL. Datasets are the files and tables that Ana works with — either uploaded by you (a CSV of target accounts, an Excel mapping table) or generated by Ana (the result of a query, a transformed dataframe, an exported table). Once a piece of data is saved as a dataset, it becomes reusable: the same dataset can be referenced by name from multiple threads, playbooks, and dashboards without re-uploading or re-querying it.

​

Dataset types

Datasets are organized into folders so related data can be grouped and found by path, and each dataset is versioned — saving over an existing dataset creates a new version rather than overwriting the prior one.

​

How Ana uses datasets

• In a thread. Attach a dataset to a conversation and Ana can query it directly as structured data, rather than reconstructing it from a description.
• In a playbook. Attach the lists and lookup tables a playbook depends on so every run reads the same source data. See Attaching datasets.
• In a dashboard. A file-backed dashboard data source reads from a dataset, so a refresh always pulls the current version.

​

Access control

Datasets enforce object-level access control. Access to a given dataset is granted in one of the following ways:

• Owner. The member who created a dataset always has access to it.
• Shared grant. A dataset can be shared with specific members or roles. Reads are gated on that grant, so people only see the datasets they have been given access to.
• Public datasets. Datasets published to the organization are readable by members per your role-based access control settings.
• Derived access. If you can access a thread or playbook that references a dataset, you can read that dataset in the context of that object.

Dataset permissions follow your organization’s role-based access control. By default, members can create and edit their own public datasets; admins can manage datasets across the organization.