Skip to main content
Version: Current guides

Invite members and assign access

Availability​

Public availability of member invitations, preset or custom roles, ownership transfer and audits remains unconfirmed. Use these instructions only when the controls are enabled. Otherwise, assign internal owners without sharing owner credentials. Actual role names, member quotas, invitation validity and permissions come from the account, not plan designs.

Map responsibilities first​

ResponsibilityAccess to review
Orders and supportOrders, necessary customer information and support cases; separately decide whether direct refunds are allowed
FinanceReconciliation and refund or settlement visibility; authorize funds execution and wallet changes separately
Development and operationsIntegration and troubleshooting, with credential or notification management as needed; no assumed wallet signing rights
Account managementMembers, settings and approval of sensitive actions; account ownership and wallet control remain separate
Read-only reviewNecessary records without write access or unrelated personal-data exports

This is an organizational suggestion, not a platform role matrix. Inspect real permissions rather than relying on a role's name.

Invite and verify a member​

  1. Have an authorized owner open team management and verify the recipient and email. Avoid shared public mailboxes.
  2. Select the least access needed using actual roles or configurable permissions. Check refunds, funds execution, wallets, credentials and customer exports separately.
  3. Send the invitation and record its state. Sent does not mean joined.
  4. Have the member accept through the real invitation and complete applicable security checks. Do not forward token-bearing invitations to unrelated people.
  5. Use the member's own account to verify that required tasks work and unnecessary sensitive operations are unavailable.
  6. Record who granted access, the responsibility and review date. Change permissions when duties change rather than lending another account.

Troubleshoot access​

  • Missing invitation: check the email, spam and invitation state before resending an existing valid invitation.
  • Expired or duplicate invitation: use supported reissue or revocation controls; do not assume a seven-day lifetime.
  • Visible page but rejected operation: verify acceptance, merchant, environment and action permission; button visibility does not establish authorization.
  • Access persists after a role change: sign in again and inspect actual results, retaining evidence for the administrator. Do not assume sessions, API credentials and wallet rights were all revoked together.

Offboard a member​

  1. Reassign pending orders, support cases and reconciliation, ensuring unresolved work has an owner.
  2. Revoke pending invitations or remove the member through available controls and inspect sessions.
  3. Separately inventory exposed API Keys, notification secrets, wallet signing rights, report recipients and external systems; revoke or rotate as needed.
  4. For ownership transfer, have the current owner verify the recipient through the supported flow, then inspect both parties' access. Removing a member does not establish ownership transfer.
  5. Retain the record and check that queries for important orders, refunds and settlements still work.

Use security for compromise and developer operations to verify credential changes.