Guide
Team Product Scope
Combine role permissions with the products the member is allowed to manage.
Two checks, not one
A permitted action still needs the relevant product scope. A product assignment does not by itself grant every operational or financial permission. Test both dimensions when reviewing team access.
Some account-wide settings require broader scope and specific view/manage permissions. For example, GA4 settings require the appropriate settings permission and all-product scope; assignment to one product is not enough.
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.
Review changes
Use supported role/scope updates and member removal. Confirm later sessions and requests honor the new access. Do not share the owner account to bypass a member restriction or place owner tokens into client packages.
Scope values and complete updates
The two scope modes are all_products and selected_products. For selected_products, send the complete selectedProductIds array on every member update, even when changing only the role. An empty or omitted selection is rejected. Membership updates revoke existing sessions; a new sign-in may be required.
Product authoring follows the active workspace
Customer accounts and view-only teammates cannot create products or invoke product-writing AI tools. Product creation and untargeted new-product AI require products.create and all-products workspace scope. Existing-product AI and edits require the matching product permission, workspace ownership and assignment to that product before database writes or AI calls.
New products belong to the effective workspace developer, not the teammate operating the editor. File actions use product_files permissions; scheduled-deal changes use marketing permissions, while purchase-option deal publication retains products.publish. Product statistics require analytics.view. Publication and archival retain their dedicated permissions. These checks do not change role definitions, checkout pricing or financial execution.
Manage related products in the selected workspace
Expansion reads use product-view permission and changes use product-edit permission. Both the parent and child must belong to the selected developer workspace and be assigned to a product-scoped teammate. Lists omit unassigned relationships and expansions. Authorized teammates use the workspace developer as owner; their own account remains the acting user.
An existing legacy subscription bundle is a workspace-wide collection: editing it requires all-products scope. Selected-product creation remains available for assigned members. Its recurring-revenue summary requires analytics-view permission. These controls do not change customer ownership, subscriptions or offline access.
Activity stays within the teammate's permitted records
The combined analytics activity feed follows assigned products, including its counts and product filters. An empty assignment returns no activity. Productless website events and workspace-wide email events are not included in a product-filtered feed; a mixed-product sale shows only its selected item amount.
Customer and visitor identity, serial details and private order references follow their separate record permissions. Free-text diagnostics and nested metadata need the complete supporting record permissions. Search runs after those fields are filtered, so a hidden email address cannot be used to identify activity. Authorized analytics remain available.
Workspace-wide revenue reports and their analytics aliases require all-products access. Aggregate totals do not grant access to customer lists, subscription identities, order references or individual refund records. Refund details require refund access; private customer/order searches also require those record permissions.
