> ## Documentation Index > Fetch the complete documentation index at: https://docs.dataerai.com/llms.txt > Use this file to discover all available pages before exploring further. # Glossary > Plain-language definitions of the core Dataerai terms — organizations, projects, collections, assets, datasets, storage, and the research record. A quick reference for the words used throughout these docs. For how the pieces fit together, see [Key concepts](/get-started/key-concepts). ## Workspace & data | Term | What it means | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | **Organization** | Your institution or lab's home in Dataerai. Members belong to it, and it can auto-join people by email domain or institutional identity. | | **Project** | A workspace for a study, grant, or effort. It owns data and controls who can access it. | | **Collection** | A folder for organizing data. Collections can nest, and access cascades down them. | | **Asset** | The core unit of data — metadata plus its file content, notes, comments, and relationships. | | **Content** | The actual file or files attached to an asset. An asset can also exist with no content yet (a [metadata-first asset](/data/metadata-first-assets)). | | **Dataset** | A container for tabular or array data that supports versioned snapshots and analysis. | | **Dataset version** | An immutable snapshot of a dataset, which Dataerai preprocesses so it can be explored and visualized. | ## Storage | Term | What it means | | -------------- | ---------------------------------------------------------------------------------------------------------------------- | | **Repository** | A storage location available to your organization, where bytes actually live. | | **Allocation** | The space assigned to you or a project within a repository, with a size and record limit. One can be your **default**. | ## Access | Term | What it means | | -------------- | --------------------------------------------------------------------------------------------------------------- | | **Permission** | A grant of access to a specific object, at a **Read**, **Write**, or **Admin** level. | | **Role** | Read / Write / Admin on data; Member / Admin within an organization or project. | | **Group** | A named set of people you can grant access to all at once. | | **Public** | Read-only access for any signed-in user who has the link. It does not expose data to people without an account. | ## The research record | Term | What it means | | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Person** | A canonical researcher identity, including identifiers like ORCID. | | **Work** | A scholarly publication or research output, aligned with open scholarly metadata. | | **Grant** | A research funding award, with its funder, dates, and amount. | | **Funding agency** | The funder behind one or more grants. | | **Provenance** | The recorded history of how data came to be, captured as **relationships** between assets. | | **DID** | A citable, cryptographically [verifiable identifier](/identity/overview) (`did:dataerai:…`) given to every asset, dataset, and person, beside its internal ID. | ## Activity | Term | What it means | | ---------------- | ----------------------------------------------------------------------------------------------- | | **Transfer** | An upload or download, tracked from start to finish in the [Transfer tracker](/data/transfers). | | **Notification** | An in-app alert for a mention or an account/storage event. | ## Next steps How these pieces fit together. Quick fixes for common issues.