Projects Menu
- Copy Space for Confluence (Unlicensed)
- Kenny Teves
- Aaron Sakievich (Unlicensed)
- Laura White (Unlicensed)
Overview of Projects
Inside the Enterprise TMS, Projects have three primary purposes. Projects:
Organize content.
Control how content interacts with the system (and connectors).
Control how users interact with the project and content.
Organizing content
Organizations can create as many projects as necessary. You can create projects for every marketing campaign, for every PO, or your different content sources (e.g., an AEM project and a Marketo project).
Content interacting with the TMS
Project Settings control how content interacts with the TMS as well as other integrations by determining:
How different file types are imported into the TMS.
The default Workflow to use to translate source content into various targets.
Which project resources are used in the translation process.
Which third-party tools are communicated with, and when.
Users interacting with the project and content
Project Settings also control how users interact with content by:
Determining the permissions project managers and vendor project managers have in the project.
How users upload new documents to the system.
What linguists can and cannot do when working on tasks in the project.
Documents and Targets
Inside the project itself, there are documents (source files that have been uploaded to the TMS for translation) and targets (the locales your source file is being translated into). Inside the Projects menu, project managers and community admins can monitor and take action on documents, targets, and phases on an individual and bulk level. We have provided an enormous set of tools and actions that can be used to make managing content simple in our system.