Projects

This section explains projects for Workspace Owners, Workspace Members, and Project Admins. Start with Creating a project if you need a new project, or read the concepts below first.

A Project is an organizational container within a Mammoth workspace. It groups related datasets and automations together and controls who on your team can access them.

Every dataset in Mammoth belongs to exactly one Project.

What projects do

Projects let you:

• Organize data: Group datasets and automations that belong to the same initiative, team, or business area
• Control access: Decide who in your workspace can see and edit each project
• Set shared defaults: Choose how the project reads ambiguous dates in uploaded files (day first or month first) and the starting display format for new date columns

Project concepts

How workspaces and projects relate

WORKSPACE
 └── Project A  (e.g. "Marketing Analytics")
 │    ├── Dataset: Campaign Performance
 │    ├── Dataset: Ad Spend
 │    └── Automation: Weekly Report Refresh
 │
 └── Project B  (e.g. "Finance Reporting")
 │    ├── Dataset: Revenue by Region
 │    └── Dataset: Budget vs Actuals
 │
 └── Project C  (e.g. "Product Insights")
      └── Dataset: User Engagement

A workspace can contain many projects. Each project is independent. Its datasets, access settings, and team members are configured separately.

Access levels

When you create or edit a project, you set who can see it:

Access level	Who can see it
Everyone in this workspace	All current and future workspace members
Some people in this workspace	Only the users you explicitly select
Only me	Only you (the project creator/admin)

You can change access at any time from Project Settings.

Project roles

Two roles control what people can do inside a project:

Role	What they can do
Project Admin	Manage settings, share the project, add or remove members, delete the project, plus all Editor capabilities
Project Editor	Access and work with all data and pipelines in the project

For the full permission breakdown, see Project roles and permissions.

Project lifecycle

CREATE PROJECT
      ↓
SET ACCESS LEVEL (Everyone / Some people / Only me)
      ↓
INVITE COLLABORATORS (if needed)
      ↓
ADD DATASETS & AUTOMATIONS
      ↓
MANAGE SETTINGS (rename, recolor, update access)
      ↓
SHARE WITH NEW MEMBERS (as team grows)
      ↓
DELETE PROJECT (when no longer needed; irreversible)

Core tasks

Task	Where to go
Create a new project	Project selector → New Project
Change project name, color, or date settings	Project manage menu → Project Settings
Change who can access the project	Project manage menu → Project Settings
Add or remove team members	Share button (top-right) or Project manage menu → Manage Users
Change a user's role	Share Project modal → role dropdown next to each user
Leave or delete a project	Project manage menu → Leave Project / Delete Project
Understand what each role can do	Project roles and permissions reference

Who can create projects

All workspace roles can create projects:

• Workspace Owner
• Workspace Member

The creator is automatically assigned the Project Admin role on the new project.

In this section

• Creating a project: Create a project, then leave or delete it
• Project settings: Configure name, color, date handling, and access
• Sharing a project: Add team members and manage their roles
• Project roles and permissions: Full permission reference

For workspace-level settings and users, see Workspace management.

---

Need help? Check the troubleshooting guide or contact Mammoth Support.