{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T07:59:18.009Z",
  "record_id": "VXI-EXT-PROCUREMENT-DATABRICKS-BINDING-01-v1",
  "record_kind": "external_reference",
  "title": "Databricks catalogs: Workspace binding and user grants",
  "system": "Databricks",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a SELECT grant prove an agent can access a catalog from any Databricks workspace?",
  "near_questions": [
    "Can a catalog binding override SELECT access?",
    "Is a catalog open to every workspace by default?",
    "Does the default workspace catalog behave differently?",
    "Can a binding be read-only?",
    "Which metastore contains the catalog?",
    "Which workspace will the agent use?",
    "Does binding a workspace grant user privileges?",
    "Can a workspace-local admin group apply elsewhere?",
    "What proves the current isolation mode?",
    "Who can change workspace bindings?",
    "When should an access claim remain unresolved?",
    "Can I retain the catalog-binding evidence?"
  ],
  "supported_claims": [
    {
      "claim": "Catalog binding can deny access from an unassigned workspace despite a user's explicit grants. A binding can also restrict that workspace to reads. Ordinary catalogs are open across the metastore by default, while automatically created workspace catalogs have a narrower default. Both binding and identity evidence are needed.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "Catalog binding can deny access from an unassigned workspace despite a user's explicit grants. A binding can also restrict that workspace to reads. Ordinary catalogs are open across the metastore by default, while automatically created workspace catalogs have a narrower default. Both binding and identity evidence are needed.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Databricks workspace-catalog bindings",
    "source_url": "https://docs.databricks.com/aws/en/data-governance/unity-catalog/access-control/workspace-catalog-binding",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-DATABRICKS-BINDING-01-v1",
    "candidate_record_sha256": "50148597db7f01a31cbad91547eafedf764a94f589cf5e2f022939f3dfebf21a",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "Catalog binding can deny access from an unassigned workspace despite a user's explicit grants. A binding can also restrict that workspace to reads. Ordinary catalogs are open across the metastore by default, while automatically created workspace catalogs have a narrower default. Both binding and identity evidence are needed.",
    "required_buyer_context": "Catalog type, isolation mode, workspace binding and user privileges. Effective buyer configuration and dated operational evidence are required.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-16",
    "claim_to_check": "A catalog grant establishes access from every workspace.",
    "documented_statement": {
      "status": "documented",
      "statement": "Catalog binding can deny access from an unassigned workspace despite a user's explicit grants. A binding can also restrict that workspace to reads. Ordinary catalogs are open across the metastore by default, while automatically created workspace catalogs have a narrower default. Both binding and identity evidence are needed.",
      "source_ids": [
        "databricks-binding"
      ]
    },
    "buyer_evidence_required": [
      "Catalog isolation mode and assigned workspaces.",
      "Binding access level.",
      "User grants and metastore association."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Require both workspace and identity scope before asserting access."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "databricks-binding",
        "url": "https://docs.databricks.com/aws/en/data-governance/unity-catalog/access-control/workspace-catalog-binding",
        "final_url": "https://docs.databricks.com/aws/en/data-governance/unity-catalog/access-control/workspace-catalog-binding",
        "title": "Databricks workspace-catalog bindings",
        "checked_on": "2026-10-16",
        "sha256": "e2f0d55f6e7e8250a534aef2e397f2faed021388a5176496d56f0f0e288dd469",
        "bytes": 37159
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Keep the identity and execution-location conditions together in a saved review.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Catalog type, isolation mode, workspace binding and user privileges"
    }
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#databricks-catalog-workspace-binding-grants",
  "machine_readable_record": "/varexis-index/records/databricks-catalog-workspace-binding-grants.json"
}