Concepts we use

This topic contains a list of concepts that are useful in understanding how inheritance works.

Folders

  • Location/Folder = the place where you save your resources

    An account consists of two default locations or folders: Root and Customers.

    You can add as many locations/folders as you like under the Customers folder. Save your resources in the location/folder of your choice to keep your account organized and to enforce the rules of access and visibility.

  • Root folder = the highest location in the hierarchy
  • Customers folder = the location where you add the clients or departments which request translation work from you
  • Home folder = the folder where a resource is saved (also known as current folder in the UI)
  • Parent folder = the folder hierarchically above the Home folder (and by extension any hierarchically superior folder)
  • Child folder = the folder hierarchically below the Home folder (and by extension any hierarchically inferior folder)
  • Brother folder = the folder which has the same parent as you Home folder
  • Public folder = the default status of all folders

    The resources inside a public folder are visible to users from the folder and below.

  • Private folder = the customized status of a folder

    The resources inside a private folder are visible to users from that folder, but not to users from any folder below.

Account access and visibility

  • Access = the property which allows users to work with account resources

    Users receive access to the account by being included in a group.

  • Permission =the property which determines the actions users can perform in an account

    Users receive permissions via their role. Some roles have more permissions than others.

  • Inheritance =the propagation rule which gives users the ability to have visibility over and work with resources in the account hierarchy

    Users can work with the resources available in the Home folder and from above the Home folder.

    Users can work with the projects in their Home folder and below. Users cannot see or work with the projects located above the home folder.

  • Visibility =the property which differentiates between public folders (locations) and private folders (locations)

    All folders are public by default. This means that they are visible to users from that folder or below.

    Folders can be made private, which means that they are visible only to users from that folder, and not to any users from below folders.

Users, groups, and roles

  • User =the individual who is part of one or more groups

    The place where users are saved as part of group is called the Home folder (also known as current folder in the UI).

  • Group =an entity which brings several users in one place and associates users with roles.

    A group is saved in a folder (location in the hierarchical account structure) and can have one or more roles. RWS recommends that you associate one group with one role.

  • Administrator =the most powerful role associated with the Administrator group

    There is a unique Administrator group in the Root folder. Administrators have system-wide scope and can do anything, anywhere, and anytime.

  • Lead Project Manager =the role associated with the Lead Project Manager group

    The Lead Project Manager role has the same set of permissions as the Administrator role, but a narrower scope confined to the customer folders where the Lead Project Manager group can be created. Administrators can create Lead Project Manager groups in any customer folder.

  • Project Manager =the role associated with the Project Manager group
    The Project Manager role has fewer permissions than an Administrator or Lead Project Manager role. The scope depends on the location of the Project Manager group:
    • If users are located in the default Project Manager group located in the Root folder, they will have wider scope.
    • If users are located in the Project Manager groups that can be created in customer folders, they will have narrower scope.

Project resources

  • Workflow = a series of steps (user tasks) and transitions which show how the content is processed from submission to delivery
  • Translation Memory = a linguistic resource which stores and manages the translated content in the form of segments for future reuse
  • Termbase = a linguistic resource which stores and manages the specialized terminology
  • Language Processing Rule = an entity which specifies how currency, abbreviation, punctuation, and other non-linguistic items should be handled when localized from a source to a target language
  • Translation Engine = a combination of linguistic resources meant to be reused

    Translation Engines consist of one Language Processing Rule, one or more Translation Memories, one or more Termbases, and any Machine Translation engines integrated in the account.

  • Custom Field = a label that can be applied at project level in order to facilitate easy search and filtering
  • Project Template = a combination of project resources meant to be reused

    Project Templates consist of one Workflow, one Translation Engine, and one or more Custom Fields.

Account resources

Account resources = project resources + users + groups

Project

Project = a combination of project resources and user/group assignments to tasks which need to be performed as part of an end-to-end localization workflow