Skip to content

Navigate the Project Workspace

The Project workspace groups related work into seven primary areas. It keeps navigation stable as optional capabilities are enabled, while hiding sections you cannot use.

  • Summary: lifecycle, journey, health, waiting on, progress, next action and key operational cards.
  • Setup & Start Readiness: Draft setup and Awaiting Start gates.
  • Activity: permission-filtered audit history.

Use milestones, the dense task List or Board, saved views and bulk planning. Select a task to open its inspector without losing Project context, or use its stable direct workspace for deeper execution.

When enabled, use role requirements, proposed or confirmed staff allocations and capacity signals. The tab can appear as Resource Plan · Off when the capability is available but not enabled for this Project.

  • Deliverables & Reviews for immutable versions, formal decisions and release.
  • Client Collaboration for messages and action items when enabled.
  • Appointments for fixed scheduled work.
  • Change Orders for approved changes after commercial hand-off.
  • Project Team controls internal membership and assignment eligibility.
  • Client Stakeholders & Access appears when explicit stakeholder access is enabled.
  • All Documents aggregates authoritative and standalone Project records.
  • Agreements and Intake Forms appear when enabled.

If an old or unavailable workflow link is opened, Yepsta falls back to All Documents rather than exposing a disabled section.

Everyone with appropriate access can use the sections relevant to the Project. These can include Financial Overview, Billing & Invoices, Retainer, Time, Expenses, Budget, Unbilled Work and Profitability.

Optional functionality follows three layers:

  1. Business availability lets the capability be used at all.
  2. Business defaults decide the starting choice for future Projects.
  3. Project configuration is the saved snapshot for this engagement.

Changing a business default does not silently add controls to existing Projects. Review and change an individual Project deliberately where its lifecycle permits it.

Dependencies are enforced. For example, an Agreement start gate requires Agreements; billable time requires time tracking; profitability needs a valid cost source; capacity planning requires resource planning; and client uploads require the Client Workspace plus explicit stakeholder access.

Preserve context when moving between modules

Section titled “Preserve context when moving between modules”

Project links to a Proposal, Estimate, Invoice, Payment, Expense or Appointment take you to that record’s authoritative workspace. Return to the Project to see the operational effect. Do not recreate the record inside Project Documents.

Last reviewed: