Guide
Program Invitations and Acceptance
Recipient onboarding, email verification, token expiry and versioned terms.
Current program availability
Affiliate and collaborator agreements, invitations, and referral tools are available through controlled rollout. General sale accounting, automated recipient notifications, and live recipient transfers are not enabled. An accepted agreement or displayed estimate is not confirmation that earnings are accruing or a payment has been authorized. Confirm account availability with SoundSync before relying on the financial workflow.
Agreement and live participation are separate
Affiliate and collaborator programs support versioned agreements, referral activity, sale allocations, recipient balances, and settlement for enrolled accounts. Live participation requires explicit acceptance by both the developer owner and recipient of the current terms and payout policy, plus verified payout details. A calculator preview or invitation acceptance alone does not authorize live payments; availability follows the account's rollout and payout readiness.
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 proposal does not overwrite current accepted terms. Both the developer owner and recipient must explicitly accept the applicable live terms and payout policy before eligible new sales accrue. Team membership cannot substitute for owner financial authorization.