Member Junction
    Preparing search index...
    • Pure fail-closed gate for approval decisions on MJ: Graph Edges (see GraphEdgeSaveNeedsApproval).

      The caller must hold Graph: Approve Edges (or an ancestor) through EvaluateAuthorizationChecks, MJ's role-based evaluation, whatever the edge's Origin. There is no bypass for any user type: an authorization that is not seeded, an empty authorization list, or a missing caller all deny, because each of them means nobody has been granted the right.

      The one exception is IsPipelinePolicyApprovedCreate. The Content Pipeline Graph stage (EntityGraphOverlayStore.UpsertEdges) saves as the run's user: the scheduler's user, whoever ran the Record Process on demand, or whoever uploaded the document, most of whom hold no Graph: Approve Edges. Its Approved status is not that user's decision but the content source's configured GraphOverlay.ConceptTaxonomyMode, so tying it to the run user would break auto-grow for every run but a developer's. The stage therefore saves inside a server operation scope instead, which no API caller can enter (see GRAPH_PIPELINE_EDGE_APPROVAL_OPERATION). Such an edge is not stamped as reviewed: no person reviewed it.

      Parameters

      Returns GraphEdgeApprovalVerdict