Team permissions are enforced by the API, not the screen
In Frachta, team permissions are enforced by the API itself, not just hidden in the interface, and only the owner can edit them.
The team permission matrix at /account#team decides exactly what each colleague can see and do inside Frachta, and it is not just a visual restriction: every permission is checked by the API itself before any action goes through. That means a dispatcher, driver, or accountant without a given permission is refused at the source, not merely steered away by a hidden button.
Open /account#team to see the current matrix for your team. Each member is listed alongside the permissions assigned to them, and the interface only shows the actions a given person is actually allowed to perform. If someone lacks a permission, the related option will not appear for them at all, because there is no point showing a button the API would reject anyway.
Only the account owner can edit this matrix. If you need to add, remove, or adjust what a team member can do, that change has to come from the owner's account; other members, whatever their role, cannot alter permissions for themselves or anyone else.
Because enforcement sits at the API level, you do not need to worry about someone finding a workaround through the browser, a direct link, or an old bookmark. Whatever the interface would hide, the API would refuse anyway, so the two layers always agree.
This protects you from the situation where a permission looks fine on screen but the underlying access is inconsistent, or where a team member ends up performing an action they were never meant to have, simply because a screen element was overlooked. With the matrix enforced end to end, what you see is what is actually allowed.