{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T12:05:03.000Z",
  "record_id": "VXI-EXT-PROCUREMENT-SLACK-HISTORY-TOKEN-TYPE-CHANNEL-MEMBERSHIP-01-v1",
  "record_kind": "external_reference",
  "title": "Slack history access by token type and membership",
  "system": "Slack",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can a Slack bot read private-channel history merely because its token has a history scope?",
  "near_questions": [
    "Does Slack history scope bypass private-channel membership?",
    "Do Slack user and bot tokens have the same conversation access?",
    "Which identity must belong to a channel for conversations.history?",
    "Does permission to post in Slack prove permission to read its history?"
  ],
  "supported_claims": [
    {
      "claim": "Slack conversations.history combines the relevant history scope with token-specific access. Bot tokens can read conversations the bot belongs to; app-level tokens cover conversations the app belongs to; user tokens cover private conversations the user belongs to and public conversations. A scope name alone does not establish membership or make bot and user access interchangeable.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Complete workspace export or permission to post or redistribute messages",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Slack conversations.history combines the relevant history scope with token-specific access. Bot tokens can read conversations the bot belongs to; app-level tokens cover conversations the app belongs to; user tokens cover private conversations the user belongs to and public conversations. A scope name alone does not establish membership or make bot and user access interchangeable.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "conversations.history method | Slack Developer Docs",
    "source_url": "https://docs.slack.dev/reference/methods/conversations.history/",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SLACK-HISTORY-TOKEN-TYPE-CHANNEL-MEMBERSHIP-01-v1",
    "candidate_record_sha256": "670b9741eba633805bc6b4052da53b467e44f2fff45004c8e8cacd2cb817084e",
    "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": "Slack conversations.history combines the relevant history scope with token-specific access. Bot tokens can read conversations the bot belongs to; app-level tokens cover conversations the app belongs to; user tokens cover private conversations the user belongs to and public conversations. A scope name alone does not establish membership or make bot and user access interchangeable.",
    "required_buyer_context": "Token type and granted history scope without exposing the token; Workspace, conversation identity and relevant membership; Purpose and authority for retrieving and disclosing the requested history. Buyer deployment not inspected.",
    "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-24",
    "claim_to_check": "Can a Slack bot read private-channel history merely because its token has a history scope?",
    "documented_statement": {
      "status": "documented",
      "statement": "Slack conversations.history combines the relevant history scope with token-specific access. Bot tokens can read conversations the bot belongs to; app-level tokens cover conversations the app belongs to; user tokens cover private conversations the user belongs to and public conversations. A scope name alone does not establish membership or make bot and user access interchangeable.",
      "source_ids": [
        "slack-history"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Bind the token identity and conversation membership to the proposed read, separately from any permission to post.",
      "source_ids": [
        "slack-history"
      ]
    },
    "buyer_evidence_required": [
      "Token type and granted history scope without exposing the token",
      "Workspace, conversation identity and relevant membership",
      "Purpose and authority for retrieving and disclosing the requested history"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not claim private-channel read authority from the presence of a history scope alone."
    },
    "unknowns": "Actual membership, effective access, history completeness and downstream disclosure authority were not tested.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Actual membership, effective access, history completeness and downstream disclosure authority were not tested."
    },
    "evidence_sources": [
      {
        "source_id": "slack-history",
        "url": "https://docs.slack.dev/reference/methods/conversations.history/",
        "final_url": "https://docs.slack.dev/reference/methods/conversations.history/",
        "status": 200,
        "captured_at_utc": "2026-10-24T11:34:51.504Z",
        "sha256": "93d67243dee8c40082e2bb6fa15a6a3f3984de8ae678a4b9a85ec3e1f5867528",
        "bytes": 105695,
        "title": "conversations.history method | Slack Developer Docs",
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "rights_review": "Factual paraphrase and source metadata only; response body retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "version_context": "Rolling official documentation captured 2026-10-24; installed buyer version not inspected",
        "reviewed_sections": [
          "Usage info: token types, scopes and conversation access"
        ],
        "claim_review_completed": true
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Check the specific identity and conversation boundary before an agent retrieves messages.",
      "free": "Complete review, sources, practical questions 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 the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Check the specific identity and conversation boundary before an agent retrieves messages.",
    "refusal_conditions": [
      "Do not claim private-channel read authority from the presence of a history scope alone."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "governance",
    "classification_label": "Agent Governance & Policy Boundaries",
    "topic_id": "governance",
    "buyer_intent": "Check the specific identity and conversation boundary before an agent retrieves messages.",
    "comparison_role": "supplementary_discovery"
  },
  "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#slack-history-token-type-channel-membership",
  "machine_readable_record": "/varexis-index/records/slack-history-token-type-channel-membership.json"
}
