Work in Project Workspace

Project Workspace is the working surface for an active project. The left side shows progress and the project calendar; the main area shows the tasks for the selected planning period; the top actions open Project chat, Team chat and Project Analytics without losing the current task context.

The workspace follows the project's operating model. Sprint controls appear for sprint-based delivery, hours appear only when time tracking is enabled, and financial actions remain hidden when the project does not use billing or invoices.

1. 1
   Choose a planning period

   Select a week or configured delivery period in Calendar. The task list updates to that period without changing the project's total duration.

2. 2
   Switch between Date and Status

   Date keeps work in delivery order. Status groups work by its current state and unlocks the status filter.

3. 3
   Filter by tags

   Use one or several project tags. Match all narrows the result to tasks containing every selected tag.

4. 4
   Use All only when necessary

   All shows tasks across planning periods. Return to the active period for focused daily work.

5. 5
   Read the completion counter

   The Done/Total indicator summarizes the currently visible scope, not unrelated tasks outside the filter.

1. 1
   Add a task

   Choose Add task, give it a concrete outcome and place it in the correct delivery period.

2. 2
   Add useful detail

   Write the description as completion evidence. Checklist lines are useful when one outcome has several verifiable parts.

3. 3
   Assign the project team

   Choose one or more specialists from the active project team. When time tracking is enabled, distribute the planned hours between them.

4. 4
   Add dates, status and tags

   Dates place the task on Calendar; status drives delivery reporting; tags make cross-sprint filtering possible.

5. 5
   Link the source plan

   If the task came from Project Architect, keep its Architect link so the delivery task remains connected to the original plan item.

6. 6
   Save, then update the state

   Keep the task current as work moves from Pending to In progress, Done and, when the client owns acceptance, Accepted.

Opening a task shows one ordered record rather than separate disconnected popovers. The header owns title, dates and status; the scrollable detail area contains the description or checklist, Work products, Work context, Work Graph and Team Pulse when those sections have relevant evidence.

On mobile, Task Details uses a full-height sheet with a fixed header and action area. The detail area is the only scrolling region, so opening a long attachment list or Work context does not move the status and task actions off-screen. The sheet follows the active light or dark theme as one surface.

Work products combines files uploaded by project participants with deliverables created by a connected project agent. Every item stays attached to its real project and task, so another participant can inspect the source, file name, summary, version and review state without searching a chat transcript.

An agent conversation does not become delivery evidence merely because the agent wrote an answer. The result appears here only after the authorized agent action saves a task artifact. Agent-generated results can then be previewed, downloaded, approved or returned with a precise revision request.

The assignee picker reads the active project roster, not every person in every attached source team. A newly added specialist becomes assignable only after the responsible specialist, partner or client has confirmed the participation request.

The same boundary is enforced by the task API. A pending or declined person cannot be attached to a task by sending a request outside the interface.

• Use Project details to review the current member status and decision owner.
• Resolve Review member before planning work for that person.
• When time tracking is enabled, use only the accepted HOURS allocation as capacity context.
• Adding a person or increasing allocation does not create an invoice without delivered task evidence.

Work Graph explains how tasks affect one another. Open a task, choose a relationship type, then search the project task list. The relationship is visible from both ends so a blocker is not hidden inside one person's task.

• Task status says what happened to the deliverable; Team Pulse says how collaboration around the task feels.
• Use Project chat for decisions and communication tied to this project.
• Use Team chat for the wider team conversation when that channel is available to your role.
• Task comments keep a discussion attached to the relevant work item instead of burying it in a general thread.
• Private messages and scheduled meetings are available from the communication layer when a conversation should move to a smaller group.

1. 1
   Open the current delivery period

   Scan Progress, Calendar and the visible task count before changing anything.

2. 2
   Review blocked and active work

   Filter by Status and inspect Work Graph links before assigning more work.

3. 3
   Update only changed tasks

   Keep assignees, status, dates and checklist evidence current.

4. 4
   Record collaboration signals

   Use Team Pulse when there is meaningful evidence, not as a decorative daily vote.

5. 5
   Open Analytics for patterns

   Use task details for one item and Project Analytics for workload, schedule and cross-sprint patterns.