Bring board owners, current memberships, workflow columns, allowed moves, review rules, WIP limits, task lists, source mappings, timezones and intended guest sharing.
Implementation
Configure Task and Kanban Board around your team’s operating policy.
Implementation phases
- Agree ownershipBoard Owner
- Configure workflowTeam and ERP.ai
- Bring work acrossTeam and ERP.ai
- Review the first handoffBoard Owner
Phase 1 · Board Owner
Agree ownership
The Board Owner sets internal roles, guest policy and board timezone.
| Role | Screens |
|---|---|
| Board Owner | 11 |
| Member | 7 |
| Reviewer | 3 |
| Viewer | 5 |
| Guest | 1 |
Role permissionsRoles and permissions →
Phase 2 · Team and ERP.ai
Configure workflow
Review columns, lanes, moves, checklists, WIP and protected destinations.
Phase 3 · Team and ERP.ai
Bring work across
Validate mappings and preserve task identity, dependencies and history.
Phase 4 · Board Owner
Review the first handoff
The Board Owner tests allowed moves, denied guest access, independent review and the last capacity slot.
Version workflow changes with a valid mapping for active tasks. Invalidate affected requests when protected task or workflow facts change. Preserve events, revoked grants, checklist waivers and prior completion cycles.
1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.