Mammoth for managers: set up and oversee your data team
This plan is for managers of data teams. In your first 48 hours you create a project (Data > project selector > New Project), invite your team with roles, and watch a first workflow in the Activity Log (Monitor > Activity Log). Your team builds the pipelines; you set the boundaries and share results as dashboards, docs and slides, and see dashboard audience (who read a dashboard and what they asked).
Then share results with an executive dashboard, check adoption in the Activity Log, and control sources and cross-project sharing in Control data sources and share data across projects.
What a Project Admin can do
When you create a project, you become its Project Admin: you control who can do what, and Project Editors control how they do it.
| Capability | Project Admin | Project Editor | Project Viewer |
|---|---|---|---|
| Add or remove project members | ✓ | ✗ | ✗ |
| Rename or delete the project | ✓ | ✗ | ✗ |
| Create, update or delete connections | ✓ | ✗ | ✗ |
| Start datasets from existing connections | ✓ | ✓ | ✗ |
| Add, edit or delete datasets, views and pipelines | ✓ | ✓ | ✗ |
| See Data Library items | ✓ | ✓ | ✓ (read-only) |
Project Admins also invite people who aren't in the workspace yet and remove access when someone leaves. On the Pro plan you can create custom project roles (Members, roles and custom roles). Name a backup admin for when you're away.
Hour 1: create a project and pick a first use case
- Click Data in the left sidebar.
- Click the down arrow next to the project name at the top, then New Project.
- Name it, for example "FP&A Monthly Reporting" or "Operations Analytics".
- Leave Who can access on Only me for now (the default).
- Click Create Project.
Mammoth switches you into the new project. If your plan's project limit is reached, New Project is blocked. See Projects.
Managers mostly work at the project level: the workspace is your subscription, the project your team's work area, datasets hold the data, views are where the team transforms it, and dashboards are what you share. Migrate one recurring process first as your proof of value, such as a monthly close report, a weekly operations dashboard, or a quarterly analysis that copies data between five spreadsheets.
Hours 2 to 4: invite your team and set project settings
Start with one or two team members; they can help onboard the rest.
- In the project selector, click More options (three dots) next to your project.
- Click Manage Users.
- Add the workspace members you want, or type the email of someone who isn't in the workspace yet.
- Assign roles: Project Editor for most, Project Admin for backup admins, Project Viewer for read-only access.
Added members appear under Shared with, by role. Then, in Project Settings:
- Check the Project Name and Project colour.
- Set Dates (US, UK / Europe, International (ISO) or Not set).
- Choose Who can access: everyone in the workspace, the people you select, or only you. Starting restrictive is easier than revoking access later.
- Click Save changes.
The project menu depends on your role: Project Admins see Project Settings, Manage Users, Leave Project and Delete Project; Project Editors and Project Viewers see Leave Project, with Delete Project greyed out; Workspace Owners not in the project see Manage Users and Join Project. Every setting: Set up your workspace.
Hours 24 to 48: watch a first workflow
- Have a team member upload a recurring file, such as last month's sales report.
- Watch them build a pipeline, to understand the process.
- Review the Activity Log to see their actions recorded.
- Hold a short team sync on how this could standardise your recurring workflow.
Standardise recurring workflows with a reference pipeline
- Identify workflows that repeat: monthly close, weekly operations summaries, quarterly board packs, recurring client deliverables.
- Document the current process with the person who does it: where the data comes from, what changes, the output, and how long it takes.
- Build a reference pipeline with your most technical team member. It becomes your template.
- Replicate it: others use Copy pipeline in Pipeline Version history, or copy single tasks and use Paste below, then adapt. See Edit, reorder and copy tasks.
- Monitor adoption in the Activity Log each week: who uses the reference pipeline, where people deviate, and who still works by hand.
Grow the team over months 1 to 3
Roll out in stages: champions (one or two people) in weeks 1 and 2, early adopters (three or four) in weeks 3 and 4, who help train the full team in weeks 5 to 8. Keep a library of reference pipelines, each with a clear name, notes on the business logic, example uses and an owner. Measure time, error rates, rework and active users against a baseline recorded before automating.
After 3 to 6 months, add scheduled Dataset Refreshes (daily, weekly, monthly), pipeline templates (Save as template in Pipeline Version history downloads the pipeline as a file the team can apply to another view), and dashboard templates (see Start from a template). If you use Tableau or Power BI, send prepared data with the Tableau Server/Cloud export (Team and Pro), or publish it to a Mammoth-managed database your BI tool reads. See Send data to a database or BI tool.
Related
- Set up your workspace: invite users and configure projects.
- Share an executive dashboard: access options for boards and clients.
- Review team activity: the Activity Log and offboarding.
- Pick your path: the plans for analysts and technical users.
Something wrong? support@mammoth.io