Playbooks as a published workspace — not a folder on a laptop.
An Ansible workspace holds playbook and inventory files for a connection. You edit items, publish a revision, then runs use that snapshot. Starter scenarios (for example deploy or Linux bootstrap) can seed the tree.
How workspaces work
Same `ansible` connector entitlement as Ansible connections. Creating, updating or deleting a workspace requires approval.
Workspace files
Playbooks, inventories and related files are stored as workspace items on the Ansible connection.
Revisions
Publishing creates a numbered revision. A job can require a published revision, not an unpublished draft.
Starter scenarios
Admin can instantiate packaged scenarios (deploy web app, Linux bootstrap and similar) instead of starting from an empty tree.
Inspect
ansible.inspect-workspace loads playbook, inventory and workspace context for operators and workflow steps.
Still allowlisted
A workspace does not bypass playbook allowlists, extra-var limits or secret handling.
Ready to move beyond the chatbot?
Build AI that understands your business, follows your processes, finishes the work — and keeps token spend under your control.