Managed changes
Managed changes is the separate authority that allows Flowpane to make supported changes on a connected Site. A connection allows supported observation and reporting. Connecting Flowpane does not give Flowpane permission to modify the Site. Managed changes must be explicitly enabled separately.
Use this distinction when an agency wants to observe a client Site while keeping publication with the client's existing maintainer. A Connected Site with Managed changes disabled can still report supported observations; it has no permission to perform those managed changes.
Prerequisites and permissions
You need a supported Site Integration, the correct Site association, applicable access and a role authorised for the proposed action. Confirm availability with Flowpane before making management part of a client commitment. Review the specific capability shown for the connected installation; a general connection label does not make every action available.
Supported examples
- Joomla robots.txt: an offered managed Apply can publish a reviewed, saved and validated robots.txt revision on a supported connected Joomla Site.
- Page directives: supported controls can manage a page's indexing or link-following policy. Review the page and its current effective policy before changing it.
- Flowpane-managed sitemap: supported controls manage Flowpane's own sitemap output. They do not take ownership of another plugin's sitemap.
Available actions depend on the installed package and the Site. These examples are not a general-purpose website editor, automatic CMS patcher or permission to modify every governance file. Review Joomla management and WordPress support boundaries.
Review, save and apply
Preparing Proposed content, saving a revision, validation and approval are preparation steps. Apply is a separate action that can change the Site. Read the target, exact content or policy, warning and confirmation before continuing. If Flowpane says the current evidence changed, reread it and review the proposal again rather than forcing an older decision through.
A requested change is not a confirmed public result. Check the returned state and public verification where offered. A Pending or Needs attention result means further review is needed; do not repeatedly apply the same change in response to uncertainty.
Withdraw and inheritance
Where offered, Withdraw, Inherit or a corresponding removal action releases the managed effect described by that control. Inherit allows the underlying CMS behaviour to determine the page policy. It is different from deleting the page or changing its public content. Read the confirmation because ending management and reversing a previous change can have different effects.
When Managed changes is disabled
Further managed actions are prevented. Changes already applied can remain on the website; switching off authority is not a general rollback. If you want a supported managed effect removed, review the offered withdrawal action before disabling management. If the action is no longer available, preserve the current output and contact support.
Disconnecting a Site is also distinct from withdrawing previous effects. Follow the visible lifecycle guidance; a disconnected installation cannot be treated as current evidence. Flowpane does not automatically replace unrelated CMS/plugin output.
Troubleshooting
For an unavailable action, check connection status, supported versions, role, Site access and the specific management capability. For an unexpected public result, check the observation time and which CMS, plugin or file owns the response. See connection troubleshooting.