slug: docusign provider: Docusign 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: 17 edges: - tag: Envelopes spec_file: docusign-envelopes-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.8 evidence: Envelopes_PutEnvelope Send, void, or modify a draft envelope. Purge documents from a completed envelope; AuditEvents_GetAuditEvents Gets the envelope audit events for an envelope reason: The core envelope surface creates, sends, tracks status of, voids and audits agreements sent for signature — the drafting-to-closure contract lifecycle. Title's 'Admin AccountBrands' is spurious concatenation; operations are envelope lifecycle. - tag: eSignUserManagement spec_file: docusign-esignusermanagement-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.8 evidence: '"Returns the list of permission profiles in an account." / "Creates a new user." / "Closes a user''s memberships." / "Deletes user identities."' reason: Organisation-level user, group, permission-profile, membership and identity administration is Identity & Access Management (joiners-movers-leavers, entitlement profiles). Some ambiguity with tenant identity/user lifecycle in a SaaS sense, hence 0.8 rather than 0.95. - tag: AccountPermissionProfiles spec_file: docusign-accountpermissionprofiles-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.75 evidence: '"Creates a new permission profile in the specified account"; schemas permissionProfile, accountRoleSettings, userAccountManagementGranularInformation' reason: CRUD over permission profiles (roles) governing what users may do in an account — access rights administration, i.e. Identity & Access Management. - tag: Accounts spec_file: docusign-accounts-api-openapi.yml capability_id: BC-4230.10 capability_id_l1: BC-4230 capability_name: Tenant Provisioning & Lifecycle confidence: 0.75 evidence: '"Creates new accounts." / "Deletes the specified account." / "Updates the account settings for an account."' reason: Account here is the tenant in Docusign's multi-tenant service; the operations create, retrieve, configure and delete accounts, i.e. tenant provisioning and lifecycle. Some spill into configuration and billing charges. - tag: GroupUsers spec_file: docusign-group-users-api-openapi.yml reanchored_from: docusign-groupusers-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.75 evidence: '''Gets a list of users in a group.'' / ''Adds one or more users to an existing group.'' / ''Deletes one or more users from a gro''' reason: CRUD over group membership for user accounts is access-rights administration (joiners-movers-leavers, group-based entitlement), which is Identity & Access Management. Schemas (userInfo, userInfoList) confirm these are user principals, not business contacts. - tag: Groups spec_file: docusign-groups-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.75 evidence: '''Creates one or more groups for the account.'' / ''Deletes an existing user group.'' Schemas: group, groupInformation, userInfo' reason: Lifecycle of user groups used to grant permissions within an account — security group administration, i.e. Identity & Access Management. 'Groups' is not an organisational-unit or HR construct here; the schemas are user/permission oriented. - tag: MultiProductUserManagement spec_file: docusign-multiproductusermanagement-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.75 evidence: '"Adds a list of users to a DSGroup."; "Assigns user to permission profiles for one or more products."; schema ProductPermissionProfileRequest' reason: Operations create groups, add/remove users and assign permission profiles across products — administrative user provisioning and access rights, i.e. Identity & Access Management. Slight ambiguity with tenant identity/entitlement framings keeps confidence at 0.75. - tag: Users spec_file: docusign-users-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.72 evidence: Users_PostUsers Docusign Adds news user to the specified account. ... Users_RemoveUser Docusign Removes a user from a company account. reason: Create, update, list and remove user accounts and their privileges within an organization/account, plus email-address changes — classic user account administration (joiners-movers-leavers) under Identity & Access Management. - tag: AccountPasswordRules spec_file: docusign-accountpasswordrules-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.7 evidence: '"Get the password rules" / "Update the password rules"; schemas accountMinimumPasswordLength, accountPasswordLockoutDurationMinutes' reason: Operations manage password strength, expiry and lockout policy for account users — an identity and access control policy surface, not a business process of the buyer. - tag: BillingPlans spec_file: docusign-billingplans-api-openapi.yml capability_id: BC-4240 capability_id_l1: BC-4240 capability_name: Subscription Lifecycle Management confidence: 0.7 evidence: '"Gets the list of available billing plans." / "Updates the account billing plan." / "Reserverd: Purchase additional envelopes."' reason: Operations expose the plan catalogue and change an account's subscription plan (plus add-on envelope purchase and stored credit-card metadata), which is subscription plan lifecycle for a SaaS offering. Ambiguous between plan design, modification and payment-method handling, so no L2 asserted. - tag: ConnectConfigurations spec_file: docusign-connectconfigurations-api-openapi.yml capability_id: BC-4270.80 capability_id_l1: BC-4270 capability_name: Webhook & Event Subscription Management confidence: 0.7 evidence: '''Creates a connect configuration for the specified account.'', ''Updates a specified Connect configuration.'', schema connectCustomConfiguration' reason: Docusign Connect is the outbound event/webhook publishing service; these operations create, update and delete webhook endpoint subscriptions for an account, matching outbound webhook and event subscription lifecycle. Some risk that 'Connect' is read as a generic integration config rather than webhooks. - tag: ConnectEvents spec_file: docusign-connectevents-api-openapi.yml capability_id: BC-4270.80 capability_id_l1: BC-4270 capability_name: Webhook & Event Subscription Management confidence: 0.7 evidence: '''Republishes Connect information for the specified envelope.'', ''Gets the Connect failure log information.'', schemas connectFailureResults, connectDebugLog' reason: Retry queues, failure logs and delivery logs for Connect message publication are webhook delivery reliability operations. Moderate confidence as it is operational logging around the event delivery pipeline. - tag: EnvelopeDocuments spec_file: docusign-envelopedocuments-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.7 evidence: Documents_PutDocuments Adds one or more documents to an existing envelope document; Documents_DeleteDocuments Deletes documents from a draft envelope reason: Managing the documents that constitute an agreement envelope sent for signature is part of the contract lifecycle from drafting to execution. Title mentions Admin/AccountBrands but operations are clearly envelope document handling. - tag: IdentityProviders spec_file: docusign-identity-providers-api-openapi.yml reanchored_from: docusign-identityproviders-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.7 evidence: '''Returns the list of identity providers for an organization.'' Schemas: Saml2IdentityProviderResponse, RequiredAttributeMappingResponse, CertificateResponse' reason: SAML2 identity-provider registration and attribute mapping for an organisation is federated single sign-on configuration, which BC-620.20 explicitly covers ('IAM, PAM, federation'). BC-4230.50 Tenant Identity Federation is an equally plausible reading from the vendor side, hence 0.7 rather than higher. - tag: Invoices spec_file: docusign-invoices-api-openapi.yml capability_id: BC-4250.30 capability_id_l1: BC-4250 capability_name: Invoicing & Statement Management confidence: 0.7 evidence: '"Docusign Get a List of Billing Invoices"; "Docusign Retrieves a billing invoice."; schema billingInvoice' reason: Operations retrieve billing invoices and past-due invoices for the subscribing account, i.e. invoice/statement surface of the SaaS billing model. Mapped to Invoicing & Statement Management; some ambiguity with generic accounts-receivable framing, hence 0.7. - tag: Payments spec_file: docusign-payments-api-openapi.yml capability_id: BC-4250.40 capability_id_l1: BC-4250 capability_name: Payment Collection & Dunning confidence: 0.7 evidence: '"Docusign Posts a payment to a past due invoice."; schemas billingPaymentRequest, billingPayment' reason: Operations retrieve and post payments against account billing invoices, including past-due settlement — payment collection against subscription invoices. Confidence 0.7 given the alternative reading as generic accounts-receivable cash application. - tag: Recipients spec_file: docusign-recipients-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.7 evidence: POST /accounts/{accountId}/envelopes/{envelopeId}/recipients — "Add Recipients to an Envelope"; schemas Signer, InPersonSigner, SignHere, DateSigned, CertifiedDelivery reason: Operations manage the signing parties on an e-signature envelope, with signer/sign-here/date-signed constructs. This is execution of agreements, i.e. the contract lifecycle (drafting-to-signature) capability. Mapped at L2 Contract Management with moderate confidence since the surface covers only the signature-routing slice.