Teams and organizations

Everything in Videxo belongs to an organization: its plan and credits, API keys, jobs and their files, uploads, webhooks, usage, billing and support tickets. People are members of an organization, each with one role.

Your organizations#

When you sign up you get a personal organization, with you as its Owner. You can create more from the organization menu at the top of the dashboard's sidebar, and join organizations that invite you. You can own up to 5 organizations; there is no limit on how many you belong to.

A new organization starts on the Pay as you go plan with no credits. Each organization has its own plan and its own billing.

The dashboard shows one organization at a time. Its name and your role there are at the top of the sidebar, and every page (jobs, keys, webhooks, usage, billing, support) shows that organization only. To switch, open the organization menu and choose another one; the page opens again in it. The organization is chosen per browser session: two browsers can show two organizations.

A page left open from before a switch, for example in another tab, does not change anything in the organization you switched to. It says which organization is current now and offers to reload.

Roles#

Every role sees the organization's usage and members and can open support tickets. Pages a role cannot use stay in the dashboard's menu with a lock and the reason. Developers revoke the keys they created; Owners and Admins revoke any key.

Every role can connect an app to the MCP server, limited to what that role may do, and sees and revokes the apps they connected under Settings, Connected apps. Owners and Admins see and revoke every member's.

Only the Owner and Admins invite people and change roles. An Admin can give the Admin, Developer and Viewer roles; only the Owner gives the Billing role. Nobody changes their own role, and the Owner's role changes only by a transfer.

Inviting people#

Owners and Admins invite people under Settings, Members, by email and with a role. The invitation email holds one link, valid for 7 days. The person opens it, signs in or signs up with the address it was sent to, and accepts; the dashboard then opens in the organization. An invitation can be sent again (valid for 7 days from then) or revoked from the same list.

Each plan allows a number of members, pending invitations included: 3 on Pay as you go, 5 on Starter, 20 on Pro and 100 on Scale. A plan change never removes anyone; while an organization is over its limit, new invitations are refused with limit_exceeded (member_limit).

Leaving and removing members#

Any member but the Owner can leave under Settings, General. Owners and Admins remove members under Settings, Members; the Owner cannot be removed. The person is emailed and loses access on their next request.

API keys belong to the organization, not to the person who created them, so they keep working after that person leaves. When you remove a member, the dialog lists the keys they created and revokes them by default; leave that off if an integration still needs them. Jobs, files and tickets stay with the organization.

API keys#

A key acts for the organization it was created in, with the full API: it creates jobs that use that organization's credits, reads its jobs and files, and manages its webhooks. The API has no roles: a key can do everything the API offers, whoever created it. GET /v1/me returns the organization as account:

{ "account": { "id": "acc_...", "plan": "starter" }, "key": { "id": "...", "name": "production-worker" } }

The keys page lists every key of the organization with who created it, so you can tell whose integration a key is. A key of a member who left shows "Former member" with the address they had.

Ownership and deletion#

The Owner can make another member the Owner under Settings, General, by typing the organization's slug; the previous Owner becomes an Admin. The plan, billing and credits stay with the organization.

The Owner can delete an organization by typing its slug. It cannot be deleted while it is your only organization or while it has a live subscription: cancel the subscription under Usage and billing and wait until it has ended. Deleting cancels queued and running jobs, disables every API key and webhook endpoint, and removes every member, who is emailed. Unused credits are lost. Payments, usage and support history are kept, and a deleted organization cannot be restored.

The audit log#

Owners and Admins see what members did under Settings, Audit log: settings, members and invitations, API keys, webhooks, connected apps and billing changes, with who did it and when.