SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
SDL TMS is a powerful Translation Management System - and a lot of its power comes from the hierarchical structure.
The ability to have multiple levels (organizations) allows you to decide on:
That's great, but what does that mean in terms of setup? Do I need to create all my objects inside all the various organizations?
Of course different people have different ways of working - but my rule of thumb is: create each object at the highest level at which it is both useful, and allowed.
Admittedly, that sentence could sound a bit like it came from a fortune cookie, so let me explain.
First of all, let's look at what your organization structure should look like:
Root Organization: this level comes out of the box and is mandatory. It should be reserved for any Admin level users and any other objects which come out of the box with TMS (like content types).
Professional Services: Insert your company name here! This will be the main node in your setup - the common ground for all the objects which are widely shareable.
Other organizations: This is where you get to build your org structure; in my case, I have two organizations at the same level (siblings) and both with the same parent (Professional Services org). These are also often called sub-orgs to the Professional Services org, in this case.
At this point, you might be asking: yeah, that's great, but
Organization will normally be related to departments, or business units, or different teams within your company. They can also in some cases be related to different countries/geographical regions - it all depends on what kind of business, or even content separation makes sense in your particular case.
The Main Reasons for Separate Organizations are:
You may also decide on having a set of organizations which reflects the structure of the business that TMS instance is associated with - just bear in mind that you will then have separate reporting and separate visibility across those organizations, so always try to find a balance between getting the results you want, and making it realistic to manage.
Remember to always have your corporate node underneath Root - and then work the rest out from there.
On the next post I will cover how to find the best balance between reusing setup and having the right level of visibility.
In the meantime, stay warm!