A role that has all available permissions including full access to account settings and account data. Only Admins can create and edit other Admin users.
A markup applied to an asset during review. This is used to indicate someone has comments about a particular area of a proof. Any markup on an asset within the review environment. Annotations help provide crystal clear context for comments added by reviewers.
A status assigned to a page within a proof denoting the approval status and potential need for revisions.
An annotation tool that places an arrow on an asset. It can be drawn by a user by clicking, dragging the mouse, then releasing.
A monthly view of project, task and proof deadlines.
A collection of projects that are related in some way. They may be supporting the same objective or were submitted as separate deliverables via a campaign request form.
The area in the review environment in which a proof's asset is loaded for review.
Provides collective summary of all conversations, reviewers' comments, and file attachments in the right-hand panel of the review environment. It provides reviewers with ability to like comments, reply to comments or edit their own comments.
A single user input of text that may have an associated annotation. A comment can also be a reply to a prior comment, creating a conversation thread. Only the first comment can have an associated annotation and all subsequent comments are associated with the initial comment.
A status that generally depicts that work is finished.
Group of user-input text threaded to show a relationship to a single annotation or topic.
An annotation tool that places a simple, non-resizable circle on an asset.
An annotation tool that places a custom drawn line on an asset by using the mouse as a pen. It can be drawn by a user by clicking, dragging the mouse, then releasing.
A status that generally depicts that work is active and underway.
This status indicates that the proof is available for review. Any invited reviewers will be able to access the proof to perform a review.
Level of Effort
The amount of time you estimate that a work item will take to complete.
A tool in the review environment that allows reviewers to measure the active asset in pixels, inches and centimeters.
Mentioning or @Mention
A method of notifying a colleague by tagging them within a comment or reply.
A collection of tasks and/or proofs that can be managed as a single item with a shared status, due date, assigned team members and collaboration.
A predefined project setup including project details, tasks, proofs and/or work groups that can be applied to new projects.
A proof represents a draft of a single or multiple assets requiring review and approval that you would like to track as a part of your team workflow. Proofs can be stand-alone or associated with a project. Proofs can be assigned to one or more project team members to complete.
A method of routing proofs through tiers of reviewers based on pre-defined rules.
The proof name shown to reviewers in the review environment.
An annotation tool that places a resizable rectangle on an asset. It can be drawn by a user by clicking, dragging the mouse, then releasing.
The ability to send a proof email reminder to outstanding reviewers.
Customized view of data tracked within inMotion ignite.
A new job that is submitted for approval and associated with a project, task or proof. External stakeholders and internal team members can create new requests.
A form compiled of a series of fields meant to gather information needed in order to understand the scope of requested work.
All reviews of a proof have been submitted and the proof is returned with feedback to the designer.
Asset(s) routed via a proof for feedback and approval.
A group of one or more reviewers within a proof route. Each group can have an assigned number of required reviewers from one user to all.
Route End Date
The date at which a review will expire and prevent reviewers from adding additional feedback or applying an approval status.
A predefined proof route that can be applied to a proof before sending out for review. Route templates can be placed in draft or published mode. It must be published in order to be applied to a proof.
A role type that can be assigned permission to request work and/or review assets. These users require a unique login.
A short phrase that represents the stage that an item falls in to at a particular time.
A keyword or term you would like to associate with a request, project, task or proof that can be used in search or filtering.
A task represents a to-do item that you would like to track as a part of your team workflow. Tasks can be stand-alone or associated with a project. Tasks can be assigned to one or more project team members to complete.
A role type that can be assigned most permissions including those related to project, task, proof and user management. These users require a unique login.
Text Highlighter Tool
An annotation tool that allows the user to highlight text in certain documents. This tool places a colored background behind the selected text and loads it into the associated comment.
Text Strikethrough Tool
An annotation tool that allows the user to highlight text in certain documents. This tool places a line through the selected text and loads it into the associated comment.
A stage of a proof route that can include one or more reviewer groups. Rules can be applied to each tier to that advance the route forward based on submitted approval statuses.
A status that generally depicts that work is not yet started.
The latest iteration of a proof that has been posted for review. Versions can be compared in the review environment to ensure project work is proceeding as expected.
Any task or proof is considered work to be done.
A collection of tasks and/or proofs that are joined together via a work group. Work groups can represent project phases, deliverables, teams, or whatever categories make sense for the project at hand.