Skip to content
Merulan

Approvals, sharing, and controls

Approvals, sharing, and controls bound access decisions through review, Group grants, role conflicts, and spend rules.

Approvals, sharing, and controls decide whether work may proceed. Governance & Administration owns these checks. A passed check leaves the other rules in force.

Ownership

Approvals at /governance/approvals holds Role and Purpose requests for a reviewer to decide. Sharing at /governance/sharing shows a Group's access to resources in the Workspace. Separation of Duties at /governance/separation-of-duties defines pairs of Roles that cannot be held together. Spend Controls at /governance/spend bounds the cost of work. Select the check named by the refusal.

Lifecycle

An Approval records a decision on a pending request. A denied Role request creates no active grant. Sharing persists a policy for the Group, action, and resource. Revocation removes that share. A spend policy checks its scope and time window. Its chosen response can alert, require approval, or stop work at the limit.

Warnings report approaching spend limits. They do not grant access or stop work by themselves. Hard limits and approval rules are checked before spending. The policy uses trusted Workspace, Group, caller, or other scope facts. Free-form labels added for reports cannot satisfy a hard control.

Boundaries

An Approval does not bypass Field Access, Purpose checks, or Separation of Duties. Sharing an action on a resource also leaves its field checks in force. A break-glass Role needs review after the emergency grant and still faces Role conflict checks. Treat the grant's time limit and the review as separate obligations.

Failures

An Approval can be refused because the request expired, was already decided, or would approve the caller's own Role request. A share list that fails to load does not prove no shares exist. A Role conflict blocks activation even after approval. A spend refusal needs the named budget or review condition resolved before work can proceed.

A refused Role conflict leaves no new grant and keeps its audit evidence. The administrator can inspect that refusal before changing the conflicting grants.

Recovery

For an Approval refusal, refresh the request and check its current state. Resolve Role conflicts through the administrator before seeking access again. For a share, inspect the Group roster and resource scope before changing the policy. The policy publication contract owns a change to the active rule. Publication failure preserves the prior revision.