Abilities

Sixty-four switches, all of them off, per site.

The model

An ability is one thing the plugin will allow: read a page, edit an Elementor widget, upload to the media library, write a file, publish. There are sixty-four of them, and every one is off when a site is linked.

They are per site. Your own site and a client's can have entirely different answers, and turning something on for one says nothing about the other.

See all sixty-four, by group →

Where the check happens

On the site, in the plugin, not in the app. That matters: the app deciding what it is allowed to do is a promise, while the site deciding is a control. If the credential were ever used from somewhere else, the same limits would still apply.

What the agent is told

The app tells the agent which abilities are on, up front. Without that, an agent spends a conversation discovering refusals one at a time and guessing at workarounds, which is both slow and exactly when it starts doing something creative you did not ask for.

Three things no ability turns on

Some things are not switches, because there is no configuration under which they are a good idea:

• Running arbitrary PHP
• Injecting unsanitised CSS
• Writing raw custom fields without going through the handler that knows what they mean

These are not hidden behind an advanced toggle. They are not there.

A sensible starting set

Reading, and editing drafts. That is enough to find out whether the agent understands the site at all, and nothing a visitor can see changes while you do it. Publishing, media and file writes are worth adding one at a time, after you have watched it work.