OPERATIONS / RESPONSIBILITIES AND ACCESS
A written responsibility.
Access that matches it.
A charter can state that a human validates. But the software must also tell the roles apart, apply their rights and keep the state of the decision.
Written by Saphan · 7 September 2026
Link each operation to a role
Start from a specific workflow. Who can view the supporting documents, prepare a proposal, approve it and carry out the operation? A small team can combine several roles, but the system must know which one is acting. The person in charge of operations is not automatically authorized to make a business decision.
Fictional example: an assistant prepares an order change. It reads the authorized references and produces a draft. The sales manager approves the changes. The connector executes only the approved operation, not a new version modified in the meantime.
Check the permissions in the tools
Use identities suited to the workflow, without reusing a person’s administrator account out of convenience. Distinguish read from write, then examine the accessible scope: cases, teams, actions. An instruction in the prompt does not remove a right granted to the connector.
Using an ordinary account, test one permitted operation and one refused operation. Then remove an access right and check its effect on new requests, existing sessions and pending processing. Note the delays or dependencies you observe instead of assuming immediate revocation everywhere.
Keep a trail that lets you resume
For an important action, link the request, the prepared version, the approval, the execution and the result in the target software. A case identifier makes it possible to follow the workflow without copying the full documents into every log.
Define who looks at these trails, why, and for how long they are needed for the intended operation. Secrets have no place in them. A “success” message must be traceable to a real state, and an uncertain attempt must remain recognizable.
Try out stopping and resuming
The stop button can suspend new actions without undoing those already carried out. Document this difference. In an agreed exercise, interrupt the workflow, find the operations in progress and resume without running anything twice. A named person in charge then decides whether to reactivate the service. Saphan can build these mechanisms together with the connection, then hand them over to the people who run it.