FAQ

What is Stackr Project used for?

Stackr Project is the project management module of Metadot, built around boards that organize your work into projects and tasks. It's a good fit for structured, repeatable work — like an IT manager running a laptop refresh or on/offboarding rollout, or a Facilities manager coordinating recurring maintenance across multiple school buildings. You can set up boards manually with Projects, plan ahead with Scheduled, or start faster with Templates.

What can each role do?

There are three roles: Viewer, Member, and Admin. A Viewer has read-only access to the boards they've been granted, so they can follow progress without making changes. A Member can create and edit projects and tasks, but only on boards they can access. An Admin has full control over app-wide configuration — templates, taxonomy, and publishing — but does not automatically get access to every board; they still need to be granted access like anyone else.

How does access to boards actually work?

Access in Stackr Project is board-level, not workspace-wide. Being an Admin gives you configuration power over things like templates and taxonomy, but it does not bypass a board's own permissions — you still need to be added to a board to see or edit its contents. This means an IT manager can run a sensitive offboarding board without every workspace Admin automatically having visibility into it.

Who can see a board I create?

Only people who've been explicitly granted access to that board can see or work in it, based on their role — Viewer, Member, or Admin-level configuration rights layered on top. This is useful when a Facilities manager wants to keep a maintenance board scoped to specific staff at a specific school, rather than exposing it to the whole organization.

What's the difference between Projects, Scheduled, and Templates?

Projects is where you build and manage boards day to day — creating tasks, tracking progress, and organizing work. Scheduled helps you set up recurring or future-dated work, which fits naturally with things like routine building maintenance. Templates let you standardize a board layout once — like a laptop refresh checklist — and reuse it instead of rebuilding it each time.

How do I run recurring work without recreating it every time?

Use Templates to define the standard structure of a recurring project, then use Scheduled to have that work generate on a repeating basis. This is especially useful for a Facilities manager handling ongoing maintenance across several buildings, since the setup only needs to happen once.

Can actions on a board trigger other things automatically?

Yes. Actions you take in Stackr Project can trigger automations, such as sending an email, creating a follow-up task, updating a field, or firing a webhook — all without any code. This lets you build workflows like automatically notifying someone when an onboarding task is completed.

How does Stackr Project connect to the rest of Metadot?

People in Stackr Project are recognized the same way across all of Metadot — a collaborator on a board is the same profile as a CRM contact, Tickets requester, or InvoiceMe customer, so you never re-enter someone's information. Everything you create in Stackr Project is also findable through workspace-wide search, and access always follows your workspace's roles plus this module's own board-level permissions.