How to Save a Project View

A saved project view is a way to reopen the same picture of the tasks without rebuilding it. Dayzen has two different saves, and mixing them up is how a team thinks a filter was shared when it was only on one person's screen.

A view template is stored on the project. Someone who can manage views names the current layout and other people on that project can apply it. A view preference is stored for one user. It remembers which tab you had open, which tabs you show, and your filters. Applying a template does not rewrite everyone else's personal preference unless they apply it themselves.

The pictures you might save are the ones the project already has: list, board, calendar, Gantt, table, timeline, and workload. Kanban versus Gantt is the choice between board and schedule. Calendar versus timeline is the choice between due dates and a person's row. Saving a view does not create a new kind of chart.

What goes into a template

A template has a name and a configuration. The configuration is the layout you were looking at: which view, and the filters or arrangement that went with it. One project can hold several templates. One of them can be marked active, which is the layout the project offers as the current shared starting point. It is not a lock. A person can still switch tabs.

Name the template after the question it answers.

• "This week's board" for status columns with a short date filter.
• "Client dates" for the calendar, if the shared audience is people who only need due days.
• "Schedule" for the Gantt, when the useful picture is Blocks and dates.

Avoid names like "My view" or "Final." A template is for the project, so the name should still make sense when someone else reads it next month.

What stays personal

Your preference remembers the view you returned to, on that project or on a task list that is yours. If you hide a tab because you never open the timeline, that hide is yours. It does not remove the timeline for a colleague. If you filter to your own tasks, that filter should stay on your preference, not become a template called "the project," or everyone else will open the project and see only you.

This split is the whole feature. Shared means the team can reopen a named layout. Personal means the product remembers your last arrangement. Neither one emails a report, and neither one is a dashboard.

List and table, as one example

List and table are two of those views, not two products. The list is a readable queue. The table is the same tasks with more columns in view, which helps when you are checking owners, priorities, and dates together. You do not need an article to choose between them. Save a table template if the planning meeting uses columns. Leave the list as a tab people open when they are doing the work. Both read the same tasks.

When to save, and when not to

Save a template when two or more people ask for the same arrangement every week. The signal is repetition: "Can you put it back on the calendar, filtered to the launch section?"

Do not save a template for a one-time slice. A filter you used once to find a missing task is a preference at most. A pile of unused templates is worse than no templates, because nobody knows which name is current.

Do not save a template to hide tasks from a client. Hiding is access, not a filter. A guest who should not see internal work needs a share on the right project or section, not a view that happens to filter them out on your screen. Filters are easy to clear.

A short setup

1. Open the project and arrange the view you want the group to reuse. Include only filters you would defend out loud.
2. Save it as a template with a plain name.
3. Ask one other person to apply that template and say what they see.
4. If they see your private tasks only, you saved a personal filter. Clear it and save again.
5. Leave each person's tab order alone. That is their preference.

If the other person cannot apply it, they may lack access to the project, or the permission to manage templates. Fix access. Do not paste a screenshot into chat and call that the saved view.

What a saved view will not freeze

Dates, statuses, and assignees stay live. A template does not snapshot the tasks as they were on Monday. When someone opens "Schedule" on Thursday, the bars are Thursday's dates. There is no baseline inside the view. If you needed last Monday's bars, that is a comment or a note, not a second template.

Workload saved as a view is still a count of tasks due per person this month. Saving it does not turn it into hours or a fee forecast. The timeline saved as a view is still the per-person swimlane, not a duration bar.

A planning meeting that uses one template

The Monday meeting opens the template named "Schedule." Everyone who applies it sees the Gantt with the launch section included and the archived section excluded. That is worth a template because the meeting repeats and the filter is the same. People who do not attend leave their own preference on the board. They are not wrong. Their job that afternoon is status, not the schedule.

Halfway through, someone filters to a single assignee to answer a question. That filter is not saved back onto the template. If they click update without looking, Tuesday's meeting opens on one person and the group thinks the data vanished. The habit is: apply the template at the start, poke around, and do not write those pokes back unless the group agreed the layout changed.

After the meeting, one person still cannot see the template. They are not a member of the project. No saved view fixes that. Membership first, template second.

Table versus list can be a second template later, if the meeting starts wanting columns of priority and due date instead of bars. Until someone asks twice, do not save both. One shared layout is easier to trust than a menu of near-duplicates.

Conclusion

Save a project view as a named template when the team should reopen the same layout. Keep tab choice and private filters in the personal preference. Use list, board, calendar, Gantt, table, timeline, or workload as the picture, and do not expect the save to lock the data or hide tasks from someone who has access. The views live in /pms.

One mistake to avoid

Do not save a template from a filtered personal queue and then tell the team "the project is saved." Apply it with a second account or a second person the same day. What they see is the template. What you see after clicking around is your preference. If those two screens differ, say so in the meeting before anyone plans from the wrong one.

Also resist a template per person. "Alex's board" and "Sam's board" are preferences. A template named after a person becomes wrong the week they change teams, and other people apply it by habit.