RealAdvice

WarpCore

WorkFlow PM

/

Company Settings

Screen

Company Settings

The company's settings, which everyone reads and company administrators change: the required MEA version.

What you need to know

Company Settings holds the settings that apply to the whole company. Today it holds one: the required MEA version, the oldest version of the Master Engagement Agreement that a client's signed MEA may be and still count as current. Everyone can read it. A company administrator changes it.

The required version measures; it never stops work. Three places compare each client's MEA with it: the MEA pill of each party on an engagement's page, the Buyer MEA and Seller MEA columns of the Weekly Project Review, and the KPI Signed current MEA before closing on Department health.

How to get here

In the left menu, open WorkFlow PM and select Workflow Templates. At the top right, select Company settings. The button shows to everyone who can open Workflow Templates.

What is on this screen

Part
What it shows
Required MEA version
The version, such as 3.1. A company administrator sees it in a box, with Save beside it. Anyone else sees the version as text.
The sentence under it
What counts as current, and the three places that compare each client’s MEA with it.
The last line
When the version was last changed and by whom. Until a company administrator sets it, the line says “Not set yet. Until a company administrator sets it, no client's MEA is judged.”
No records

What you can do here

Who can do what here

Everyone reads the required version. Only a company administrator changes it: a department manager, a contributor and the executive observer see it as text, with no box and no Save. See Who can see and do what.

Things to know

  • A version is numbers separated by dots, with or without a leading v: 3, 3.1, 3.1.2 or v3.1. It is compared number by number, never as a decimal: 3.10 is later than 3.2, and neither is 3.1.
  • A required 3.1 accepts 3.1 and every 3.1 variant, such as 3.1.0 and 3.1.4, and every later version, such as 3.2 and 4.0. It does not accept 3.0.
  • A signed MEA with no version recorded does not count as current.
  • Until the version is set, no client's MEA is judged: the MEA pills are gray, the Weekly Project Review never asks to Update MEA, and the KPI reads Not measured yet.

Good to know

A new MEA for new clients does not have to make every long-standing client out of date. To keep an older version acceptable, leave the required version at it: clients on the new version still count as current. Raise it when every client should be on the new version before their next closing.