Features / WordPress request history

Know what was asked. See what actually happened.

The request ledger connects a prompt to its targets and operations. Use it when a teammate or client asks for the history behind a change.

In practice

How you use it

01

Find the original request

Review requests by their state, including queued, running, completed and failed work. The request remains the starting point for its per-site detail.

02

Read the operation timeline

Open the events behind a result, including approvals where used. A partial failure stays different from a fully completed request.

03

Track workspace usage

Internal records include charged credits where applicable. Requests made with the team's own OpenRouter key do not consume managed IrmaWP credits.

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.

WordPress request history

The request ledger connects a prompt to its targets and operations. Use it when a teammate or client asks for the history behind a change.

IrmaWP wordpress request history workspace context
Demo workspace · Dark mode
Before you connect

What to know

Is the request ledger a client portal?
No. It is the team's operational record. The Agency client portal is a separate, restricted client-facing surface.
Does a completed request prove business success?
It records the workflow outcome, not a guarantee of conversions, rankings or a perfect design. Review important results on the site.

Start with your own sites.

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