When a member is removed from a workspace or organization, Synthesia disables the API keys that the member owns. Integrations that use those keys stop working until you replace or re-enable the keys.
When Synthesia Disables a Member's API Keys
Synthesia disables a member's API keys when the member is removed in any of these ways:
An admin removes the member in Workspace settings or Organization settings.
SCIM or SAML group sync removes the member.
The member leaves the workspace.
Synthesia removes the member, for example after a plan downgrade.
The scope of the removal decides which keys Synthesia disables:
Removal from one workspace disables the member's keys in that workspace only.
Removal from the organization disables the member's keys in every workspace.
What You See Before Removal
When an admin removes a member who owns active API keys, the remove dialog shows a warning. In Workspace settings, the warning reads "2 API keys will be disabled". In Organization settings, the warning reads "2 API keys across 3 workspaces will be disabled".
A member who leaves a workspace on their own sees no warning.
What Happens After Removal
After a member is removed, these changes apply:
Integrations that use the disabled keys receive the same error as an invalid key.
Workspace admins receive an email that lists the disabled keys, no more than once per hour. If the workspace has no admin, organization admins receive the email.
The removed member receives no email.
In the API keys list, Removed appears next to the key owner. To see the removal date, select the Disabled status and find the entry "Owner removed" with the date.
In Audit logs, the entry reads "Disabled the API key [key name] owned by [owner name]".
How do I replace a disabled API key?
To replace an API key that Synthesia disabled after a removal:
Ask a member who is staying in the workspace to create a new key on the Developers page.
Switch the integration to the new key.
Go to API keys.
Select the ... menu next to the old key.
Select Delete, and then select Delete key.
✍️ Deleting an API key cannot be undone.
How do I undo a removal?
To restore a removed member's API keys:
Add the member back to the workspace.
Go to API keys.
Select the ... menu next to each key, and then select Enable.
Enable is unavailable while the key owner is not a member of the workspace, so add the member back before you enable the keys.
💬FAQs
Why did my integration stop working after a member left?
Why did my integration stop working after a member left?
An integration stops working after a member leaves because Synthesia disables the API keys that the member owned when the member was removed. To restore the integration, replace the key with a new key from a member who is staying.
What are inherited API keys?
What are inherited API keys?
Inherited API keys are keys that Synthesia moved to an admin when the key owner was removed, before Synthesia began disabling keys on removal. These keys show "Inherited from a previous owner" in the API keys list, and the Inherited filter finds them. Inherited keys still work, so review each key.
What happens to API keys when an account is deactivated?
What happens to API keys when an account is deactivated?
Deactivation already disabled all of the member's keys before this change. The keys show "Owner deactivated" and can't be enabled while the account is deactivated. Admins get no email.