Skip to main content

Accounts, Organizations and Organizational Units

The conceptual Account > Organization > Organizational Unit hierarchy in wxrks, and how it controls who can see and manage which projects, users, and assets.

Every wxrks account is organized into three nested levels: Account, Organization, and Organizational Unit. This structure decides who can see which projects, users, and assets — so it's worth understanding before you start creating Organizations or Organizational Units of your own.

💡 Who is this for? This guide is for Account Admins who need to plan and understand how the Account, Organization, and Organizational Unit hierarchy controls visibility and access within the wxrks platform.


The three levels of your account

From top to bottom, the hierarchy always nests the same way: one Account contains one or more Organizations, and each Organization contains one or more Organizational Units (often shortened to Org Unit or OU). An Organization always belongs to exactly one Account, and an Organizational Unit always belongs to exactly one Organization — there's no sharing a unit across two parents.

  • Account — the outermost container for your whole company's presence in wxrks. It's created for you when you're onboarded, so you won't set one up yourself.

  • Organization — the first sub-layer inside your Account. Most accounts use this to represent a division, brand, region, or major client, depending on how your company is structured.

  • Organizational Unit — the layer directly beneath an Organization, and the level projects actually get created under. Many accounts use one Org Unit per department, team, or client account, but there's no fixed rule — organize them however matches your business.

An Account Admin can create and rename Organizations and Organizational Units at any time — see How to create an Organization or Organizational Unit for the exact steps, All about Organizations for what each Organization tab does, and All about Organizational Units for the full list of Org Unit settings.

An Organization's Hierarchy View tab, showing the Organization at the top with two Organizational Units nested underneath it

An Organization's Hierarchy View tab (shown above) always renders this same shape: the Organization on top, with every Organizational Unit that belongs to it laid out underneath. The names in this example are placeholder test data — yours will show your own Organization and Org Unit names.


How the hierarchy controls visibility and permissions

The level a user is added at determines how much of the Account they can see. This applies to any role — Project Manager, Vendor, and others alike:

  • A user added at the Organizational Unit level only sees the projects, users, and assets that belong to that one Org Unit.

  • A user added at the Organization level automatically sees every Organizational Unit under that Organization — not just one.

  • Account Admins always see every Organization and Organizational Unit in the Account, regardless of where they're individually assigned.

Example: say Organization B contains Organizational Units A and B. A Project Manager added at the Organization B level can see and manage projects in both of those Org Units. A different Project Manager added directly to just Organizational Unit A can only see that one — they'd have no visibility into Org Unit B, or into any other Organization's units, even though all three sit in the same Account.

You manage these assignments from an Organization's or Organizational Unit's Associations / Access Management tab — see All about Organizations and All about Organizational Units for exactly where each option lives.


Where projects sit in the hierarchy

Projects are always created directly under an Organizational Unit — there's no such thing as a project that lives at the Organization or Account level. Translation Memories, Glossaries, and Price Lists are shared assets that a project's Organizational Unit connects to; see All about Organizations and All about Organizational Units for exactly how each is linked.


Can I reorganize this structure later?

An Organizational Unit's parent Organization is set when it's created and can't be changed afterward — wxrks doesn't support moving an Organizational Unit (or its Translation Memories and Glossaries) to a different Organization once created, to protect the integrity of that data.

What you can't do either is delete an Organization or Organizational Unit from the wxrks interface once it's created. If you've created one by mistake or no longer need it, contact [email protected].


Related articles

Did this answer your question?