---
id: ATS-CRM-ACT-007
scope: CAP-CRM-ACT-007
product_area: crm
module: activities-tasks
revision: 3
status: proposed
approved_by: null
approved_at: null
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  rhythm-v2-docs: 18a49edf30ee6bda18b159b65a2b91e093ea713d
scenarios:
- id: ATS-CRM-ACT-007-01
  title: Evaluate activity query authority
  level: api
  proves:
  - BR-CAP-CRM-ACT-007-01
  - BR-CAP-CRM-ACT-007-08
  preconditions: A customer administrator and Rhythm staff caller are available.
  steps: Run All activities as each.
  expected: Requests follow query authority and record any customer-policy gap.
  negative: true
  data_needs: Each run creates and isolates the records it needs.
  bound_to:
  - react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0721.spec.ts#CRM-ACC-0721
  - TST-CRM-ACT-065
  provenance: test
  source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0721.spec.ts#CRM-ACC-0721
  category: permission
  binding_scope: Each registered suite contributes the assertions named by the retained file bindings;
    a compound scenario can require several suites. Conformance remains unverified.
- id: ATS-CRM-ACT-007-02
  title: Open a direct activity link in its record context
  level: browser
  proves:
  - BR-CAP-CRM-ACT-007-05
  preconditions: Activities have a primary contact or only an organization.
  steps: Navigate to each activity link.
  expected: The related timeline opens with the activity selected.
  negative: false
  data_needs: Each run creates and isolates the records it needs.
  bound_to:
  - react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0722.spec.ts#CRM-ACC-0722
  - TST-CRM-ACT-066
  provenance: test
  source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0722.spec.ts#CRM-ACC-0722
  category: interaction
  binding_scope: Each registered suite contributes the assertions named by the retained file bindings;
    a compound scenario can require several suites. Conformance remains unverified.
- id: ATS-CRM-ACT-007-03
  title: Compute activity summaries on related records
  level: api
  proves:
  - BR-CAP-CRM-ACT-007-07
  preconditions: Contacts and organizations have completed, scheduled or no activity links.
  steps: Read their query-view summary fields.
  expected: Latest completed time and total count match the links, with empty time and zero count for
    no activities.
  negative: false
  data_needs: Each run creates and isolates the records it needs.
  bound_to:
  - services-crm:modules/activities/tests/integration/db/activity-summaries.view.integration.spec.js#answers
    the newest completed activity and every linked one for a contact
  - services-crm:modules/activities/tests/integration/db/activity-summaries.view.integration.spec.js#answers
    no last activity and a count of 0 for a contact with none
  - services-crm:modules/activities/tests/integration/db/activity-summaries.view.integration.spec.js#answers
    the same two for an organization
  - TST-CRM-ACT-004
  provenance: test
  source: services-crm:modules/activities/tests/integration/db/activity-summaries.view.integration.spec.js#answers
    the newest completed activity and every linked one for a contact
  category: rule
  binding_scope: Each registered suite contributes the assertions named by the retained file bindings;
    a compound scenario can require several suites. Conformance remains unverified.
- id: ATS-CRM-ACT-007-04
  title: Discovery lands on the selected record timeline
  category: interaction
  level: api
  proves:
  - BR-CAP-CRM-ACT-007-05
  - BR-CAP-CRM-ACT-005-05
  preconditions: An interaction links a primary organization and a contact.
  steps: Find it through a permitted workspace query and follow its direct link, then compare the timeline
    entry with the query result.
  expected: The contact timeline opens at the same interaction; sharing does not duplicate the selected
    entry.
  negative: false
  data_needs: Run-owned records in an isolated workspace; fixed clock for calendar checks.
  bound_to: []
  provenance: proposed
  source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0722.spec.ts#CRM-ACC-0722;
    services-crm:modules/activities/tests/integration/services/persistence/activities.queries.integration.spec.js#shows
    the activity linked to three contacts and an organization once on each of the four timelines
  exercises:
  - CAP-CRM-ACT-007
  - CAP-CRM-ACT-005
  related:
  - CAP-CRM-ACT-005
evidence:
- 'services-crm at a8d1364f1dd44b723bb5f9acba12f983e9ec8d69: scenario sources, executable assertions and
  local dependency boundaries are inspected.'
- 'react-console at baf6dae382d6f41dce976c7f848667ccc37e076f: scoped component tests and browser journey
  assertions are inspected.'
coverage:
  rule: covered
  transition: 'gap: FND-CRM-ACT-053'
  validation: 'gap: FND-CRM-ACT-053'
  permission: covered
  edge: 'gap: FND-CRM-ACT-053'
  failure: 'gap: FND-CRM-ACT-053'
  boundary: 'gap: FND-CRM-ACT-053'
  concurrency: 'gap: FND-CRM-ACT-053'
  invariant: 'gap: FND-CRM-ACT-053'
  interaction: covered
coverage_obligations:
  finding: FND-CRM-ACT-053
  unproved_rules:
  - BR-CAP-CRM-ACT-007-04
  permission_matrix:
    keys:
    - crm.activities.query
    - crm.activity-types.read
    - crm.activities.read
    remaining: Complete allow/refuse combinations, including each console guard and each API operation.
  execution_note: Covered means a scenario is specified; it does not mean that scenario has executed or
    every variant has an executable binding.
related_coverage:
- capability: CAP-CRM-ACT-005
  scenarios:
  - ATS-CRM-ACT-007-04
  finding: FND-CRM-ACT-053
permission_coverage:
- key: crm.activities.query
  finding: FND-CRM-ACT-053
  note: The finding covers unproved operation and surface combinations; a permission-category scenario
    is not a complete permission matrix.
- key: crm.activity-types.read
  finding: FND-CRM-ACT-053
  note: The finding covers unproved operation and surface combinations; a permission-category scenario
    is not a complete permission matrix.
- key: crm.activities.read
  finding: FND-CRM-ACT-053
  note: The finding covers unproved operation and surface combinations; a permission-category scenario
    is not a complete permission matrix.
---

# Find and open activities across the workspace: Capability Test Specification

## Coverage

Category coverage counts specified proof. Unbound cases remain proposed; registered assertions do not establish a passing run.

| Rule | Proof Scenario Or Finding |
|---|---|
| `BR-CAP-CRM-ACT-007-01` | `ATS-CRM-ACT-007-01` |
| `BR-CAP-CRM-ACT-007-04` | `FND-CRM-ACT-053` |
| `BR-CAP-CRM-ACT-007-05` | `ATS-CRM-ACT-007-02`, `ATS-CRM-ACT-007-04` |
| `BR-CAP-CRM-ACT-007-07` | `ATS-CRM-ACT-007-03` |
| `BR-CAP-CRM-ACT-007-08` | `ATS-CRM-ACT-007-01` |

## Interactions With Related Capabilities

An interaction links a primary organization and a contact. Find it through a permitted workspace query and follow its direct link, then compare the timeline entry with the query result.

The interaction scenario names the capabilities and rules it exercises. The coverage finding retains incomplete permission combinations and failure variants.