Skip to content
Learn › Start here: open the docs menu

Mammoth core ideas: workspaces, projects, datasets, views

Mammoth organises data work in seven nested levels: a workspace holds projects, a project holds datasets, each dataset holds batches of rows and opens in one or more views, and each view has a pipeline of tasks. Data flows from a source into a dataset, through a view's pipeline, and out to an export or dashboard. Learn views and pipelines first; the rest builds on them. The Quick start shows these ideas at work on a small file.

Seven nested levels: Workspace, Project, Dataset, Batch, View, Pipeline, Task, each with its container and security level

The seven levels at a glance

LevelContainerWhat it holdsAccess set byRoles
1WorkspaceProjects, users, planWorkspace membershipWorkspace Owner, Workspace Member
2ProjectDatasets, connections, automations, dashboardsProject membershipProject Admin, Project Editor, Project Viewer
3DatasetBatches and viewsThe projectProject role
4BatchRows of dataThe projectProject role
5ViewA pipelineThe projectProject role
6PipelineTasksThe projectProject role
7TaskOne operationThe projectProject role
Data flow diagram: Data Source to Dataset with Batches, to View, to a Pipeline of five Tasks, to Export or Dashboard

Each level in detail: Workspaces and projects, Datasets and batches, and Views, pipelines and tasks.

Worked example with all seven levels

  1. Workspace: "Acme Corp" (your company)
  2. Project: "Q4 Sales Analysis" (your team's area)
  3. Dataset: "Salesforce Opportunities" (imported data)
  4. Batch: "December import" (this month's data)
  5. View: "Sales Pipeline Analysis" (where you work on it)
  6. Pipeline: five tasks transforming the data
  7. Tasks: Conditional Filter, Remove Duplicate Rows, Join, Math Function, Group & Pivot

Industry examples

These examples are illustrative.

Financial services: monthly regulatory reporting
Workspace: Example Bank
Project: SOX Compliance
Dataset: General Ledger Transactions
Batch: December (Replace mode)
View: Regulatory Report View
Pipeline: Filter → Categorize → Validate → Aggregate
Tasks: Conditional Filter, Label & Insert Values, Data Check, Group & Pivot
Manufacturing: production quality tracking
Workspace: Acme Manufacturing
Project: Quality Control
Dataset: Production Line Data
Batch: Daily production runs (Combine mode)
View: Quality Metrics
Pipeline: Calculate defect rates → Flag outliers → Trend analysis
Tasks: Math Function, Conditional Filter, Window Function
Hospitality: multi-property revenue analysis
Workspace: Example Hotels
Project: Revenue Management
Dataset: Property Management System Data
Batch: Nightly revenue reports (Replace mode)
View: Executive Revenue
Pipeline: Combine properties → Calculate RevPAR → Compare periods
Tasks: Join, Lookup, Math Function, Group & Pivot

How the structure keeps data secure

Workspace isolation keeps each workspace separate from every other. People see a project's data only as members (Marketing doesn't see Finance's data unless they join the Finance project). Connection scoping keeps credentials with their project. Role-based permissions come from workspace roles (Owner, Member) and project roles (Admin, Editor, Viewer), plus custom roles on the Pro plan. Workspace and project actions are recorded in the Activity log. See Security: sign-in, data security, compliance and audit logs.

Common questions about Mammoth concepts

QuestionAnswer
Where is my data stored?In Mammoth's cloud, in your workspace, organised by project, dataset and batch.
What's the difference between a dataset and a view?A dataset is the imported data; a view is where you explore and transform it.
Why do I need projects?They decide who can see and change which data.
What happens to my pipeline when I add new data?The new data runs through the existing pipeline.
Can I have several pipelines on the same dataset?Yes: create more views of the dataset, each with its own pipeline.
Was this page helpful?

Something wrong? support@mammoth.io