{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-14T01:25:58.088Z",
  "record_id": "VXI-EXT-PROCUREMENT-DRIVE-FOLDER-INHERITANCE-01-v1",
  "record_kind": "external_reference",
  "title": "Google Drive: Folder inheritance and limited access",
  "system": "Google Drive sharing",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can a file-level sharing change remove access inherited from a Drive folder?",
  "near_questions": [
    "Can a file permission override inherited folder access?",
    "Which parent folder grants access to a document?",
    "How does limited folder access change the review?",
    "Can a file move alter its effective audience?",
    "What evidence should an agent request for inherited sharing?",
    "Does one file settings screenshot show every grant?",
    "Can group membership preserve access after a direct grant is removed?",
    "What should procurement ask about shared-folder boundaries?",
    "How should an agent qualify a file revocation claim?",
    "Which folder configuration should a saved review identify?",
    "Can I preserve the Drive inheritance evidence?",
    "When should shared-folder access be reassessed?"
  ],
  "supported_claims": [
    {
      "claim": "Google explains that folder access is inherited by contained files and subfolders. Reducing inherited access requires addressing the folder-level permission; limited-access folders provide a separate boundary. Review the path and explicit grants rather than interpreting a single file setting in isolation.",
      "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": "Google explains that folder access is inherited by contained files and subfolders. Reducing inherited access requires addressing the folder-level permission; limited-access folders provide a separate boundary. Review the path and explicit grants rather than interpreting a single file setting in isolation.",
  "related_record_ids": [
    "VXI-EXT-PROCUREMENT-ATLASSIAN-APP-COVERAGE-01-v1",
    "VXI-EXT-PROCUREMENT-NOTION-INHERITED-SHARING-01-v1",
    "VXI-EXT-PROCUREMENT-SHAREPOINT-LINK-AUDIENCE-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Google Drive inherited and limited folder access",
    "source_url": "https://support.google.com/drive/answer/7166529?hl=en",
    "checked_on": "2026-10-14",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-DRIVE-FOLDER-INHERITANCE-01-v1",
    "candidate_record_sha256": "f9de2b734819d95653a3057a032f12cc6992f83864210102030c6f24c2ed57a8",
    "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": "Google explains that folder access is inherited by contained files and subfolders. Reducing inherited access requires addressing the folder-level permission; limited-access folders provide a separate boundary. Review the path and explicit grants rather than interpreting a single file setting in isolation.",
    "required_buyer_context": "File path within shared folders, inherited grants and limited-access configuration.",
    "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-14",
    "claim_to_check": "Changing one file permission removes all inherited folder access.",
    "documented_statement": {
      "status": "documented",
      "statement": "Google explains that folder access is inherited by contained files and subfolders. Reducing inherited access requires addressing the folder-level permission; limited-access folders provide a separate boundary. Review the path and explicit grants rather than interpreting a single file setting in isolation.",
      "source_ids": [
        "drive-sharing"
      ]
    },
    "buyer_evidence_required": [
      "Parent-folder access and relevant group membership",
      "Direct grants and limited-access folder configuration",
      "Observed access for the intended identities after changes"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Require inherited-permission evidence before claiming file access is removed."
    },
    "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": "drive-sharing",
        "url": "https://support.google.com/drive/answer/7166529?hl=en",
        "final_url": "https://support.google.com/drive/answer/7166529?hl=en",
        "title": "Google Drive inherited and limited folder access",
        "checked_on": "2026-10-14",
        "sha256": "94a65f9b6b4fb154d6b31fd01ea44dd5e0e29d1335c7c5d77e81a46607171bb6",
        "bytes": 1628108
      }
    ],
    "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": "Save the inheritance checks behind a document-access procurement 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": "Recheck folder moves, group membership and limited-access changes."
    }
  },
  "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#google-drive-folder-inheritance-evidence",
  "machine_readable_record": "/varexis-index/records/google-drive-folder-inheritance-evidence.json"
}