Guide
Program Invitations and Acceptance
Recipient onboarding, email verification, token expiry and versioned terms.
Preview participation
Affiliate and collaborator programs are being introduced through agreement previews. Live commission accrual and recipient payouts are not enabled. Preview acceptance does not authorize payments; live participation will require separate acceptance and verified payout details.
SoundSync
Invitation lifecycle
| Stage | Action |
|---|---|
| Proposal | Set recipient email, name, eligible products, rates and effective date |
| Invite | Copy the generated link or request delivery; inspect delivery failure separately |
| Identify | Sign in with the invited email or use the invitation-authorized account setup |
| Verify | Complete email verification; existing two-factor authentication still applies |
| Review | Read developer identity, product names, effective dates and the displayed payout policy |
| Accept | Accept the specific version, terms and payout-policy version |
| Maintain | Revise, pause, resume or end through the permitted management workflow |
A link is a secret
Invitation tokens expire after seven days and are stored as hashes. Used, expired and revoked invitations cannot be accepted. Generating or emailing a replacement revokes older pending links. Do not publish invitation URLs in screenshots, issue reports or public documentation.
Permissions remain separate
Acceptance does not grant developer team membership, reseller authority, product editing or customer-data permissions. Read-only workspace members should review permitted records without seeing management actions. Use Team Accounts when a contributor also needs dashboard access.
Changes require a new decision
Accepted terms are versioned and effective-dated. A new proposal does not overwrite the current accepted terms. Preview acceptance cannot silently become a live payment agreement; the live program will require a separate explicit acceptance.