Which plans include approval flows?

Approval flows, reviewers and comments are part of the Scale plan, on all three of its credit tiers, and of Enterprise. Launch, Grow and Free workspaces don't have them.

Limits by plan#

Scale tiers are named by their monthly credits, as on the pricing page.

On Scale 75,000, each review stage takes Any one approver. Every preset fits the smallest tier.

How the limits count#

• Approval flows counts the flows in use. Archived flows don't count, so archive one to add another.
• Stages per flow counts the stages in use in one flow. Archived stages don't count.
• History is the activity of your templates and flows: moves, approvals, change requests and blocked renders. Older activity is removed after the number of days above. Comments stay.
• Reviewers take a seat, like members. Your plan's team members are on the pricing page.

When you reach a limit, the Approvals page says so, like "Your plan includes 3 approval flows. Archive one to add another."

After a downgrade#

Moving to a smaller plan is never blocked, and no flow or stage is deleted.

• Fewer approval flows: the first flows in your list stay active, default flow first. The rest are over your plan's limit.
• Flows over the limit can be opened, commented on and archived. Nothing in them can be added, moved, approved or changed, and they don't block automation or lock designs.
• Bring them back by archiving or upgrading. Archive an active flow and the next one in the list becomes active. Upgrade and they're all active again.
• Fewer stages per flow: the stages you have keep working. You can't add one until the flow is under the new limit.
• Features the new tier leaves out: stages already set to Every approver, A set number of approvers or Keep rendering the approved version keep working. Switching a stage to one of them is refused.
• History follows the new plan, so activity older than it keeps is removed.
• A plan without approval flows hides Approvals from your team and blocks nothing. Your flows and stages are kept for when you upgrade, and so is a year of history.

A flow over the limit says so on its board: "This approval flow is over your plan's limit of 3 approval flows. It can't be changed, and its templates don't need approval for automation."

Comment and request limits#

These apply on every plan that has approval flows:

• Comments: one person can post up to 20 comments a minute and 200 an hour in the Orshot app. Past that, the app asks you to wait a moment and try again.
• @mentions: one comment can mention up to 20 people.
• Approvals API: up to 120 requests a minute for each API key or person in a workspace.

The Approvals API#

The Approvals API is available on Enterprise plans, or through first-party apps (the Orshot app and the Orshot MCP server).

On Scale, you work with approval flows in the Orshot app, and the Orshot MCP server acts as the person who connected it. Calling the Approvals API with an API key or your own OAuth app needs an Enterprise plan, with each access level turned on for your workspace. Start with the Approvals API overview, or contact us about Enterprise.

Needing approval for automation doesn't need the Approvals API. On Scale and Enterprise, it applies to all automation, from the REST API and SDKs to n8n, Make, Zapier and the Playground.

Sandbox workspaces#

Partner sandbox workspaces don't have approval flows.