Key Terms

Glossary: TaskTrain Terms
Updated 1 day ago

User

A User is a unique TaskTrain sign-in profile.

User profile illustration

Account / Organization Member

A User may have one or more Accounts. Each Account makes the User an Organization Member by granting the User access to an Organization with a specific Workspace Access.

One User with multiple Accounts each granting Organization Membership

Organization

An Organization is a workspace comprised of Accounts, Portfolios, Procedures, Resources, and Assignments under a common Billing Plan determining its feature availability.

Organization workspace structure

Workspace Access

Workspace Access grants an Organization Member permission to take certain actions within TaskTrain. The four Organization Roles within TaskTrain are Associate, Lead, Administrator, and Guest.

Note: Guest access is available on paid subscriptions only.

Workspace Access roles overview

Organization Member

An Organization Member may access Portfolios and their Procedures with associated Resources and Assignments according to their Portfolio Access.

Organization Lead

An Organization Lead is a Member who can create new Portfolios.

Organization Administrator

An Organization Administrator is a manager who can add or remove Organization Members and update their Organization as well as Portfolio Access. An Administrator is also responsible for billing.

Organization Guest

An Organization Guest may only be assigned Portfolio Guest Access and made Assignee on an Assignment or Task; they may not see Organization People, Positions, or Billing. Note: Guests are available only on paid subscriptions.

Exchange

The Exchange is a shared collection of public, browsable, and searchable Procedures, which you can copy or purchase. The public Exchange allows you to easily learn from others and to download ready-made Procedures and then tweak them to meet your needs. You can contribute to others as well by sharing the work Procedures you yourself have created!

Exchange of shared Procedures

Portfolio

Portfolios organize Procedures and control the access Organization Members have to the Procedures (and related Assignments) they contain.

Portfolio organizing Procedures

Portfolio Access

Portfolio Access grants permission to take actions on the Portfolio, the Procedures it contains, and the associated Assignments. Portfolio Roles include Guest, Associate, Lead, and Administrator.

Portfolio Access roles overview

Portfolio Guest

A Portfolio Guest may view Procedures and create or request Assignments from them.

Portfolio Associate

A Portfolio Associate may view all Assignments of Procedures in the Portfolio, plus all Guest actions.

Portfolio Lead

A Portfolio Lead may edit Procedures and update Assignments, plus all Associate actions.

Portfolio Administrator

A Portfolio Administrator may add or remove Members and update their Roles, plus all Lead actions.

Procedure

A Procedure is a set of step-by-step work instructions documenting your Standard Operating Procedures, captured in a multi-level outline of Procedure Steps, each of which may contain explanatory Resources.

Procedure with numbered Steps and a Step's Resource visible in the detail pane

Procedure Step

A Procedure Step is a discrete, individually trackable work instruction within a Procedure, which may contain additional explanatory Resources.

Procedure with nested Steps showing the substep hierarchy

Resource

A Resource is reference material associated with one or more Procedures or Steps. A Resource may be Embedded (formatted text entered directly in TaskTrain), Attached (a file upload), or Linked (a website URL). Resources become viewable as a Guide on the Assignment or Task corresponding to the Procedure or Step to which the Resource is connected.

Procedure showing all three Resource types: Linked, Attached, and Embedded

Published Procedure

A Published Procedure is a Procedure that has been marked as Published and can now have Assignments created from it.

Assignment

An Assignment is a unique instance of a Procedure used as a checklist to guide and track work. Each Assignment may have its own Assignee, Start Date, Due Date, Priority, and Completion Status.

Assignment with Tasks at varying completion states

Assignment Task

An Assignment Task is an individual checklist item within an Assignment, corresponding to a Step within the Procedure from which the Assignment was created. Each Task may have its own Assignee, Start Date, Due Date, and Completion Status.

Completion Status

A Completion Status indicator identifies the stages that an Assignment or Assignment Task may pass through: Not Started, In Progress, On Hold, Skipped, or Complete. Changes to the Completion Status of a child or sub-Task automatically update the status of its parent Task, and vice versa. Updating Task Completion Status automatically updates Assignment status, and vice versa.

Completion Status indicators

Completion Category

The five Completion Statuses are grouped into two Completion Categories: Open and Closed, which can be filtered in the Assignments list.

  1. Open: Not Started, In Progress, and On Hold Assignments or Tasks.
  2. Closed: Skipped or Complete Assignments or Tasks.
Completion Categories: Open and Closed

Comment

A Comment is a note made on an Assignment or Task. Comments allow Assignees to communicate, coordinate, and document work at the Task level.

Comment on a Task

Comment Thread

A Comment Thread is a series of related Comments made on an Assignment or Task, similar to an e-mail discussion thread.

Comment Thread on an Assignment

Attachment

An Attachment is a file uploaded with a Comment. Note: This feature is available on paid subscriptions only.

Attachment on a Comment

Inbox — Assignments

The Inbox — Assignments organizes all Assignments for which the User’s Account in an Organization is the Requestor or the Assignment or Task Assignee.

Inbox of Assignments

Inbox — Comments

The Inbox — Comments organizes all Comment Threads a User’s Account in an Organization is included in, either as the Assignment or Task Assignee, or as an explicitly added Follower.

Inbox of Comment Threads
Did this answer your question?