---
id: TST-PFM-SEC-129
title: Resource scopes database and service checks
kind: integration
product_area: platform
module: security
revision: 2
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/security/tests/integration/services/membership/resource-scopes.integration.spec.js
implements:
  - ATS-PFM-SEC-010-03
  - ATS-PFM-SEC-010-08
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: Use the prepared test database and suite-owned fixture rows; retain shared seed records.
assertion_evidence:
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/resource-scopes.integration.spec.js#security:
      resource-scoped grants
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/resource-scopes.integration.spec.js#grants
      a role on an existing custom object and lists the scope on the role’s members
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/resource-scopes.integration.spec.js#grants
      a role on a draft custom object, which is live though not yet active
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/resource-scopes.integration.spec.js#refuses
      a resource type that is not on the allow-list, naming the field, and writes nothing
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/resource-scopes.integration.spec.js#refuses
      a custom object the tenant does not have as not found, naming the object key, and writes
      nothing
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/resource-scopes.integration.spec.js#refuses
      an archived custom object, naming the object key, and writes nothing
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/resource-scopes.integration.spec.js#leaves
      a resource grant untouched, and out of the answer, when the role’s scope is set
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The suite controls workflow execution, the clock at the declared seams; those collaborators remain
  outside its live proof.
evidence:
  - >-
    services-platform:modules/security/tests/integration/services/membership/resource-scopes.integration.spec.js
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  Each binding names the scenario to which this file contributes assertions. A binding is not a
  recorded pass and does not extend the file’s dependency boundary.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: >-
    services-platform:modules/security/tests/integration/services/membership/resource-scopes.integration.spec.js
  explicit_no_doubles: false
  identified_double_boundaries:
    - workflow execution
    - the clock
---
# Resource scopes database and service checks

## Verification Boundary

The file exercises database or service behavior through the local integration harness. The assertion references identify the source checks for resource scopes.

## What This Suite Proves

The source assertions support the observations named in the bound scenarios. A scenario spanning multiple files must retain the other files’ contributions.

## What It Does Not Prove

This examination does not run the suite. Passing behavior, deployed conformance and the behavior of substituted dependencies require separate execution evidence.

## Real Dependencies and Test Doubles

The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here. The suite controls workflow execution, the clock at the declared seams; those collaborators remain outside its live proof.

## Must Not Be Doubled

Keep the queried database, applicable constraints and transaction boundaries real. Provider substitutes cannot establish delivery, cloud execution or cross-service recovery.