Skip to content
SoundSyncAudio software platform

Guide

Team Invitations

Invite a member to the intended developer workspace and verify accepted access.

SoundSync

Invite deliberately

  1. Person

    Use the intended recipient and workspace.

  2. Role

    Select the necessary supported role/permissions.

  3. Products

    Choose the relevant product scope.

  4. Acceptance

    Have the member complete the supported account/invitation flow.

  5. Verification

    Test permitted operations and denied product/actions with that member.

SoundSync

Choose a role and the products it can access

The team workspace brings members, invitations, roles and product-access choices together. Personal fields are blurred. No invitation was sent or membership changed for this image.

Team accounts - Private account details and business metrics are blurred.

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

Join a developer team without losing the invitation

  1. Open the private invitation

    Review the invited email, workspace and role. Keep the token private and use the intended individual account.

  2. Use developer signup or login

    The invitation continues through developer registration, sign-in, two-factor verification and email-verification resend. A customer account using the same email is separate and does not grant workspace membership.

  3. Complete verification and accept

    Return to the invitation after verification, then accept the current role and product assignments. A preview or verification resend does not accept membership.

  4. Check the assigned workspace

    Confirm both permitted work and a denied unassigned product. Billing reports do not grant owner-only payout onboarding, and limited-product roles cannot edit workspace-wide settings.