The first question will not be about marketing

The question you will be asked

You can make the case for this in a meeting. Someone above you will then ask what it is allowed to do, who approved it, and what happens when it is wrong. If the answer is that it posts things, the conversation ends there and the budget does not move.

So this page is about governance, because governance is the actual work of adopting agent software inside a larger organization.

Governance you can point at

Every agent follows written permission rules across five tiers: read, propose, stage, execute, destructive. By default, publishing, sending, spending, merging code and changing a lead record all wait in one approval queue. Research and internal reporting run on their own and are logged, so autonomous activity is visible rather than invisible.

Scale adds the controls a larger team asks for first: bulk approvals for batches already reviewed, audit logs, and API access so the record can live wherever your reporting lives. Autopilot exists on Scale, is off by default, and is enabled per eligible action, which makes it a decision about a named category of work rather than a switch that turns the team loose.

Where the ceiling is

Say it before someone else discovers it. The top plan is Scale: 10 seats, 5 projects, $247 a month or $205 billed yearly. Single sign-on is not listed among the Scale features, and there is no per-department tenancy. On certification, the security page states that certification work is still in progress and does not name which certification, so treat any specific ask as unanswered until someone confirms it in writing. Either way there is no report to hand to your security team today.

If procurement needs those before a pilot, this is not the tool for that process yet, and starting a review you cannot finish wastes months. What Scale does support is a marketing team running five outcomes at accelerated cadence with 7,500 credits and 100 tracked prompts, under approval rules you write, with a log of what happened.

One queue is the whole design

The approval queue is a single queue, not a per-department workflow engine. For a marketing team of ten that is the feature: one place to see what is waiting, one record of who released it. For a matrixed organization with regional sign-off chains, that is a real constraint and not a small one.

What rules this out today

If single sign-on, departmental isolation or a compliance certificate is a precondition rather than a later question, this will not clear that gate today. Nor will it suit a team that wants agents operating without a named approver. A procurement-led rollout that begins with the security questionnaire will stall here.