1. Accounts Concept 

In Bureau Works, we have a concept called Accounts. 

An Account is an entity that allows users to Group other sub-entities within it, like:
Vendors, Departments, Clients, etc

The Account concept was created to:

• Give more flexibility when creating different entities in the system

• It also allows the Account Admin to structure the Account Tree and users in a way that will work best for his use case

2. Accounts Structure (Organizations and Organizational Units)

An Account has two sub-layers:

• The first layer is the Organization

• The second layer is the Organizational Unit

This is how a basic Account structure looks like:

In this structure, the Account Admin can make decisions on how to organize the users that will belong to the Account and also the Assets (Translation Memories, Term Bases and Price Lists).

For example:
The Account Admin can add a user with the Project Manager role at the Organizational Unit level, but not at the Organization Level, with that, this Project Manager will only have visibility/access to the projects/users/assets in the Organizational Units that he/she belongs to.

On the other hand, if the Project Manager is registered at the Organization level, this Project Manager will have access/visibility on all projects/users/assets in the Organizational Units that are part of that Organization.

To Illustrate the example, above, please refer to the following image:

As you can see, the user Project Manager 1 was registered in the Organization B and with that, the Project Manager 1 will also have access to the Organizational Units A and B, since both belong to the Organization B.

The Project Manager 1 will not have any visibility or access to Organizations A or C users, projects or assets.

The same rule will be applied to users with the role Vendor (linguists).

Account Admins, on the other hand, will have full access to all Organizations and Organizational Units in a given Account.