In this article, we will provide a comprehensive overview of both the existing configurations and the available options that can be implemented within an organizational unit.

If you need to learn how to create an Organizational Unit, please refer to the following article:

After creating the Organizational Unit, we can access and view various configurations. The first available tab is General.

In the General tab, you can include more direct information about the Organizational Unit, such as its name and address. Bureau Works allows users to define their own method of organization, so Organizational Units may not necessarily be companies with a physical address. Therefore, most of these fields are not mandatory to fill out.

It is not possible to alter the foundational creation details of assets, such as the parent organization of an organizational unit. Bureau Works does not support the transfer or movement of these data elements to ensure the utmost protection of user data and assets. This policy aligns with our commitment to maintaining a secure environment, adhering to the highest standards of data integrity, and complying with SOC 2 Type 2 certification requirements.

An organizational unit has numerous associations and correlated metadata, and to prevent any disruption or unauthorized access, these associations are considered definitive and cannot be modified.

Within this tab are settings that function as default configurations for the Organizational Unit. These settings will be automatically applied across all projects. However, during project creation, you will still have the opportunity to modify them as needed.

1. Contact Person: Sets the point of contact of every project created under this Org. Unit. The Project Manager is normally the point of contact.

2. Source Language:Set the default source language. This setting speeds up project configuration by defaulting to the language indicated below; however, it can be changed manually for each project if necessary.

3. Target Languages: Set the language to which the project should be translated. Multiple languages can be selected. This setting speeds up project configuration by defaulting to the language indicated below; however, it can be changed manually for each project if necessary.

4. Regular expression/Override Default Regex: Also known as Regex, they are a sequence of characters that define a search pattern, allowing you to perform complex searches and replace operations in strings. Essentially, the regex will determine which segments of your content need to remain accessible for translation and which segments should be transformed into tags. When the option Override Default Regex is enabled, the informed expression will override the default configuration.

5. Continuous Tags: You can determine which will be the corresponding tags for projects created via connectors.

6. Count 100% TM Match Over Repetition: If enabled, 100/101% segment matches will not be considered as repetitions when the logfile is calculated for every project created under this Org. Unit.¹

7. Ignore Subsequent Non-Translatable as Repetitions: If enabled, all Non-Translatable segments will be considered as non-translatable, and their subsequent non-translatable segment will not be considered as a repetition.¹

8.Continuous Project Configuration: This option allows you to standardize the prefixes/suffixes that should be included in the translated file name based on the language. When downloading a translated file in the pt-BR language, for example, the translated file name can be pt_br/filename>, standardizing file nomenclature.

9. Filter Settings: Allows you to create standardized custom filters for new projects created under this Org. Unit. You can learn more about Project Filters here.

10. Credentials For Web Preview: Credentials to access the web preview in the Editor.

¹ Depending on the logfile and net rate settings, it may have an impact on the project's overall cost.

This tab allows you to configure information about project expenses.

1. Charge By Words or Pages: A project can be charged by the number of words or by the number of pages. Charging by pages is mostly used for DPT workflow.

2. Words per Unit: It is possible to specify the number of words that the system considers each billing unit to contain. If pricing per word, for example, this setup is set to one word per unit. If you are charging per page, you can assume an average number of words per page and enter that value here, for example, 50 words per page.

3. Currency: Specify in which currency the value will be set.

4. Show Requester Name: When enabled, it will display the Client's name on the invoice after the delivery of the project.

5. Delete/Add: At least one price list needs to be included for the Organizational Unit. The price lists must first be linked to the parent Organization of each unit.

6. Price list: Displays any price list that is associated with Organizational Units. It is possible to verify its Name, its Currency, its Minimum Fee setting, its Default Price per item, and its Minimum Fee value.

7. Default: To expedite project formation criteria, you can make a price list the default one.

If you need to learn more about price lists, please refer to How to create a Price List in Bureau Works.

The billing information can be specified on this tab. This is where you can provide the recipient's information to be included in the invoice generated after the job is completed.

1. Auto Billing Enabled: When enabled, the system will automatically send an invoice to the billing contact.

2. Send invoice to Requester: When enabled, the invoice will be sent to the project's requester instead of the billing contact.

3. Send Email Notification: Will send a email notification to the select billing contact whenever a new invoice is created.

4. Require Purchase Order: When enabled, the platform will require a PO number in order for the project to be approved. The PO number is indicated in the project creation or in the Costs tab.

​​
5. Consolidate Invoice: When enabled, it will display consolidated information if more than one project is considered for invoicing.

6. Use User's Account Info: When enabled, this button allows you to create a receivable using the logged-in user's account information instead of the default account settings.
(Manual creation only)

7. Billing Contact information:

If you want to learn more about the Accounting section, please refer to How to manage the Accounting Section.

In this tab, we can add users associated with the Organizational Unit and also see the listed existing associations.

1. Search/Add User: You can search for a new user by their name and associate them with the Organizational Unit by clicking on the Add User (+) button.

2. The already associated users have their name and email listed.

3. You can easily remove an association by clicking on the delete button.

If you need to learn more about users, please refer to Creating a User in Bureau Works.

We have numerous translation settings and a greater number of combinations that can be applied.

These settings can be pre-defined per Organizational Unit, but can also be altered directly on the project.

1. General

2. Auto Translate From

3. Segments

You can choose to standardize the expected behavior of segments with high matches. This can optimize the linguist's work, preventing the translation of already saved TM content, for example.

4. Unlock options

Theses features only applies to the Organizational Unit, although they are visible at the project level, and only affects the project once it has been created. After creation, changing these settings will have no impact on projects.

5. Mismatch Warnings

²Does not affect the QA checks warnings.

To learn more about the settings at the project level, please refer to Project's Translation Settings.

In order for a project to have an associated translation memory or glossary, it must first be associated to their Organizational Unit. This can be done by going to the Context tab.

1. Delete/Add: You can select and delete an already associated TM, or search and select a new one. The TM must first be linked to the parent Organization of each Organizational Unit.

2. Translation memory: Displays any TM that is associated to the Organizational Unit. It is possible to verify its Name, and its Source and Target languages.

3. Default: Make this the default TM for all projects.

4. Read: Make its content available in the Editor, to be used to populate segments.

5. Write: Allow the confirmed segments content to be saved in the TM.

6. Penalty: Applies a percentage penalty in the TM matches.

7. Threshold: Establishes a minimum percentage match threshold for segments to appear in the Editor's suggestions tab, making them accessible for application by linguists.

8. Creation date: Displays the creation date of the TM.

To learn more about translation memories, please refer to How to handle Translation Memories in Bureau Works.

In order for a project to have an associated glossary, it must first be associated to their Organizational Unit. This can be done by going to the Glossaries tab.

1. Delete/Add: You can select and delete an already associated glossary, or search and select a new one. The glossary must first be linked to the parent Organization of each Organizational Unit.

2. Glossary name: Displays any glossary that is associated to the Organizational Unit. It is possible to verify its Name, and its Source and Target languages.

3. Default: Make this the default glossary for all projects.

4. Creation date: Displays the creation date of the glossary.

To learn more about glossaries, please refer to How to create a Glossary.

It is possible to personalize the Net Rate Settings at the Organizational Unit level.

This configuration can impact how project costs are calculated and how much should be charged and paid for a service. The percentage to be paid to linguists based on TM and MT/AI utilization can also be adjusted.

1. Edit Coefficients: Allows you to select your own coefficients for payment calculation.

2. Payment Logfile Type: Allows you to select if the projects created under this Org. Unit will use pre-analysis or the post-analysis logfile. You can learn more about logfiles here.

Account_admin users do not have access to this setting; nevertheless, if you need to update it, please contact the Bureau Works support team at [email protected].

Our platform allows the user to personalize it's Machine Translation provider. This setting needs to be done first at the Account level, by inserting and saving the user's provider API key into Bureau Works. After that, it can be granularly defined by the Organizational Unit level.

There are two ways to configure the MT: one is defining the new default provider, and the other is by setting it by language pair.

1. MT Settings by default: Allow the user to select a new default provider among those previously configured in the account.

2. MT Settings by language pair: Displays the already set language pairs.

3. Add Lang Pair: A pop-up window will show up for configuration. See below:

1. Select the new provider;

2. Select the source language and the target language;

3. Set as an active configuration.

It is possible to use different providers to different language pairs.

To learn how to configure the MT provider in you account, please refer to the article Bureau Works Machine Translation integration.

This last tab allows you to personalize the segmentation of the files at the Organizational Unit level.

The Bureau Works Editor has several common segmentation criteria that determine how the file's information is split in order to fill the segments for the linguist to work on. It is possible to personalize these rules to adjust this behavior, allowing segmentation to work alongside translation while maintaining the content's sense.

If you need to customize these rules, please contact our support team at [email protected] and we will assist you in determining the best approach to do so.

The Bureau Works LLM can also be called Bureau Works Generative Language Engine and its stands as the cornerstone of our suite, providing unrivaled power and efficiency. By seamlessly combining Translation Memories, Machine Translations, and Glossaries into a unified, smart, and context-aware feed, it transforms the way you work, learn, and interact. You can learn all about Bureau Works LLM here.

1. Enable Augmented Translation Actions: Enables or disables support for Augmented Translation/Review in the editor. Note: The owner account of this org.unit must have this property enabled to activate this option.

2. Enable Sending Learned Terms To Terminology Board: Enables or disables sending learned terms to the terminology board. Note: The account that owns this organizational unit must have this property enabled to activate this option.
​​
​

Bureau Works allows the user to define those specific steps and tasks in the moment of project creation or when uploading new files to an already existing project. Thinking about flexibility and optimization, the Bureau Works platform allows you to set custom Workflows. The Workflow is a predefined set of steps and tasks, and you can create your own custom Workflows based on the file type that is being uploaded, so you don't need to set those steps every time a new demand arrives.

1. Add a New Configuration: Allows you to create a new configuration;

2. Delete a Configuration: Allows you to delete the existing configurations;

3. Custom Workflows: Allows you to modify the configurations you've created before.

By expanding the Custom Workflows tab, you will be displayed with further settings:

1. Choose a Configuration: Choose between already existing configurations;

2. Workflow: Choose the file extensions that will load the determined workflow when creating a new project;

3. Add a new workflow: Allows you to add a new workflow step (Review, Editing) and then associate file extensions to them.

4. Delete button: Allows you to delete a workflow from your configuration.

You can learn a lot more about Custom Workflows here!

Bureau Works also allows you to send email Notifications for the project's stakeholders when certain events happens.

Bureau Works also allows you to add metadata on it's entities, including your Organizational Unit. You can learn All About Custom Fields here.