Organizations

An organization lets you work as a team: shared projects, members with roles, and billing handled at the organization level instead of per member. If you run projects alone, you don’t need one; the moment several people share the same projects, rates, and clients, an organization is the container for all of it.

Organization context vs personal context

You always work in one context at a time: your personal context, or one of your organizations. The context switcher (top right) moves between them, and the switch is global — projects, offers, resources, and notifications all follow the active context. A project created in an organization’s context belongs to that organization; one created in your personal context is yours alone.

In personal context, the Organization page shows what an organization unlocks; in an organization’s context it shows the real thing: everything about the organization in one place, one tab per area — Members, Projects, Workflows, Rates, Clients, Workload, and Reports.

To set one up, see Creating an organization — it also covers roles, invitations, and switching in detail.

Members

The Members tab lists everyone in the organization: their role tier (owner, PM, translator, or member), whether they hold a seat, and their status. Members occupy seats up to the organization’s seat limit; a pending invitation does not take a seat until it is accepted.

The owner manages membership here: invite people (by name search, choosing their tier), change a member’s tier, revoke a pending invitation, or remove a member — which frees their seat and takes effect immediately. The full invitation lifecycle is described in Creating an organization.

Projects

Projects created in the organization’s context are organization projects: every active member can see and open them, and the work is billed to the organization. The Projects tab lists them, shows each project’s cost estimate — estimated usage against what the organization’s plan includes — and lets a PM approve the estimate when approval is required.

Staffing an organization project has two lanes:

• Internal assignment — assign a member to a file’s target language and stage directly. No offer, no negotiation, and no per-offer billing between members: it is simply the team’s work, covered by the organization.
• External offers — for people outside the organization, the normal offer flow applies, billed to the organization.

Workflows

The Workflows tab manages workflow templates — the stage sequences projects run through (for example translate, then review). It lists the templates visible in the active context: global templates provided by the platform, plus the organization’s own.

Owners and PMs can compose new templates from the available stage types. Each stage can optionally carry a QA gate: advancing past the stage either warns about or is blocked by unresolved QA issues at or above a severity you choose. A final PM review stage is appended to every template automatically. You can clone a global template into the organization to customize it, and deactivate templates the organization owns.

Projects pick a template at creation, so a shared template is how an organization standardizes its process — see Translation setup.

Rates

The Rates tab holds the organization’s rate cards: named cards with a per-word rate and currency, one of which is the default. Quotes and automatically placed offers resolve the default card when no explicit rate is given, so the default card is effectively the organization’s price basis.

Each card also carries the CAT billing matrix — the per-band multipliers applied to translation-memory matches, fuzzy matches, repetitions, copied rows, and new content (see the volume breakdown for what the bands mean). Owners and PMs can edit the matrix per card: a blank cell inherits the platform default, and the editor warns when a value falls below the platform floor for translator offers — offers never pay a band below that floor, while customer quotes use the card’s values as-is.

Owners and PMs manage cards; other members see them read-only. Personal (non-organization) projects always use the platform defaults — there is no per-project matrix.

Clients

The Clients tab is for the customers your organization translates for. A client record holds contact email addresses and a set of linked projects, and those two things define the client portal: each contact signs in with a magic link — a single-use, time-limited sign-in link a PM copies and shares — and sees the linked projects’ status and downloads, nothing else.

• Add a contact to give someone at the client access; disable a contact to end it.
• Link a project to make it visible in that client’s portal; unlink to remove it.
• Deleting a client ends its portal access immediately.

Client management requires the owner or PM role.

Workload

The Workload tab shows who is carrying what across the organization’s projects: each person with active assignments, flagged when any are overdue or at risk. Expand a person to see their assignments — project, file, target language, stage, role, and due date. It is the view to check before assigning more work.

Reports

The Reports tab summarizes delivery across the organization’s projects over a 30, 90, or 180-day window: the mix of project statuses, on-time delivery (how many deliveries met their deadline), translated volume by language pair, and throughput over time. The scope follows the active context, so the same view in personal context reports on the projects you manage yourself.

Billing

Work on organization projects is billed to the organization, not to the member who happens to run it, and internal assignments involve no per-offer billing between members at all. Plans, credits, and usage are covered in Billing & plans.