Who can do what, enforced by the database. Permissions are capabilities granted by roles. A member's effective permissions in a project are the union of the active roles they hold there.
execute_code is separate: granted per project and per role, default off for every role. See Code nodes.
How far a platform administrator reaches into projects is itself a setting: no project access, viewer, or owner. Administrators can grant execute-code but do not hold it implicitly.
For financial-grade separation of duties, avoid giving one person both Editor and Approver on a production-critical project. If unavoidable, require an independent reviewer per change, review the audit trail, and make the elevated access time-bound.
This site needs JavaScript for the full experience. Every page above is reachable without it.