slug: synadia-communications
provider: Synadia Communications
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 7
edges:
- tag: nats-user
  spec_file: synadia-communications-nats-user-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.78
  evidence: '"Get Bearer JWT", "Get Creds", "Get HTTP Gateway Token", "Assign Team App User to NATS User",
    schema UserPermissionLimits'
  reason: Lifecycle of NATS user principals, their permission limits, credential/JWT/token issuance and
    assignment to app users — identity and access management for platform access. Some ambiguity vs developer
    credential management, but the IAM reading is the plain one.
- tag: app-user
  spec_file: synadia-communications-app-user-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.75
  evidence: listAppUserRoles 'List Roles'; assignTeamAppUser 'Assign App User to Team'; deleteAppUser
    'Delete App User'; schema AppRoleScope
  reason: Create/update/delete of platform user accounts plus role listing and team (access group) assignment
    — joiner-mover-leaver style user and access administration, i.e. Identity & Access Management.
- tag: authz
  spec_file: synadia-communications-authz-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.75
  evidence: POST /core/beta/authz/check 'Check Authz Decisions'; listPolicies 'Get Policy List'; schemas
    AppPolicyStatement, AppRole, AppRoleEffect
  reason: Authorisation policy and role inspection plus runtime permission decision checks — access control
    administration and enforcement, clearly Identity & Access Management.
- tag: Issuance
  spec_file: synadia-communications-issuance-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.7
  evidence: GET /core/beta/nats-user-issuances/{issuanceId}  getNatsUserIssuance; schemas Permissions,
    UserLimits, UserPermissionLimits, NatsUserIssuanceStatus
  reason: Issuance of NATS user credentials carrying permissions and limits — issuance and stewardship
    of access credentials, i.e. identity & access management rather than any commercial 'issuance'.
- tag: app-service-account
  spec_file: synadia-communications-app-service-account-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.7
  evidence: getAppServiceAccount 'Get App Service Account'; createAppServiceAccountToken 'Create Acess
    Token for App Service Account'; schemas ServiceAccountScope, AppRoleScope
  reason: Lifecycle of non-human machine identities (service accounts) and their scoped access tokens
    on the control plane — machine identity and credential administration, squarely Identity & Access
    Management.
- tag: auth-callout
  spec_file: synadia-communications-auth-callout-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.7
  evidence: getAuthCallout 'Auth Callout Config'; addAuthCalloutUser 'Create Auth Callout User'; schema
    AuthCalloutAuthenticatorConfigViewResponse
  reason: Configuration of the NATS auth-callout authenticator, its target accounts and users — delegated
    authentication and access configuration for the messaging platform, an IAM capability rather than
    any line-of-business function.
- tag: sig-key-group
  spec_file: synadia-communications-sig-key-group-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.7
  evidence: '"Roate Active Signing Key", "List Signing Keys", "List NATS Users", schema SigningKeyGroupUpdateRequest'
  reason: Signing key groups, key rotation and the NATS users/permission limits bound to them — credential
    and access administration. IAM is the best fit; some ambiguity with secrets management.