Creating an organization

Any user can create an organization. Once it exists, you invite members, assign them roles, and work from the organization’s context: projects created there are shared with the team and billed at the organization level.

Create the organization

On the Organization page, click Create org and give the organization a name and a seat limit. You become the organization’s owner and occupy its first seat.

Seats are how membership is counted against the limit: every active member holds one. A pending invitation does not consume a seat — the seat is taken when the invitation is accepted, and freed when a member is removed. When all seats are taken, new invitations cannot be accepted until one frees up.

Roles

Organization tiers

Every member has one of four tiers:

• Owner — the person who created the organization (one per organization). Only the owner manages membership: inviting and removing members, changing tiers, and revoking invitations. Owner-only project actions include deleting a project and transferring its lead PM.
• PM — project managers. PMs manage the organization’s work: projects, workflow templates, rate cards, and clients. Only PM-tier members can be added as a project’s co-PMs.
• Translator and member — the base tiers for people who carry out assigned work.

Every active member, whatever the tier, can see and open the organization’s projects. Doing more than reading requires the matching role: managing a project takes a PM, and editing content takes an assignment (below).

Roles on a project

Organization projects distinguish:

• Lead PM — the project’s designated owner. Only the organization owner can transfer the lead to another PM, and only owner-level users can delete or restore the project.
• Co-PMs — additional PMs on the project. A co-PM can do everything the lead can, except delete the project or transfer the lead.
• Per-stage roles — people are assigned to a file’s target language at a specific workflow stage, in a specific role: translator, reviewer, or proofreader, matching the stage’s work. Editing rows requires an active assignment at the row’s current stage (PMs can always edit); advancing a stage requires the stage to be complete and the caller to be assigned to it or a PM.

Removing or suspending a member takes effect immediately — access is checked on every request, so a removed member loses the organization’s projects at once.

Invitations

Membership is consent-based: nobody joins an organization without accepting.

1. The owner invites. In the Members tab, choose Invite member, find the user by name, and pick their tier. The invitation is created as pending — no seat is taken yet.
2. The invitee is notified. The invitation appears as a notification, as a badge on the context switcher, and in the pending invitations panel on the Organization page, showing the organization, the offered tier, and who invited them.
3. Accept or decline. Accepting makes them an active member and consumes a seat (it fails if the organization is full); declining discards the invitation.
4. Or the owner revokes. A pending invitation can be revoked from the Members tab at any time before it is accepted.

Switching between contexts

The context switcher (top right) selects what you are working as: your personal context or one of your organizations. The switch is global — projects, offers, resources, and notifications all follow it, whichever page you make the switch from.

The active context also decides where new projects go: create a project while in an organization’s context and it is an organization project; create it in personal context and it is personal. The two differ in exactly the ways this chapter and Organizations describe:

	Personal project	Organization project
Visible to	people explicitly on the project	every active member
Staffing	offers (Offers & assignment)	internal assignment, or offers for externals
Billing	you	the organization
Workflow templates	global and your own	global and the organization’s