> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/reference/user-interfaces/portal/project-suite/projects.md).

# Projects

The central element of the We360.ai Project Suite is the **Projects** dashboard itself, providing a top-down view of all ongoing work and linking time-tracking directly to deliverables.

<figure><img src="/files/YZAjOceFFOk3f0nPBitG" alt="Projects dashboard showing project list and task management views"><figcaption><p>Projects dashboard with project listing and task management</p></figcaption></figure>

{% hint style="info" %}
This page describes the Project Suite screens and where controls live. For what projects, tasks, statuses, and billing *are* and how they behave, see the [Projects & Tasks reference](https://docs.we360.ai/reference/work-and-time-management/product/work-and-time-management/projects-and-tasks). For step-by-step goals, see [Managing Projects & Time](https://docs.we360.ai/how-to-and-best-practices/managing-projects-and-time).
{% endhint %}

## Dashboard

The project **Dashboard** is the operational landing screen. It combines organization-level project visibility with the signed-in user's own tasks, standups, and timesheet reminders in one place.

<figure><img src="/files/B7TP2GkBToX5MjW80RTm" alt="Project management dashboard"><figcaption><p>The project management dashboard</p></figcaption></figure>

**KPI summary cards** give a quick read on the user's own workload: total and active projects, active tasks, tasks due today, and hours logged.

<figure><img src="/files/ZvRxQPUhIYywFErWYWnQ" alt="Personal KPI summary cards"><figcaption><p>Personal KPI summary cards</p></figcaption></figure>

The **Project Overview** area summarizes the active projects the user can access, with visual indicators for scanning several projects at once.

<figure><img src="/files/RwaCTZqdULbWOLa1IyFO" alt="Project overview across active projects"><figcaption><p>Project overview across active projects</p></figcaption></figure>

## Project Management

At a high level, administrators or project managers define the overarching "Projects."

* **Configuration**: Managers can create new projects, assign a default active status, and dictate which teams or specific individuals are allowed to log time against the project.
* **Custom Fields**: We360.ai supports up to 8 strongly typed "Custom Fields" per project (for example, string, integer, or boolean formats). This lets organizations append specific metadata, such as internal billing codes, priority tags, or external client IDs directly to the project for reporting.
* **Access Control**: Depending on the Role settings, lower-level employees see only the projects explicitly assigned to them, while Tenant Owners maintain a global view.
* **Project Status Filter**: Projects can be filtered by status—**Active** or **Archived**—so managers can keep the dashboard focused on current work while retaining historical project data for reference.

## Project Detail View

<figure><img src="/files/lzhaSQicx0DeLFglLKBM" alt="Project detail view with task list"><figcaption><p>A project's detail view and task list</p></figcaption></figure>

Clicking into an individual project opens its detail view, which surfaces the full list of tasks assigned to that project along with cumulative time logged. The task table displays the following columns:

| Column                    | Description                                                           |
| ------------------------- | --------------------------------------------------------------------- |
| **Summary**               | Title of the task (clickable to open details).                        |
| **Status**                | Current progress indicator (for example, TODO, IN PROGRESS, or DONE). |
| **Assignee**              | User responsible for completing the task.                             |
| **Estimate**              | Time estimate to complete the task.                                   |
| **Start Date / Due Date** | Task scheduling details.                                              |
| **Reporter**              | User who created or reported the task.                                |

The table footer displays the total number of tasks within the project, with pagination options for viewing tasks in batches. Search bars allow filtering tasks by summary/keywords or by assigned users. From this view managers can add new tasks, reassign members, and review progress against estimates without leaving the project context.

## Task Management

If a "Project" is the bucket, "Tasks" are the individual drops of work. Large projects are broken down into assignable sub-tasks that act as individual line-items for time tracking.

* **Task Types**: Tasks can be further categorized structurally as an `EPIC` (a large body of work), a standard `TASK`, or a `BUG` (defect resolution).
* **Dual View Modes**: The Task interface can be toggled via a primary switch between two modes:
  * **List Data Table**: A dense, sortable table displaying all tasks, their assignees, due dates, and statuses.
  * **Kanban Board**: A visual drag-and-drop board (for example, To Do → In Progress → Review → Done), so Agile-focused teams can move cards through a workflow pipeline visually.
* **Quick Creation**: The List view features an inline "Quick Add" input field, so managers can add new tasks without opening a separate form for every entry.
* **Add Task Panel**: Creating a new task opens a side panel with structured fields: **Type** (Epic, Task, or Bug), **Summary** (task title, mandatory), **Description** (detailed explanation), **Assignee** (responsible user), and **Start Date / Due Date** (scheduling). Click the Add Task button to save and add the task to the project list.
* **Task Details Drawer**: Clicking any task opens a comprehensive side-drawer detailing the description, assignee history, and a timeline of exactly how many hours have been logged against that specific sub-task. The detail view includes:
  * **Attachments**: Option to upload related files to the task.
  * **Child Issues**: Ability to link or create subtasks within a parent task.
  * **Detail Panel (Sidebar)**: Shows Assignee and Reporter info, time tracking details (Estimate and Time Logged), Start and Due Dates, and Created/Updated timestamps.
  * **Comments**: Collaborate through task-specific discussions.
  * **Status Changes**: Switch between statuses (TODO, IN PROGRESS, or DONE) directly from the detail view.

## My Tasks

**My Tasks** is a personal workspace where users manage their own assigned work: viewing tasks, updating statuses, logging effort, and tracking deadlines across projects.

<figure><img src="/files/tR6Z0ZC6aj8nTCrI3k7B" alt="My Tasks workspace"><figcaption><p>The My Tasks workspace</p></figcaption></figure>

Filters narrow the list by status, priority, due date, project, sprint, or tags.

<figure><img src="/files/K4KAlOpeHsv3307RiR9e" alt="Filtering the My Tasks list"><figcaption><p>Filtering the My Tasks list</p></figcaption></figure>

## All Tasks

**All Tasks** widens the view to work across every project the user can access, for monitoring progress, reviewing assignments, and analyzing workload. The same filters apply, with assignee and reviewer added.

<figure><img src="/files/9mOSPbHt7lFBS2yn6FFR" alt="Tasks across all accessible projects"><figcaption><p>Tasks across all accessible projects</p></figcaption></figure>

## Calendar View

Alongside the List and Kanban views, a **Calendar View** places tasks on a timeline for date-based planning. Managers can schedule tasks, adjust timelines, and review upcoming deadlines, and filter the calendar by sprint, status, or assignee. Unscheduled tasks stay visible until a date is added.

## Sprints

Tasks can be grouped into **sprints**—time-boxed cycles with a start and end date. The sprint controls let managers create a sprint, add tasks to it, start it, and complete it; when a sprint is completed, unfinished tasks can carry over to the next one. Task views can be filtered to a single sprint to keep the board focused on the current cycle. For running a sprint end to end, see [Plan and run a sprint](https://docs.we360.ai/how-to-and-best-practices/managing-projects-and-time/plan-and-run-a-sprint).

## Daily Standups

The **Standup** screen gives teams a single place to run a daily check-in without opening each board. From it, the team can review progress across members, add work logs, create or update tasks, change assignees, and add comments. A standup summary can be saved, downloaded as an image or PDF, and shared as a meeting record.

<figure><img src="/files/Fm8gHR6snzOhvgTZPylU" alt="The daily standup screen"><figcaption><p>Running a daily standup from one screen</p></figcaption></figure>

## Access & Roles

Project access is controlled by membership and role. Projects define **Project Owners** and **Project Members**, and **Guests** have view-only access. Permissions can be set at both the organization and project levels.

<figure><img src="/files/XVVU3CffSTkA5mjUnHfq" alt="Managing project members"><figcaption><p>Managing project members</p></figcaption></figure>

<figure><img src="/files/2vYoWTfXrj2d857k9FUM" alt="Role-based access within a project"><figcaption><p>Role-based access within a project</p></figcaption></figure>

## Workflow Automation

The **Workflow** screen lets organizations automate routine project actions such as sprint creation, sprint completion, task movement, and status transitions, keeping process consistent across teams.

<figure><img src="/files/JOz2rR5E8R6WzozpSwGa" alt="Automating project workflows"><figcaption><p>Automating project workflows</p></figcaption></figure>

## Archived Projects

Inactive projects can be archived to hide them from operational views while keeping their tasks and history. A project can also be marked **To Be Deleted** for permanent removal.

<figure><img src="/files/WI4W9atD1hh0y5hHaM32" alt="Archived projects remain available for reference"><figcaption><p>Archived projects remain available for reference</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.we360.ai/reference/user-interfaces/portal/project-suite/projects.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.