Organisations
An organisation owns projects, moderation policies and billing, and its members share them. Every account starts with a personal organisation, so you can work alone without setting anything up; create a team organisation from the portal menu when you work with others, and manage its members in Portal › Organisation.
Roles
| Action | Owner | Member |
|---|---|---|
| See the organisation and its members | Yes | Yes |
| Work on projects they're invited to | Yes | Yes |
| Own every project in the organisation | Yes | No |
| Create projects and moderation policies | Yes | No |
| See usage, invoices, cards and credit; change spend limits and auto top-up | Yes | No |
| Invite people, change roles and remove members | Yes | No |
| Move projects to another organisation they own | Yes | No |
Within a project, members have the project roles described in Members and permissions. Accepting a project invitation also makes you a member of the project's organisation. An organisation can have several owners and always keeps at least one; your personal organisation always keeps you.
Billing
Usage in every project is billed to the project's organisation: its free uploads, its card, its prepaid credit, its spend limit and its usage tier. It doesn't matter who uploads or which API key sends the request. Owners receive the organisation's billing emails.
Moderation policies
Saved moderation policies belong to the organisation, so all of its projects can use them. Owners create and edit them; editing a policy changes it for every project that uses it.
Moving a project
An owner of both organisations can move a project between them in Project settings. The move takes effect immediately:
- Usage up to the move stays with the old organisation. Uploads, storage, delivery and search from then on are billed to the new one.
- The project's moderation policy is copied into the new organisation. A policy that follows its preset keeps following it there.
- Project members who don't belong to the new organisation lose access to the project, and their pending invitations are revoked.
API keys, connectors, upload presets and the project's data are unchanged.
Leaving and removing members
Owners can remove members, and members can leave an organisation themselves. Leaving or being removed ends access to all of the organisation's projects. Deleting your account deletes the organisations you alone own; make someone else an owner of a shared organisation first.