Team permissions enforced where it matters
Frachta checks every team member's permissions at the API level, not just in the screen they see.
The team permission matrix on Frachta decides what each person on your account is actually allowed to do, and that decision is enforced by the system itself rather than just by what buttons happen to be visible on screen.
To see it, open /account?view=team. If you are the account owner, you can review the matrix and adjust what each team member is permitted to do. If you are a team member without owner rights, you will see the matrix as it applies to you, but you will not be able to change it.
The enforcement happens underneath the interface: when a team member tries an action they are not permitted to do, the request is refused by the system itself, not just hidden by the screen. In practice this means the interface naturally hides options that would be rejected anyway, so a team member generally only sees what they are actually able to use.
Because only the owner can edit the matrix, there is a single clear point of control for who can do what on the account. Team members cannot adjust their own permissions or anyone else's, no matter how the account is used day to day.
This saves you from the situation where a permission setting looks fine on screen but someone finds a way around it, or where a team member is confused by a missing option, wondering if it is a bug rather than a deliberate limit on what they can do.