---
id: CON-MBR-STR-006
name: Membership Setup
feature: FEAT-MBR-STR-06
product_area: membership
module: structure
revision: 1
status: draft
product_intent: proposed
implementation_evidence: partially-observed
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
definition: >-
  Membership setup brings together the customer’s structural and membership configuration, its shared change
  safeguards and its workspace lifecycle contribution.
owned_by: MOD-MBR-STR
synonyms:
  - association setup
  - membership configuration governance
not_to_be_confused_with:
  - Platform workspace orchestration
  - Security roles and policy evaluation
  - Commerce member-pricing settings
facets:
  - name: Readable references
    meaning: >-
      Configuration records use staff-supplied or name-derived references, with package identity supplied by
      Accounting.
    used_for: Connecting related records and migration inputs.
  - name: Change versions
    meaning: Version checks protect ordinary configuration mutations from intervening edits.
    used_for: Coordinating administrators and integrations.
  - name: Dependency protection
    meaning: Referenced records resist removal while dependent records retain them.
    used_for: Preserving membership and structural references.
  - name: Workspace isolation
    meaning: Records belong to one customer workspace and reads honor that boundary.
    used_for: Keeping customer information separated.
  - name: Administration authority
    meaning: 'Read and manage permissions distinguish structure, program and configuration responsibilities.'
    used_for: Controlling workspace-wide setup work.
  - name: Initial configuration
    meaning: Standard relationship purposes and recognizable development records supply starting information.
    used_for: Preparing new workspaces and development environments.
  - name: Migration contribution
    meaning: Operation definitions describe supported record loading and dependency order.
    used_for: Preparing migration work whose submission wiring remains incomplete.
  - name: Export and removal
    meaning: Dataset and lifecycle contributions describe retained data and controlled cleanup.
    used_for: 'Supporting workspace export, reset and deletion.'
relationships:
  - to: CON-MBR-STR-001
    statement: 'The structure participates in setup lifecycle work, including export and removal.'
    provenance: observed
    source: 'services-membership:modules/structure/services/lifecycle/structure-participant.ts:structureParticipant'
  - to: CON-MBR-STR-003
    statement: Programs and classifications use shared configuration operations.
    provenance: observed
    source: 'services-membership:aws/api/configuration-routes.ts:configurationRoutes'
  - to: CON-MBR-STR-004
    statement: Packages use the shared operations with product-supplied identity.
    provenance: observed
    source: >-
      services-membership:modules/configuration/services/configuration/configuration-records.ts:packageResource
lifecycle: []
acted_on_by:
  - CAP-MBR-STR-018
  - CAP-MBR-STR-019
  - CAP-MBR-STR-020
visible_to:
  - ACT-MBR-001
  - ACT-MBR-002
  - ACT-MBR-003
  - ACT-MBR-004
evidence:
  - >-
    services-membership: Verified material includes the configuration route builder, shared store and record
    helpers, the permission catalogue, the structure lifecycle participant, data operations and exports.
  - >-
    services-membership: Verified material includes route authorization, database refusals, row-level security
    and lifecycle tests; configuration acceptance journeys.
supersedes:
  - react-console acceptance inventory CAP-MBR-CFG-011
  - react-console acceptance inventory CAP-MBR-CFG-013
  - react-console acceptance inventory CAP-MBR-CFG-014
  - react-console acceptance inventory CAP-MBR-STR-012
  - react-console acceptance inventory CAP-MBR-STR-013
  - react-console acceptance inventory CAP-MBR-STR-014
---

# Membership Setup

## What It Is

Membership setup is the association’s structure and membership configuration considered as a managed whole. It includes the unit arrangement, programs, classifications, offerings, action reasons and future change policies that staff prepare around individual memberships. The concept also explains their shared administration: how related references survive changes, how competing edits are detected and how the module participates in a workspace’s life.

This view helps a product manager reason about dependable configuration rather than treating every setting as a separate thing. A record has an identity and dependencies as well as its visible choices. Its operations have particular replacement and version behavior. Setup is therefore broader than a collection of forms, and the present API contribution can be examined even before the administration screens exist.

## What It Is Not

The setup does not orchestrate every application’s workspace lifecycle. Platform owns that coordination and invokes Membership’s contribution. Security owns role assignments and permission evaluation. The console’s current Membership Settings page concerns Commerce member pricing; it does not establish screens for this structural configuration. Nor are all module operations identical merely because they share an administrative purpose.

## How It Is Used

Administrators maintain the setup as membership offerings and organizational arrangements change. Readers inspect it without management authority. Migration producers rely on operation definitions for bringing existing customer records across, while system work seeds, exports and removes module data. Staff encounter different save semantics between structure and configuration: complete ordinary-field replacement on one side and partial changes on the other. Some structural operations also omit version checks unless the caller supplies a version. These distinctions need deliberate handling by future screens and integrations.

## Its Facets

**Readable references.** Stable record references connect configuration without making every display name permanent.

**Change versions.** Ordinary configuration mutations state the version read.

**Dependency protection.** Removal cannot casually discard a record still used elsewhere.

**Workspace isolation.** The database boundary complements request checks.

**Administration authority.** Workspace-wide setup permissions differ from an officer’s local membership authority.

**Initial configuration.** Seed bookkeeping preserves the customer’s subsequent choices.

**Migration contribution.** Supported loads declare dependencies and validation without establishing a reachable submission experience.

**Export and removal.** Owned data is described for export and removed only under appropriate workspace states.

## How It Relates

The hierarchy, units, programs and packages provide the business content managed through setup. Term interpretation consumes their calendar choices. Platform supplies lifecycle coordination, data-job execution and permission evaluation. Membership administration owns individual holdings and the broader configuration-history concern. Connected applications consume this module’s information without becoming its authoring home.

## What It Could Become

The product should complete data-job wiring, settle reprovisioning after purge and reconcile console permission vocabulary before adding setup screens. It should also decide whether stored lock flags become effective administration controls. Aligning replacement and paging behavior could reduce integration mistakes, but any alignment must preserve the meaning of existing callers’ requests.