Roles aren't about team size
A team of three needs the same kinds of decisions as a team of thirty: who approves an offer, who has access to invoicing, who can add a new client. The difference is that at small scale, you can handle it with two or three roles, not ten.
A simple three-role model
In Voltzzflow, this translates directly into roles and permissions you assign to each teammate:
- Owner: sees everything, manages billing and the subscription, adds or removes people from the team.
- Project manager: manages their own clients and projects, but has no access to billing settings.
- Collaborator: sees and works only on what's been assigned to them, with no access to other people's clients.
Why it matters even for small teams
Without clear roles, every new teammate implicitly gets access to everything, which means a mistake (deleting a project, editing a sent invoice) becomes possible for anyone, not just for whoever should actually be making that call.
Bottom line
Roles aren't bureaucracy, they're a way to make sure an accidental mistake stays small instead of becoming a problem for the whole business. Granular per-employee roles are included in the Pro plan.