FAQ

What is Stackr Project used for?

Stackr Project is Metadot's project management module, built for planning and tracking work across boards. It's a good fit for scenarios like an IT manager running a laptop refresh or on/offboarding rollout, or a facilities manager coordinating recurring maintenance across multiple school buildings. You organize work using Projects, set up recurring work with Scheduled, and standardize repeatable setups with Templates.

What can each role actually do?

Viewers have read-only access to the boards they've been granted, so they can follow progress without editing anything. Members can create and edit projects and tasks, but only on boards they can access. Admins have full app-config access, including Templates, taxonomy, and publishing settings, but that config power doesn't extend to board content they haven't been given access to.

How does access to boards actually work?

Access in Stackr Project is board-level: being a Member or Admin doesn't automatically mean you can see or edit a given board's contents. Admins configure the module's shared settings, like templates and taxonomy, but still need to be granted access to a specific board to work in it. This keeps sensitive rollouts, like an on/offboarding board, visible only to the people who need it, regardless of their role.

Does being an Admin mean I can see everything?

No. Admin gives you control over app-wide configuration such as templates, taxonomy, and publishing, but it does not bypass board-level ACLs. If you need to view or edit a specific board, someone still needs to grant you access to it, just like any other role.

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

Projects is where your day-to-day boards, tasks, and progress tracking live. Scheduled is for recurring work, like the facilities manager's routine building maintenance, so it doesn't have to be recreated manually each cycle. Templates let you standardize a repeatable setup, such as a laptop refresh checklist, so new projects start with consistent structure.

What does a typical day-to-day workflow look like?

Most day-to-day work happens inside Projects: Members create tasks, update status, and move work forward on the boards they have access to. Recurring efforts, like monthly maintenance rounds, run through Scheduled so they regenerate automatically instead of being rebuilt each time. Viewers check in on progress without making changes, keeping oversight and execution cleanly separated.

Can Stackr Project trigger automations?

Yes. Events in Stackr Project, like a task moving to a new status or a project being created, can trigger no-code workflows elsewhere in Metadot. That means an update on a board can automatically send an email, create a follow-up task, update a field, or fire a webhook without manual work.

How does Stackr Project connect to the rest of Metadot?

The people collaborating in your projects are the same identity records used across Metadot, so a Stackr collaborator can also be a CRM contact or Tickets requester without duplicate profiles. Projects, tasks, and boards are indexed in workspace-wide search, making them findable alongside records from other modules. Access still follows the workspace RBAC model layered with Stackr's own board-level permissions.