What you can set up
- Projects — one workspace per team; each project has its own backlog, settings, and members.
- Issues — tasks, bugs, stories, and epics with priorities, assignees, due dates, and workflow states (Backlog → Todo → In Progress → Done).
- Modules — group related issues into feature buckets (e.g. “Payments”, “Onboarding”).
- Pages — lightweight project wiki pages for specs, runbooks, and meeting notes.
- Cycles — time-boxed sprints when enabled on a project.
- Views & filters — saved board/list views by assignee, priority, label, or state.
- Labels & estimates — tag issues and optionally size work for planning.
Day-to-day use
- Create and assign issues; move them across the board as work progresses.
- Link issues to modules to track feature-level progress.
- Use project pages for design docs that sit next to the backlog.
- Check overdue and blocked items from list or board views.
- Comment on issues and @mention teammates for async updates.
Access & maintenance
- Plane uses a separate login — you need a workspace invite (not Authentik SSO).
- Workspace admins invite members by email; project leads add members per project with roles (Guest, Commenter, Contributor, Admin).
- Admins use God Mode for workspace-wide email, branding, and instance settings.
- Webhook notifications can route issue events to external systems (e.g. notify service).