Skip to main content
Business Accounts are in early access. See Business Accounts for the model.
When Business Account invitations are enabled for an environment, adding a member or end-user signer creates pending access. The invited user becomes an active member only after signing in and accepting the invitation.

​
Invitation lifecycle

  1. An owner or admin starts a member or signer addition.
  2. If the account governs that action, the required approvals complete before the addition proceeds.
  3. Dynamic creates a pending membership and an invitation. The inviter receives an invitation receipt containing the supplied identifier and invitation ID, without the resolved user ID.
  4. The invited user signs in. Dynamic identifies them from their authenticated session and returns only invitations addressed to that user.
  5. The user accepts the invitation. Dynamic activates the pending membership and refreshes their authorization state.
Invitations are environment-specific. The invited user must sign in to the environment where the invitation was created, using the credential that matches the invitation.

​
Member and signer invitations

Members and signers remain separate concepts. A member invitation grants account access with a role. A signer invitation also grants signing access to the specified wallet after acceptance.

​
Approvals and step-up authentication

Creating and canceling invitations use the same controls as the corresponding membership action:
  • Adding a member or signer can require approvals.
  • Canceling an invitation can require the approvals configured for removing a member.
  • The initiating owner or admin must complete step-up authentication for the protected action.
  • Accepting an invitation does not require the inviter’s elevated token. The authenticated invitee accepts for themselves.
Step-up authentication confirms the initiator’s identity. Approvals collect consent from other members. Invitation acceptance confirms that the invited user wants the access. These checks serve different purposes and can all apply to one addition.

​
Cancel an invitation

An authorized owner or admin can list outstanding invitations and cancel one by its invitation ID. Canceling a signer invitation also revokes its staged signer and key-share resources. A canceled invitation can no longer be accepted.

​
Security model

  • Inviter-facing invitation receipts omit the resolved user ID.
  • Recipient-facing list and accept operations derive the invitee from the authenticated session. A client cannot supply a different target user.
  • Acceptance is idempotent. Repeating a successful acceptance returns the accepted invitation and active member.
  • Active business account data does not include pending members or pending signer access.

​
Next steps

Implement invitations

Create, list, accept, and cancel invitations with the JavaScript SDK or React hooks.

Members and roles

Understand membership roles and account permissions.
Last modified on November 12, 2026