People, projects and jobs

People

People are users/accounts in Plint. They could represent an in-house resource or an outside freelancer, a project manager or a client contact representing a company. They could also be a vendor – a company providing a service. All People can be assigned Jobs in Plint. 

Accounts are divided into four types

Workbench

• • Root / admin users, with access to all projects, accounts and data

Manager

• • A customisable login type which can potentially access all the same tools and data as a Workbench user
    • But cannot manage other Manager/Workbench accounts
  • Access can be set for:
    • Specific tools/pages
    • Projects or People matching certain criteria
  • A built-in limitation is that Manager users cannot edit the properties of Workbench and Manager user accounts. 
  • A typical example would be a project manager who only sees projects and resources with certain target languages or for a certain client company. They could handle both the projects and the relevant pool of freelancers. 
  • Another example would be a finance manager with access only to relevant tools, such as reporting and rate cards.

Client

• • Typically a person representing a client company.
  • This account type has read access to all projects for the same company and some tools not available to Resource users. 

Resource

• • An in-house or external user or vendor responsible for specific Jobs. 
  • Resource users do not have access to overall project information and the general progress. I
    • nstead, all necessary information to complete a job is visible in the context of the job itself. 

Projects

A project in Plint is something that needs to be done: typically media in need of localization. This might be a single film or an entire series, including supplementals. The project serves as a container for all the information about the project, such as number of episodes and their running times, the source language and the target languages.

Who sees what?

• As a Workbench or Manager user, you have full access to all information within the scope of that project, 
  • This includes general project data, files and jobs as well as notes and messages linked to individual jobs on the project.
• As a Client user, you can create a project by placing an order. After this point, changes to the project need to be done by a project manager but you can always follow the general progress of the project. 
  • You also have access to a client Filezone where relevant files for all parts and languages can be made available. 
• As a Resource user, you have no overview of the project itself, only jobs assigned to you. All information and files necessary to complete a job are made available within the scope of the job.
  • (Some basic Project information is automatically visible to all job owners; such as project title and project manager.)

Jobs

A job is a step that needs to be performed in order for a Project to be completed. Typically a translation job assigned to a freelancer, or preparatory work assigned to a project manager. But it may also be an automated task represented as a job in the workflow: a process. 

How a job is done in the system is decided by its Delivery method (sometimes called its Action). A job can only have a single method, and the choice will have great impact. From the "Report" method, which simply lets a user click a button to mark it as done (for offline work, for example), to "Online editing" which opens a built-in subtitle editor, or automatic jobs such as "Auto-render subtitles". 

They all have in common that on completion they are set to Done, allowing the next job (or jobs) to begin. 

Joblists

Jobs are linked to projects in interlinked chains called joblists. These can be created manually, or automatically using Joblist templates, based on project data. 

A number of consecutive Jobs linked to a Project. Jobs are typically assigned to People, but may also represent an automated step.