Roles & Permissions
Who can do what in Stackr Project
Stackr Project has the following roles and permissions:
| Role | Description | Permissions |
|---|---|---|
| Viewer | Read-only access to boards the user has been granted on | board:read |
| Member | Can create and edit projects and tasks (on accessible boards) | board:manage, task:manage |
| Admin | Full app-config access (templates, taxonomy, publishing). Does NOT bypass board-level ACLs. | board:publish |
Each project also has a separate access level:
| Project access | What it allows |
|---|---|
| Viewer | Read the project and its cards. |
| Editor | Create and edit cards, without changing columns or sharing. |
| Maintainer | Manage project settings, columns, tags and sharing. |
Whoever creates a project becomes a Maintainer of it, and so does anyone appointed project manager. There is no separate owner: the creator and the manager are ordinary Maintainers in Manage access, and any Maintainer can change their access as long as at least one Maintainer remains. A manager must be an active workspace member with Stackr Member or Admin access. Changing the manager doesn't remove the previous manager's access; change it in Manage access if needed.
If everyone who could maintain a project leaves, a workspace owner or admin can name a new Maintainer from Settings → Unmanaged items, without gaining access themselves.
Your app role still limits what you can do. An app Viewer cannot edit a project even if they are a Maintainer of it. Publishing publicly requires app Admin plus project Maintainer. Archived projects must be restored before changing cards, columns or sharing. Workspace administrators cannot automatically read private projects.
Duplicating a project makes the person creating the copy its manager and a Maintainer of the copy. Folder access and the Keep sharing & access option determine its other collaborators.
Was this page helpful?