Settings: Workspace

Plans

How to review, approve or reject changes an agent has proposed for your workspace.

Plans lists the changes an agent has proposed for your workspace. Nothing in a plan is written until someone approves it, either you here or an operator at your agency in Plans and blueprints. A plan never deletes anything.

Who can open it

Only owners and admins. Plans is not shown in the Settings menu for anyone else, and anyone else who opens the address is sent back to Settings. Only plans for this existing workspace appear here. A plan that creates a new workspace stays with your agency.

The list

Plans waiting for approval are listed first. Each row shows where the plan came from (for example, the template it was built from), its state and when it was made. The states you can see are:

State	Meaning
Planned	Drafted, not yet sent for approval.
Waiting for approval	Ready for you to decide.
Applying	Approved and being written now.
Applied	Written in full.
Rejected	Turned down. Nothing was written.
Stopped at a failure	Writing stopped partway.
Expired	Not decided in time.
Out of date	Things changed since it was made.

Review and decide a plan

Open a plan from the list. The header shows its state and, while it is waiting, when it expires.
Read the confirm card, which lists each change with its value before and after.
Check the other sections. Not yet lists changes that approving will skip, each with what has to happen first. You also see how many things are already as the plan wants, and anything the plan leaves as it is.
Choose Approve and apply to write the changes. You see "Approved and applied." when it has finished.
To turn it down, choose Go back on the card, then Reject it and confirm. Nothing is written, and the agent has to make a new plan. If a plan writes nothing because everything is already true or blocked, choose Close it instead.

Tokens a plan issues

If an approved plan creates API tokens, they are shown once under Tokens issued. Copy them straight away, because PYLO keeps only a fingerprint and cannot show them again. You manage tokens afterwards on API tokens.

What changes elsewhere

Approving writes the listed changes to your workspace immediately, so they show up wherever that setting is used in PYLO.