# User Story: Project Management | SuiteDash

*Source: https://suitedash.com/user-stories/project-management/*

> Follow a real SuiteDash Project Management journey: set up a Client Project, organize Tasks and Phases, control Client visibility, and complete or archive the work.

User Story: Project Management | SuiteDash

## **User Story: Project Management**

This is the operating reference for a SuiteDash team that needs to set up, deliver, communicate about, and retain a Client Project. It follows the actual Projects, Tasks, Phases, Templates, Generators, Dashboard, Files, and archive journey—not a generic project-management description. It is a detailed companion to the broader [Project Management & Invoicing Software feature page](https://suitedash.com/features/project-management-invoicing-software/), not a replacement for that feature page or an internal engineering story.

In SuiteDash, a **Project** is the client-facing and internal delivery container for an engagement with an end goal. **Tasks** are the individual assigned jobs that move that engagement forward. Optional **Phases** group related Tasks into meaningful delivery stages. The same Project can carry internal context, a tailored client experience, shared and private Files, delivery assignments, updates, and the rules that govern visibility and completion.

### At a glance

This feature lets youImportant boundary

Run a delivery engagement around a Project, Tasks, and optional PhasesEvery Project requires a Client.

Assign delivery responsibility to Staff or Teams and nominate a Project LeaderOnly a Super Admin, Admin, or Project Manager can be the Project Leader.

Reuse a repeatable delivery design with Task Templates and Project GeneratorsA Template generates Tasks and Phases; a Generator preconfigures and creates the Project itself.

Give a Client a deliberately limited Project Dashboard and file experienceThe Project Dashboard is a per-Project experience, not the platform-wide Client Portal Dashboard.

Automate project/task completion and phase-completion actionsCompletion synchronization is off until it is deliberately enabled.

Preserve completed work through archivingArchived Projects cannot be edited; restore them before resuming work.

### What it is — and what it is not

A Project is the primary delivery record for work connected to a Client. It can include the Project name and status, expected dates, staff-only and client-only information, internal delivery assignments, Tasks, Phases, Project Updates, Project Files, and client-facing settings. It is the record that joins a client relationship to the team’s actual work.

A Task is an assigned job in the platform. A Task may be associated with a Project, or may be created independently; a Project Task is simply a Task attached to the delivery record. Tasks can be assigned to Staff Members and Contacts, but not to Leads, Prospects, or Office Managers. A Task records who is responsible, what is expected, its status, timing, priority, optional Phase, followers, files, and—when used—dependencies or recurrence.

A Phase is a grouping of Tasks. It is useful when the team needs stages such as discovery, production, review, approval, and launch. A Phase does not replace its Tasks, and a Phase due date is a stage goalpost: it does not automatically alter the due dates of the Tasks placed in that Phase.

A Task Template is a reusable blueprint for creating Tasks and Phases in a Project. It does not itself create a Project. A Project Generator is the next level of automation: it preconfigures a Project’s information, settings, delivery structure, and optional schedule so a Project can be generated during onboarding, through No-Code Automations, or on a schedule.

The Project Dashboard is the optional client-facing, at-a-glance view for one Project. It can display a welcome message, the Client’s logo, Project Status, a Progress Arc, and time-stamped Project Updates. It is not the same thing as the wider Client Portal Dashboard; enabling one does not mean that every Project area or every Task becomes visible.

### Who uses it

PersonWhat they can doWhat they cannot do or need from someone else

Super Admin or AdminConfigure account-wide Project defaults, visibility, notifications, dashboard behavior, business sectors, and create/manage Projects.Default settings apply to newly created Projects; they do not retroactively change existing Projects.

Project ManagerCreate and manage permitted work, lead a Project, and use the all-Task/assignee views available to that role.Must be assigned or granted relevant Project access; only a Project Manager or higher can be Project Leader.

Assigned Teammate or TeamDelivers assigned Tasks, participates in the Project, and can receive template-based assignment notifications.Seeing every Task depends on the individual Project’s “see all Tasks” setting; assignment alone does not grant universal Task visibility.

FreelancerCan work on assigned Tasks and may access Project Files when that separate setting is enabled.Cannot access Private Project Files; file access must be specifically enabled for Freelancers.

Primary ClientIs the required Client on every Project and can use the enabled client-facing Project experience.Access to Dashboard, status, progress, notes, Kanban, Files, archived Projects, and update comments is governed by settings.

Secondary ClientCan be added to a Project where a client-side team needs more than one person involved.Has limited access: for example, does not see a Primary Client’s assigned Task unless added as a follower.

Task FollowerCan view a followed Task and receives its standard notifications.Is not the assignee, and the Task does not appear in their My Tasks list merely because they follow it.

### Where to find it

- **Projects > Projects** is the home for creating and managing Projects. Open a Project to use its Tasks, Phases, Files, Kanban, Settings, and other Project areas.
- **Projects > All Tasks** lets eligible roles create and manage Tasks across Projects. **Projects > My Tasks** is the personal Task area.
- **Projects > Projects > Templates** is where Task Templates are created and maintained.
- **Projects > Projects > Generators** is where Project Generators are created and maintained.
- **Projects > Settings** is where Super Admins and Admins configure account-wide Project and Task defaults, notifications, dashboard defaults, business sectors, and related controls.
- An individual Project’s **Settings** tab is where its own visibility, Files, Dashboard, Progress, automation, and client experience are configured.
- **Projects > Projects > Archive** lists archived Projects.

### Choose the right delivery building block

NeedUseWhy

One client engagement with a concrete end goalProjectIt is the delivery record that holds assignments, work, information, Files, settings, and client experience.

One unit of work that somebody must performTaskIt carries the assignee, status, timing, priority, followers, dependencies, and optional Project/Phase relationship.

A delivery stage made up of several TasksPhaseIt groups related Tasks and provides its own status and milestone dates.

The same Tasks and Phases repeatedly, inside different ProjectsTask TemplateIt generates a predefined work structure, with dynamic dates based on a chosen date.

The same configured Project repeatedly, during onboarding, an automation, or a scheduleProject GeneratorIt can create the Project and apply its configured delivery structure to the relevant Client.

An at-a-glance client update experience for one ProjectProject DashboardIt shows only the Dashboard elements you intentionally enable.

A closed or inactive Project that must be kept or later restoredArchiveIt removes the Project from active work; it is not an editable “completed” state.

### Set up the Project record

##### Start with the required Client relationship

Go to **Projects > Projects** and select **+Add Project**. Every Project requires a Client. If an internal initiative genuinely has no client relationship, SuiteDash documentation suggests using a placeholder Client rather than trying to create a Project without one.

Assign the primary Client first. Add **Secondary Clients** when a client-side team, rather than one individual, needs access. A Secondary Client is created as a normal Client; “secondary” describes their relationship to this Project rather than a different contact type. Secondary Clients can view the enabled Project Overview Dashboard, can be assigned to Tasks in a Project where they are assigned, and can follow Tasks in that Project. They do not automatically see Tasks assigned to the Primary Client. If they are added as a follower to such a Task, they can see its details but cannot edit it or change its status or priority.

##### Name, status, dates, and information fields

The **Project Name** is visible to users assigned to the Project, including Clients, so it should be recognizable outside the internal delivery team. Select an initial **Status** from the available Project statuses. Default statuses are available, and custom Project statuses can be created through Content Categories when the operating model needs its own vocabulary.

Use **Project Start Date** when an official start date is useful for reference. Use **Estimated Completion Date** for the team’s expected completion date. **Target Time** is optional and works with the Estimated Completion Date; its available selection is in 30-minute increments.

The two Project Information fields have intentionally opposite audiences:

- **Project Information (Visible only to staff)** is internal context and is not visible to the Client.
- **Project Information (Visible only to Client)** is client-facing context and is not visible to Staff.

Treat those fields as a visibility boundary rather than duplicate descriptions. Put internal delivery assumptions, handoffs, or sensitive context in the staff-only field; use the client-only field for information the Client should be able to rely on.

##### Assign the internal delivery group and Project Leader

Assign at least one **Teammate** or **Team**. A Teammate is a single Staff Member; a Team is a group of Staff Members. If the fields are left blank, the person creating the Project is assigned and becomes its Project Leader. The logged-in creator does not appear as an assignment option because that person is automatically added.

The **Project Leader** is the person responsible for Task approvals and completions in the Project. Only a Super Admin, Admin, or Project Manager can be selected. Choose this role deliberately when the person accountable for delivery differs from the Project creator.

##### Add classification and economic context when needed

Choose a **Business Sector** when the account uses a customized classification system to organize Projects. Business Sectors are defined in Project Settings and can represent the type of work—such as Payroll, Tax Returns, or Corporate Bookkeeping—rather than a status or a client.

An estimated Project value can be entered with its currency. When the value should be calculated from time spent instead, enable the time-spent calculation option. In that mode, a Task assignee is required to enter time spent before marking a Task complete. The account-level default Project currency is also the default for a new Invoice related to a Project.

### Build the work: Tasks, subtasks, and Phases

##### Deliver the work in Tasks and Phases

Eligible roles can create Tasks in more than one place:

- In **Projects > All Tasks**, a Super Admin, Admin, or Project Manager can create a Task, select its user, and choose a Project if applicable. This route can select a Client directly without selecting a Project first.
- In **Projects > My Tasks**, users can create a Task assigned to themselves and optionally attach it to a Project.
- Inside a Project’s **Tasks** area, **+Add Task** automatically associates the new Task with that Project.
- In **Calendar > My Calendar**, clicking a date can create a Task with that date as its due date.

When creating a Project Task, the **Assigned To** choices are limited to users assigned to that Project and permitted roles. Assigning a Task to a Client exposes an additional option to require Client approval. A Task title and description are visible to every user who can view that Task, so they should be written for the actual audience.

##### Define the Task record clearly

Task field or controlWhat it means in practice

Assigned ToThe responsible user. For a Project Task, the choices come from eligible users assigned to the Project.

ProjectThe optional Project relationship when the Task is created outside a Project.

Title and DescriptionThe visible name and work description for people who can see the Task.

Est Time and Time SpentExpected hours and actual hours used for the Task.

TagsComma-separated labels that can later be used to filter Task lists.

PriorityNormal by default; Low, High, and Urgent are available, plus any added Task Priorities. Priority affects tagging and filtering/sorting.

Type and StatusClassify the Task and record its current state. Some actions, including marking complete, update Status.

PhaseOptionally place the Task into a pre-existing Phase.

FollowersPeople who can view the Task and receive standard notifications without becoming the assignee.

Start Date and Due DateThe work’s beginning date and intended completion goal.

Use **Subtasks** when one Task needs a small, checkable internal checklist. From the Task view, create them as checklist entries, check them off as the work is performed, delete one when it is no longer relevant, and reorder them as needed. A Subtask is not a separate assigned Task; it is a lower-level completion list within a Task.

##### Use dependencies and recurrence only for real sequencing

Task dependency can either prevent editing or hide a Task until another Task reaches a designated status. In each case, select the other Task in the Project and the status that unlocks the behavior. This is useful for genuine predecessor relationships—such as keeping a review task unavailable until production is ready—not merely for a visual ordering preference.

A **Recurring Task** creates future occurrences according to its start and recurrence settings. The first generated Task shows the Blueprint icon, which identifies the original recurrence source. If recurrence needs to end, return to the Blueprint Task and delete the recurring details. Followers on a recurring Task are included in future Tasks.

##### Group work into Phases without confusing Phase dates for Task dates

Create a Phase within a Project’s **Phases** tab. A Phase can have a name, status, optional description, Start Date, and Due Date. Its due date is the delivery-stage goalpost; it does not change the individual due dates of the Tasks assigned to it.

After creation, the Phase Options menu supports:

- **View**: inspect its details and assigned Tasks.
- **Edit**: modify the original Phase information, including title, description, and dates.
- **Manage Tasks**: assign or unassign Tasks through the Phase’s Task grid.
- **Manage Automations**: trigger a No-Code Automation when the Phase is set to Complete.
- **Delete**: permanently remove the Phase. This cannot be undone.

Tasks can move into or out of a Phase as planning evolves. That flexibility is important: changing a stage grouping is not the same as changing Task ownership, due dates, or visibility.

##### Manage, complete, invoice, and bulk-edit Tasks responsibly

From a Task’s Options menu, the team can view, edit, complete, duplicate, manage completion automations, manage Task Files, delete, or convert the Task to an Invoice Item. Completing a Task changes its status to Completed and removes it from the normal Task list view; its status can later be changed. Deleting a Task cannot be undone.

Task Files uploaded from the Task itself are available to that Task’s assignee and appear for that user from the main Files dashboard. A Task can be added as an Invoice Item to a new or existing Invoice, or to a new or existing Accumulating Generator. After a Task has been added to an Invoice or Accumulating Generator, it cannot be added to another Invoice or Accumulating Generator.

Use bulk edit in the list views when the same operational update applies across multiple Tasks. Bulk edit can change assignee, priority, Task Type, Task Status, Phase, Due Date, and Followers. It is a powerful time-saver, but it should follow a selection check because it changes every selected record.

### Make repeatable delivery reliable: Task Templates

##### What a Task Template creates

A **Task Template** pre-creates Tasks and Phases that can be applied to a new or existing Project. When applied, it generates the predefined structure, assigns the appropriate users, and creates dynamic dates from its settings. Create and manage Templates in **Projects > Projects > Templates**.

Use a Task Template when the work itself repeats but the Project must still be created for a particular Client or situation. It is different from a Project Generator: the Template contributes the internal work structure; the Generator preconfigures the Project record that receives that structure.

##### Set relative Task dates and template assignments

Within a Template, a Task’s **Relative Due Date** is a number plus a days-or-weeks interval. It is calculated from the **Based on Date** selected when the Template is applied. For example, a Task configured for 10 days is due 10 days after that date. Negative values are permitted when a generated Task must fall before the Based on Date.

Template Tasks can be assigned to the Project Leader, Coordinator, Salesperson, Client, or an individual Staff Member. If an individual Staff Member is no longer available, SuiteDash assigns the generated Task to the Project Leader. A Template Task can also use Priority, Followers, and Subtasks. The **Prevent editing or reassigning** setting restricts the assignee to adding comments, managing Task Files, and marking the Task complete.

##### Define the stage schedule in template Phases

Template Phases use **Start/End Interval** rather than ordinary date pickers. Each interval is a number plus a days-or-weeks unit, calculated from the Based on Date. For example, an interval beginning 10 days after the Based on Date and ending 20 days after it produces that window in the generated Project. Negative Start and End Intervals are also permitted.

##### Apply a Template to a new, existing, or automation-selected Project

At new Project creation, select the Task Template and choose the Based on Date. If no alternative date is selected, generated Task and Phase dates use the Project creation date. To merge a Template into an existing Project, use that Project’s Options menu and select **Apply Task Template**.

Task Templates can also be used through an Automation. In that context, select the Template, its Based on Date, where it should apply, and the Project Status to use after the Template is applied. The automation can apply to the Contact’s most recent Project or find a Project by title. Title matching should be designed carefully: the documented lookup uses the first few letters of the first word and selects the most recent matching Project when multiple Projects begin alike. Naming conventions therefore matter when automated matching is used.

### Generate repeatable Projects: Project Generators

##### When to use a Generator instead of a Template

A **Project Generator** is for a preconfigured Project that must be generated automatically or repeatedly. It can set the generated Project’s title, initial status, expected completion timing, staff and client information, staff assignment, Task Template, Folder Generator, value settings, custom fields, client-facing Dashboard behavior, and post-generation automations. It does not need a preassigned Client in its general configuration because the generated Project is assigned to the correct Client when the Generator is triggered.

Use it for repeatable service packages, onboarding delivery, renewal work, scheduled client obligations, or any scenario where the Project record—not only its task list—has a repeatable shape.

##### Configure the Project that will be generated

Create one at **Projects > Projects > Generators**. The Generator’s own name is for internal reference and is not necessarily the title of the Project it produces. **Project Name** is the actual generated Project title; placeholders can make generated names descriptive and distinct for the Client.

Select an initial Project Status, which is required. Choose the Project completion Based on Date either from Generation Day with a positive shift or from a date-type Custom Field. A Target Time can be set for that date. Configure the staff-only and client-only Project Information with the same care as a manually created Project.

Assign Teammates, Team(s), and a Project Leader. The Project Leader defaults to the Project author. The Generator can also add the target’s Coordinator and Salesperson. In Task/Phase settings, select a Task Template and the Based on Date that will drive the generated Tasks and Phases. If relevant, apply a Folder Generator to the Project Files.

Project automations are not configured while initially creating a Generator. Save it first, then return to configure automations that run when a Project is generated and pre-create automations that run when the status of a Generator-created Project is set to Complete. The Generator can also carry Project Custom Fields.

##### Choose a schedule only when the Generator itself should create Projects on time

Scheduled/recurring generation requires at least one Client or Circle because the Generator must know who receives a Project on the scheduled date. Without scheduling, the Generator is normally applied in a context that supplies the Client.

Schedule optionUse it whenRequired operating detail

Recurring OptionsThe Project should generate at a regular number of days, weeks, months, or years.Set a start date and whether it continues indefinitely, ends on a date, or ends after a number of occurrences.

On Specific DatesA known set of dates does not follow a regular pattern.Add as many individual dates as needed.

Custom FieldDifferent assigned Contacts need different generation dates.Select a date-type Custom Field so each Contact’s date drives their Project.

For a recurring Generator applied through automation, the documented pattern is to assign the scheduling Circle to the Generator and ensure the Circle is added to the Contact or Company before or when the Generator is applied.

##### Apply a Project Generator in the right place

Project Generators can be applied when creating a new Client contact, from an existing Contact’s Options menu, through a Kickoff Form for the Client role, and through No-Code Automations. On a new Client contact, the Generator area appears when the selected role is Client. On an existing Contact, use **Apply Project Generator**. In a Kickoff Form, select the Generator when configuring the Client role. Use a No-Code Automation when the Project should follow another product event rather than a manual user action.

After creation, a Generator can be viewed, edited, duplicated, given a Folder Generator, or deleted. Deleting it removes the Generator and cannot be undone; it does not mean a previously generated Project is deleted.

### Deliberately design the Client experience

##### Separate account defaults from individual Project settings

**Projects > Settings** contains default settings. These defaults apply to new Projects and do not automatically update existing ones. An individual Project’s **Settings** tab controls that Project directly. Use this distinction deliberately: set a sensible future default, then verify high-value or exceptional Projects one by one.

Account-wide Project visibility settings can allow all Admins and/or Project Managers to access all Projects, give Clients an Archived Projects tab, control progress visibility, allow assigned Project users to see all Tasks, permit Client access to Public Project Notes, and permit Clients to create Notes when they can already view them. Individual Project settings can adjust these choices for the Project at hand.

##### Configure the Project Dashboard as a purposeful client surface

Enable the Project Dashboard in **Projects > Settings > Project Dashboard Settings** for new Projects, then configure each existing Project in its Settings tab. On an individual Project, enabling the Dashboard allows assigned Client(s) to view the Dashboard page. The Dashboard can also become the Start Page for selected assigned Clients—both primary and secondary—so they arrive on that Project Dashboard after sign-in.

The Dashboard can include a Client logo, a welcome message with an optional additional paragraph, Project Status, a Progress Arc, and Project Updates. Project Updates form a time-stamped log. The Client can be notified by email when an update is posted, and can be allowed to comment when that is appropriate. Update History provides a quick view of the updates, and the Progress Arc can reflect the progress associated with the selected update.

Client-facing elementDecision to makeWhat the setting does not imply

Welcome Message and Client LogoIs this Project a polished client progress space?It does not expose Tasks, Files, or internal information by itself.

Project StatusDoes the Client need the current status label?It does not give the Client permission to change the status.

Progress ArcShould progress derive from complete Tasks, Project Phases, or a manual value?It does not require that every underlying Task be visible.

Project UpdatesDoes the Client need a date-stamped communication history, email notices, and/or comments?It does not make every Project Note public.

Start PageShould selected assigned Clients land here after sign-in?It only applies to the selected assigned Clients.

##### Make Files visibility explicit

Every Project includes a Files tab. Internal users with the relevant access see **Private Files**, **Public Files**, and **Tasks** folders. Private Project Files are visible to assigned internal Staff, excluding Freelancers; they are not visible to Clients, Secondary Clients, or Freelancers, and those people are not shown that the private folder exists.

Public Project Files are the shared repository. Assigned team members, the Client, Secondary Clients, and assigned Freelancers can upload, download, and view the files there, subject to the Project’s access setting. The Task Files area contains a folder for each Project Task. A Task folder is visible only to people who can see that Task: Admins and Project Managers can see all Task folders, while Teammates, Freelancers, Clients, and Secondary Clients see only folders for Tasks they are assigned to or otherwise allowed to view.

The individual Project setting separately controls what Clients can do with Project Files and whether assigned Freelancers can access them. Do not use a client-facing Dashboard as a proxy for file permissions; verify both settings.

##### Control Task and Kanban visibility without assuming universal access

The individual setting **Allow assigned Project users to see all Tasks** determines whether assigned Staff Members can see Tasks that are not assigned to them. At the global level, completed Tasks are hidden by default throughout the platform; settings can allow viewing them. If Clients will not receive Tasks, the account can disable their My Tasks menu item and their Project Tasks tab, and can prevent Clients from creating their own independent Tasks.

Clients have Kanban access by default unless it is disabled. Kanban presents Tasks as cards and has Status View and Assignee View. Status View organizes cards by Task Status; dragging a card changes its status. Assignee View organizes cards by assigned Staff/Contact and is limited to Super Admins, Admins, and Project Managers; moving a card changes its assignee. Clients and Prospects cannot move cards or columns. Freelancers can move cards but cannot reorder columns. Drag-and-drop does not work on mobile devices.

### Completion, notifications, and the active-to-archive lifecycle

##### Use completion synchronization only when it matches reality

At Project level, two related controls can be enabled: automatically mark the Project status complete when all its Tasks are complete, and automatically mark all Tasks complete when the Project is manually marked complete. Neither behavior is on by default. Turn on only the direction that expresses the account’s real completion rule; otherwise, Project and Task statuses remain independently managed.

Phase completion can trigger a No-Code Automation through the Phase’s Manage Automations option. Individual Tasks can also have Automations that run on completion. Project Settings can allow Teammates and/or Freelancers to see Task Automations, but this exposes the available Automation list and may reveal information outside their usual role permissions. Apply that access intentionally.

##### Decide how people hear about the work

Project and Task notification settings can be individually customized by users. Digest Emails summarize events that have already happened, while Outlook Emails summarize upcoming Project and Task due dates; each may be set daily or weekly. Account-level changes normally apply to new users rather than retroactively changing existing users, unless the account uses **Override existing settings** for the selected role.

When a Task Template gives the same person two or more Tasks, Project Assignment Digest can send one linked briefing instead of one email per Task plus a separate Project-assignment notice. A one-Task assignment remains an individual email. This is distinct from scheduled Digest Emails: real-time in-app notifications are still delivered per Task.

##### Archive when work is no longer active; restore before resuming it

An Archived Project is no longer active—typically because it is completed or no longer valid. Open **Projects > Projects > Archive** to find archived records. An Archived Project cannot be edited, and users assigned to its Tasks cannot view those Tasks. The Archive Options menu lets the team view a high-level overview, delete the Project permanently, or restore it. The archived overview does not expose its Tasks, Phases, and similar active-work details.

Restore makes the Project active again and restores its settings and assigned Tasks. Client visibility remains a separate choice: an individual Project can allow the Client to see the Project after it is archived, while disabling that option means the Client loses access when it is archived. Archiving is therefore suitable for retaining a record without leaving active collaboration open; deletion is permanent and should not be confused with archiving.

### Operating patterns that hold up in real use

##### Run a one-off client delivery engagement

Create the Project with the right primary Client, add Secondary Clients only where they should participate, assign the delivery team and qualified Project Leader, then capture staff-only and client-only context in their separate fields. Create the Tasks within the Project, group them into Phases only where the stage view helps, set Task ownership and due dates, and decide whether the Project Dashboard needs to be a polished client home or whether the Client needs only selected Files and Tasks.

Before inviting the Client into the work, verify the individual Project settings: all-Task visibility, status/progress visibility, Kanban, Files, notes, archived access, Dashboard, and update comments. Those choices are independent and should not be inferred from one another.

##### Standardize a repeatable service without over-automating it

Build a Task Template when every engagement uses the same work stages and relative dates but requires an ordinary new Project for the specific Client. Add relative dates, template assignments, priorities, Followers, and subtasks. Apply it at Project creation, with an intentional Based on Date, or merge it into a current Project where the template’s work genuinely belongs.

Build a Project Generator when the Project itself has a repeatable configuration: client-facing messages, Project information, assignment model, template, folder structure, custom fields, and completion behavior. Apply it at contact onboarding, through a Kickoff Form, or a No-Code Automation. Add scheduling only when the Generator must itself create Projects on a calendar.

##### Give a client a focused delivery home without exposing internal work

Enable the Project Dashboard for the individual Project; add the Client logo, welcome message, status, a progress method, and Project Updates. Set it as the Start Page only for the specific assigned Clients who should arrive there after sign-in. Keep internal information in the staff-only Project field, keep staff-only documents in Private Files, and use the individual client Files permissions instead of assuming Dashboard access includes file access.

##### Close an engagement while retaining a clean record

Complete the relevant Tasks and Project according to the selected completion policy. Archive the Project after the active work has ended. If the Client needs a reference record, explicitly allow access to the archived Project; if they should no longer open it, leave that access disabled. Restore rather than recreate when the engagement resumes, because restore brings back the Project’s settings and assigned Tasks.

### Expectations and guardrails

- Every Project requires a Client. Use a placeholder Client if an internal Project must be represented in this framework.
- Project name, Task title, and Task description are visible to the people who can see their record. The two Project Information fields are deliberately audience-specific.
- A Project Leader must be a Super Admin, Admin, or Project Manager.
- A Task can be independent of a Project, but a Project Task’s available assignees are constrained by the Project’s assignment and role rules.
- A Phase due date is a stage goalpost, not a mechanism for changing Task due dates.
- Deleting a Phase, Task, archived Project, or Project Generator cannot be undone.
- Archived Projects cannot be edited; restore one before resuming active work.
- Account-level Project defaults apply to new Projects, not existing Projects. Individual Project Settings are the authoritative place for an exceptional or existing Project.
- Dashboard visibility, Task visibility, Project Files, Private Files, Kanban, Notes, Status, Progress, archived access, and update comments are separate controls. Do not make one setting stand in for another.
- Secondary Clients do not automatically see Tasks assigned to the Primary Client.
- Automated Template matching by title uses the start of the Project title and can choose the most recent match; avoid indistinguishable Project names when relying on it.

### Frequently asked questions

##### Can a Client land directly on a Project Dashboard after sign-in?

Yes. Enable the individual Project Dashboard and select the assigned primary and/or secondary Client(s) who should use it as their Start Page. Those selected Clients are directed to that Project Dashboard when they sign in.

##### Can I show progress without exposing every Task?

Yes. The Project Dashboard can show a Progress Arc calculated from complete Tasks, Project Phases, or a manual value while Task visibility remains independently controlled. The Project’s settings determine whether assigned Project users can see all Tasks.

##### Can a Phase’s due date change the dates of the Tasks in it?

No. A Phase due date is a milestone for the Phase. It does not change the due dates of the individual Tasks assigned to that Phase.

##### What is the difference between a Task Template and a Project Generator?

A Task Template generates predefined Tasks and Phases in a new or existing Project. A Project Generator preconfigures the Project itself and can include a Task Template, then creates that Project through onboarding, an automation, or scheduling.

##### Can more than one person on the client side participate?

Yes. Add each client-side person as a Client and assign the additional people as Secondary Clients. Their access remains intentionally limited, especially around Tasks assigned to the Primary Client.

##### What happens when I archive a Project?

It becomes inactive, cannot be edited, and its assigned Task users cannot view the Tasks. It can be viewed at a high level, restored with its settings and assigned Tasks, or permanently deleted. Client access to an archived Project depends on that Project’s archived-access setting.

### Related resources and next steps

[SuiteDash Help CenterCreate a ProjectRead &rarr;](https://help.suitedash.com/article/34-creating-a-new-project)

[SuiteDash Help CenterManage TasksRead &rarr;](https://help.suitedash.com/article/86-managing-tasks)

[SuiteDash Help CenterOrganize work with Project PhasesRead &rarr;](https://help.suitedash.com/article/72-projects-phases-overview)

[SuiteDash Help CenterBuild Task TemplatesRead &rarr;](https://help.suitedash.com/article/68-task-templates)

[SuiteDash Help CenterCreate Project GeneratorsRead &rarr;](https://help.suitedash.com/article/250-projects-project-generators)

[SuiteDash Help CenterConfigure the Project DashboardRead &rarr;](https://help.suitedash.com/article/120-project-dashboard)

[SuiteDash Help CenterManage Project SettingsRead &rarr;](https://help.suitedash.com/article/78-project-settings)

[Public Feature PageProject Management & Invoicing SoftwareRead &rarr;](https://suitedash.com/features/project-management-invoicing-software/)

Bring client work into one workspace

Connect client work across CRM, onboarding, portal access, proposals and billing. Choose the workflows you configure and the plan or optional Power-Ups you need. Every plan includes unlimited Clients and Staff.

Automated CRM

Onboarding

Client Portal

EXTREME White Label

Digital Marketing

Appointment Scheduling

Digital Dynamic Proposals

Billing + Packages

Contracts & eSignature

Project & Task Management

Payments + Subscriptions

File Exchange

Learning Management (LMS)

Support Tickets

Interactive Community

Secure Messaging
