6.12How the browser reports results, refusals and approvals

Every change you make in the browser is a normal directory operation. It is checked against your permissions and the operation policies, recorded in the operations log, and can trigger notifications, exactly as if it had come through the REST API.

Success and failure

A successful change is confirmed with a short message (for example "Account disabled" or "Group moved") and the object is re-read so the inspector shows its new state. A rename or move also re-reads the affected containers and reselects the object at its new location. A failed change shows the reason given by the server or the domain controller — for example a password that does not meet the domain policy — and leaves the object as it was.

Operations switched off by policy

An administrator can disable an operation for all directories or for one directory (see Chapter 10, Operation policies, attribute policies and agent supervision). If you try a disabled operation, it is refused with an error and nothing changes.

Attributes protected by policy

If a change would write an attribute that an attribute policy makes read-only or blocks — for example creating a user with a value for such an attribute — it is refused and nothing changes. The message names the attribute and the rule's reason, for example "The change cannot be made: 'mailNickname' is read-only by an attribute policy (Exchange mail routing — managed by Exchange)." A search whose filter tests a blocked attribute is refused in the same way. See Chapter 10, Operation policies, attribute policies and agent supervision.

Approval

Approval in SYNERGY Management Gateway is a control on machine credentials — API keys and AI agents — not on people. A change you make in the browser, signed in as yourself, is either carried out or refused on your permissions; it is never held for approval.

Should a change nevertheless come back as accepted for approval, the browser does not report it as an error. It shows an information message with the server's explanation that the operation is waiting for a decision, closes the dialog and leaves the object unchanged. Do not repeat the action — each repeat would queue another request. Follow it on the My Waiting Operations and Operations pages instead; see Chapter 9, Operations log, approvals and waiting operations.

Operations queued by an API key or an AI agent appear in an object's History tab with the status Awaiting approval until somebody decides them.