Key concepts

Six ideas explain how AEVU is organised: organisation, workspace, portfolio, programme, project and stage gate — plus roles, which decide what each person can do.

The hierarchy

Concept	What it is
Organization	Your company. It owns the plan, trial, seats, billing and organisation-wide policy for integrations and AI. See Organization.
Workspace	A separate space inside the organisation for a team or client. Each workspace keeps its own projects, members, roles and settings — nothing crosses between workspaces.
Portfolio	A group of related projects, used for reporting and filing.
Programme	A planning layer that groups projects. Managers run projects, not the programme they sit in, so programme access is more restricted than portfolio access.
Project	The unit of delivery: dates, budget, manager, milestones, registers, documents, payments and stage gates.

A project may be filed under a portfolio and a programme. Deleting a programme keeps its projects and simply unfiles them; portfolios are archived rather than deleted.

Workspace and organisation

• One person holds one seat across every workspace of the organisation.
• Your role is set per workspace. You can be an Owner in one and a Manager in another.
• Archived workspaces are locked: their content cannot be changed and they are not reachable from normal screens.

More in Workspaces.

Stage gates

Every project passes through five stages: Initiation, Planning, Execution, Monitoring & Controlling, Closing. To move on, the project manager submits the current stage; the PMO approves or rejects it (a rejection needs a reason).

A stage can have requirements — for example a document that must be provided. A mandatory requirement that is not met stops the stage being submitted, and the dialog names what is still needed. Each workspace can also set a time limit (SLA) per stage; going past it raises an exception.

See Stage gates.

Project health

Health is calculated every time you look; it is never typed in.

• Danger zone — a milestone is overdue, schedule performance (SPI) is below 0.85, or the gate was rejected.
• At risk — SPI below 0.95, a gate has waited five days or more for the PMO, or a risk or issue is overdue.
• On track — none of the above.

See the Glossary for SPI and CPI.

Roles and permissions

Five roles ship with the product — Owner, Admin, PMO, Manager, Finance — and a workspace can add custom roles. Each role is a set of permissions that an administrator can edit (the Owner's cannot be edited). See Roles at a glance and Roles & permissions.

TIP

Without the permission See every project in the workspace, you see only projects you are on — as manager, sponsor or creator, or on the delivery or finance team. A project you cannot see looks exactly like one that does not exist.