Features / Team approvals and change review

Review risky changes before they run.

Internal approvals let your team check proposed work and file diffs where available. They are a safety control, not a promise that every action can be undone.

In practice

How you use it

01

Review the target and change

Check the intended site, request and available diff. Approval should be based on the proposed action, not just the original prompt.

02

Use the right reviewer

Workspace roles determine who can approve and execute work. The request history records decisions so a teammate can understand what happened later.

03

Apply site policy

Use linked staging where a workflow and policy require it. Staging must already exist and be connected; IrmaWP does not create a hosted clone for you.

Inside the workspace

Keep the work in view.

An actual screen from the IrmaWP demo workspace. The workspace includes sample history; available actions depend on your plan, role and site connection.

Team approvals and change review

Internal approvals let your team check proposed work and file diffs where available. They are a safety control, not a promise that every action can be undone.

IrmaWP team approvals and change review workspace context
Demo workspace · Dark mode
Before you connect

What to know

Are these approvals the same as client sign-off?
No. These are authenticated team safety approvals. A separate client sign-off experience is planned, not part of the current portal.
Must I buy Agency to keep safety reviews?
No. Internal safety checks are not removed on lower plans. Agency's client-facing portal is separate from the team's safety workflow.

Start with your own sites.

Connect a small portfolio, check the tools you need, and choose the plan that fits your team's work.