Permissions & roles
VeloBoard has two layers of roles: organization roles decide who can admin the workspace, and team roles decide who can manage a specific team.
Organization roles
Every user has exactly one org role. From least to most privileged:
| Capability | Member | Team leader | Admin | Owner |
|---|---|---|---|---|
| Create and edit own cards | ✓ | ✓ | ✓ | ✓ |
| Vote and comment | ✓ | ✓ | ✓ | ✓ |
| Create boards | ✓ | ✓ | ✓ | ✓ |
| Create and manage own teams | — | ✓ | ✓ | ✓ |
| Configure Jira projects for own teams | — | ✓ | ✓ | ✓ |
| Invite and remove org members | — | — | ✓ | ✓ |
| Manage all teams | — | — | ✓ | ✓ |
| Org-level Jira credentials | — | — | ✓ | ✓ |
| Configure SSO and SCIM | — | — | ✓ | ✓ |
| Change member roles below Owner | — | — | ✓ | ✓ |
| Assign the Owner role | — | — | — | ✓ |
| Billing and plan changes | — | — | — | ✓ |
Member
The default role for everyone who joins the org. Members can write cards, vote, comment, and create boards.
Team leader
A member promoted to team-leader level can create teams and run the teams they lead — add members, set each team’s Jira projects, configure field defaults per issue type. Team leaders do not get workspace-level admin permissions.
Admin
Admins can manage all org members, all teams, and all integrations. They can configure SSO and SCIM. Admins can change any other user’s role except they cannot grant the Owner role.
Owner
The workspace owner has every admin permission plus exclusive rights over billing and the Owner role itself. Owners are the billing contact with Stripe.
Team roles
Within each team, users are either a member or a leader. Team leaders can manage that specific team (add/remove members, rename, assign Jira projects, configure Jira field defaults) without needing org-level admin.