Synthesia avatar sharing vs Sume workspace-scoped avatars

Synthesia's update describes sharing the base person for an avatar with teammates or the whole workspace so they can create outfits and generate media. On Sume, the boundary is the workspace: API keys are workspace-scoped, avatars are referenced by handle, and a resource outside the current workspace returns 404 not_found. The docs I read describe no per-avatar sharing control.

Synthesia's wording is from its updates page (Enterprise note); Sume's from API keys, Create new avatar and Errors and rate limits, read 2026-10-01.

What does Synthesia let you share?

The update says you can share the base person for a customizable avatar with teammates or your whole workspace, and they can create new outfits for it and use it to generate media.

How do Sume workspaces scope avatars?

API keys are workspace-scoped, and the dashboard reveals the full secret only when a key is created, so store it at once. Avatar creation takes a top-level avatar_handle; the handle may include a leading @ and is stored without it. List avatars with GET /v1/avatar-1.0/avatars. Anyone with a key from that workspace works against the same set.

What happens if a teammate uses another workspace's key?

The error table defines 404 not_found as a resource that does not exist in the current workspace. So an avatar handle created under one workspace's key should not resolve under a key from another, since it is outside that workspace.

What should I do for a team?

Create the avatar once under the workspace your app's key belongs to, record its handle, and have every service use a key from that workspace. Do not paste keys into shared chats. Compare the single-person case in Synthesia personal avatar vs studio avatar.