Guide
Team Invitations
Invite a member to the intended developer workspace and verify accepted access.
SoundSync
Invite deliberately
-
Person
Use the intended recipient and workspace.
-
Role
Select the necessary supported role/permissions.
-
Products
Choose the relevant product scope.
-
Acceptance
Have the member complete the supported account/invitation flow.
-
Verification
Test permitted operations and denied product/actions with that member.
Keep invitations private
An invitation does not authorize unrelated products or financial operations. Use the supported invitation status/revoke controls when the recipient or scope is wrong. Do not publish invitation links or member personal data.
Workspace membership is different from a customer entitlement and from a partner API relationship.
One-time invitations expire after seven days
Invitations use one-time tokens bound to the invited email. SoundSync stores a token hash rather than a reusable raw token. Sign in with the invited email to accept. A replacement invitation supersedes an earlier pending invitation for that address; revoked, used, or expired links cannot grant access.
Choose all_products for all current and future products, or selected_products with at least one owned product ID. Review the permission and product selection together. Never publish invitation links or tokens.
SoundSync
Invitation request and errors
Team Accounts API
Creation, acceptance, revocation, exact payloads, expiry, and error handling.
SoundSync