Platform Responsibility & Approval Gates

Every user in Growth OS has a role that defines what they can read, propose, approve, and execute. These boundaries aren't arbitrary — they reflect accountability. If you can approve something, you're accountable for what you approved. If you can only propose, someone else carries the accountability for approving it. Understanding your permission level means understanding what you're responsible for.

Approval gates create a deliberate pause before consequential actions. When Growth OS routes something through an approval gate, it's because the action — publishing content, updating a client record, executing a campaign change — has enough impact that a second person should confirm it. This protects the organisation from errors, and it protects you from being solely accountable for an outcome that affects others.

The platform will block actions outside your permission level — you won't be able to execute them. But it's equally important to understand why this matters beyond just "the system won't let me". Acting outside your permission level — even informally, such as asking an admin to do something on your behalf without proper process — breaks the audit trail. The audit log exists to show who decided what and when. Workarounds corrupt that record.

Growth OS has four execution modes: GOVERNED_PUSH (AI proposes, human approves, then executes), MANUAL_TASK (creates a task for human action), READ_ONLY (no writes at all), and UNAVAILABLE (feature not accessible). Your role and the current platform configuration determine which mode applies to each action. If you find an action is in READ_ONLY or UNAVAILABLE when you expected otherwise, check with your admin rather than looking for a workaround.