Team and developer settings

Members and roles

Open Settings, then Team. Members lists everyone in the workspace and their Role:

• owner: everything an admin can do, plus managing other owners and deleting the workspace. Every workspace keeps at least one owner.
• admin: billing, connecting and changing apps, the team, API keys, webhooks and the workspace settings.
• member: making videos of the workspace’s apps, fixing and sharing the videos they made, and connecting an AI assistant.

To add someone, fill in Invite a teammate with their Email address and Role, then choose Send invite. They get an email with a link to join. You can send a pending invite again with Resend, or cancel it with Revoke. A workspace can send up to 20 invites a day, resends included, and only owners can invite owners.

To change someone’s role, pick it and choose Save. To take them out of the workspace, choose Remove. When someone leaves, their API keys and AI assistant connections are revoked too.

Workspace settings

Settings → Workspace holds the Workspace name your team sees: change it and choose Save. Below it, the Brand colour is used for the bands above and below vertical videos. Enter a hex colour and choose Save brand colour. Leave it empty for the default dark slate, #1f2937. Owners and admins can change both.

API keys

Settings → API is where owners and admins make keys for scripts and release pipelines. It unlocks once your workspace has bought credits (a pack or a plan).

1. Under API keys, give the key a Key name, such as the tool that will use it.
2. If you like, set a Daily cap in credits (optional): the most the key may spend each day (UTC).
3. Choose Create key, and copy the key straight away. It’s shown only once.

A key acts as the person who made it, and it pays from the workspace’s credits. You can have up to 20 keys. To change a key’s daily cap later, edit it in the key’s row and choose Save. Revoke stops a key at once and moves it to Recently revoked. A key also stops working if the person who made it is no longer an owner or admin.

Webhooks

Under Webhooks, enter an Endpoint URL and, if you like, a Description (optional), then choose Add endpoint. We send it these events: video.ready, video.failed, video.cancelled, app.needs_reconnect. To pick which ones it gets, open the endpoint. Copy the signing secret straight away. It’s shown only once. To replace it, open the endpoint and choose Rotate secret. You can add up to 5 endpoints. How to check the signature is in the API reference.

The API reference

Every endpoint, the video object, errors and limits are in the API reference. To make videos from Claude, Cursor or ChatGPT instead, see Using the MCP.