How teams, wrkspaces, members, permissions, and deletion work in wrkin.space.
Last updated June 7, 2026
A team is the top-level container for people and billing. Everyone on a team shares the same subscription tier and member limits.
Typical examples:
A wrkspace is a project space inside a team. Each wrkspace can enable its own module mix, so a marketing launch and an engineering roadmap can live in the same team without sharing the same tool clutter.
When creating a wrkspace (team + inline form or New wrkspace), you can start blank or pick a built-in template. Template application is atomic — either the wrkspace and all modules are created, or nothing is saved.
Team roles control who can manage billing, invite people, and configure team settings.
Wrkspace membership controls who sees a specific project’s modules and content. Add people to individual wrkspaces from wrkspace settings when they should not see every project on the team.
See Inviting members for invite flows and role details.
Only the wrkspace owner can delete a wrkspace. Owners see a Danger zone section in wrkspace Settings with a permanent delete action.
This is separate from team admin: a team owner who created a wrkspace is still the wrkspace owner for deletion purposes, even if their effective team role would otherwise limit destructive actions.
Plan limits apply per team (members, wrkspaces, modules, upload size). See pricing on the landing page for tier details.
Getting started
Create your account, spin up a team, and open your first wrkspace in minutes.
Inviting members
Invite teammates by email, manage roles, and control wrkspace access.
Wrkspace and module templates
Start new wrkspaces and Cards boards from built-in templates maintained as JSON in the repo.