Guides
Care permissions explained
Understand monitoring, safe repairs, change proposals and the boundary around customer-content data.
This guide follows the information, responsibility and next action — not a disconnected feature list.
Monitor only
Care can observe the narrow technical health signal sent outward by the site. It can identify versions, connection state, background work and the configured backup signal without becoming another location for business records.
Allow safe repairs
The account owner may permit a defined set of safe repair actions. The permission is explicit, the action is attributed and the result is written to the activity history.
Allow change proposals
Care may prepare a larger change, but an authorised person on the customer side still decides whether it can be completed.
The data boundary
Orders, customers, messages, tickets, invoices and prices are not fields in the Care report. The outward report is not an incoming support webhook and does not require Care to store the WordPress password.
Use this with one real process.
Do not redesign the whole business at once. Choose one current example and test the route.
- 1Confirm the current Care permission
- 2Check the latest technical signal
- 3Keep customer-content fields outside the report
- 4Review every proposed change locally
- 5Use the activity history after any action
See the process inside a working Console.
Use the interactive sector demos to follow customers, work, communication, team activity and outcomes in context.
