Dayzen HRMS + Project Management System — people ops and delivery in one product family.
See all modulesPractical articles on HRMS, attendance, leave, payroll, hiring, and HR operations.
124 articles
Project management
A custom project role is a named set of permissions on a workspace, assigned to a member. It answers "what may this person do here?" The map of access layers, organization versus workspace versus a share, is how project access works. This page is the narrower job: create one role and apply it. The example is a reviewer who can comment and must not edit tasks.
Dayzen
Project management
A channel is a room with a scope. The scope decides who is in it. Dayzen has four scopes: the workspace, one project, one section, or a custom list of members. Pick the smallest room that still includes everyone who must hear the conversation. A custom list is how you make a private channel. It is not a direct message feature with an inbox of its own.
Dayzen
Project management
Project chat and task comments are both places to write. They are not interchangeable. A channel is the conversation for a project, a section, or a chosen group. A comment is a note on one task, including a reply in that task's thread. Put the decision where the next person will look for it. If they will look at the task, comment. If they will look at the room, use the channel.
Dayzen
Project management
Kanban and sprints are two ways to use the same board. Kanban, in the practical sense, means the cards keep moving through statuses with no dated container. A sprint, in Dayzen, means you turned cycles on and the work you are doing now sits in a cycle with a start and an end. The board does not go away when you add a cycle. The cycle does not appear just because you use columns.
Dayzen
Project management
Moving project work out of a spreadsheet means deciding what each row becomes, then creating those tasks in one project. It does not mean uploading the file. Dayzen has no spreadsheet importer. If you plan the move as a file format, you will stall on columns the product will not map. Create the tasks that are still true, and leave the rest in the sheet.
Dayzen
Project management
Setup has an order. Create the workspace, put the right people in it, create a project, add a few sections, and set a short status list. Then add real tasks. Permissions, guest shares, and a second workspace are later decisions. Doing them on an empty project produces a structure nobody has tested.
Dayzen
Project management
A task can carry three planning fields, and each one answers a different question. The start date is when the work may begin. The due date is when it should be finished. The time estimate is how many minutes you think it will take. None of them is a milestone, and the estimate is not time you have already logged.
Dayzen
Project management
A section is a named area inside one project. Discovery, build, and review can be sections. Design, copy, and launch can be sections. The section answers "which part of the project is this task in?" It does not answer "what status is it?" and it is not a milestone.
Dayzen
Project management
A kanban board is enough while the only question is which status a card is in. It stops being enough when the work has an order, a boundary, or a load that the columns cannot show. Those are specific failures. They are not a reason to collect a list of board replacements, and they are not a reason to abandon the board. The board can stay. Other views and access rules answer the questions the columns cannot.
Dayzen
Project management
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.
Dayzen
Project management
Calendar and timeline are both date views. They are not the same picture, and neither of them is a Gantt chart. The calendar answers "which tasks are due on this day?" The timeline answers "which tasks sit with this person this month?" If you open one expecting the other, the screen looks empty or pointless.
Dayzen
Project management
A Gantt chart is a schedule of tasks. Each task that has dates occupies a span. A blocking link says one task should hold another. You use the chart to see order and overlap, not to decorate a status meeting. If you only need to know what is in progress this week, a board is the better picture. The comparison is Kanban vs Gantt charts. This page is how to plan on the chart once you have chosen it.
Dayzen
Project management
Tags and custom fields both look like extra labels on a task. They answer different questions. A tag says "this task belongs with these other tasks." A custom field says "this task has this value." If you use a tag as a value, or a field as a loose sticker, the task becomes hard to filter and easy to misread.
Dayzen
Project management
A task can be broken down in two ways. A subtask is another task, with its own status, sitting under a parent. A checklist is a list of lines on the parent task. Each line can be ticked, and a line can name a person, but the line is not a task. Picking the wrong one makes the board noisy or hides work that needed an owner and a date.
Dayzen
Project management
Priority and due date answer different questions. Priority asks how much this task matters relative to other tasks. The due date asks when it has to be finished. Teams collapse them into one word, "urgent," and then cannot tell a task that is important next month from a task that is due tomorrow and barely matters.
Dayzen
Project management
A task status is the shared answer to "where is this?" If the list is long, people invent private meanings and the board lies. If the list is short and each name maps to a group everyone understands, the board is readable. Setting statuses is that mapping. It is not a workflow engine, and it is not a copy of your hiring pipeline.
Dayzen
Project management
A small team can share one board and still know what everyone is doing. A growing team hits a different problem: the board is full of work that most people should not see, and the work they do need is buried under other groups. Project management software for growing teams is not a larger checklist than the small-team one. It is a question about separation.
Dayzen
Project management
HR software and project software answer different questions. HR asks who works here, how they attend, and what they are paid. A project asks what the team is delivering, who owns each task, and what is blocked. The buying question is not "which product has more modules." It is whether the same people should open both through one login, in one organization.
Dayzen
Project management
A spreadsheet is a good place for numbers. A chat thread is a good place for a quick question. Projects break when the spreadsheet becomes the plan and the chat thread becomes the status. The break is specific. You do not need a new tool the first week a sheet exists. You need one when the sheet and the thread disagree, and nobody can say which is current.
Dayzen
Project management
A task list answers one question: what do I still have to do? A project answers a different question: what is this piece of work, who is on it, and what is blocking it? The two phrases get used as if they were the same product. They are not. The useful split is the unit of work, not the brand name on the box.
Dayzen
Project management
Agency project management fails in a predictable way. The work for Client A and Client B sits on one board, a client is invited “to make updates easier,” and the hours live in a sheet the producers do not open. The fix is delivery structure: one project per client engagement, access that stops at that work, and time recorded on the tasks. It is not a ranking of agency platforms, and it is not an invoicing guide.
Dayzen
Project management
System, software, and tool show up in the same search results, often on the same vendor homepage. Work management is a fourth label. They are not four products. They are four ways of talking about where a team keeps projects and tasks.
Dayzen
Project management
Attendance answers whether someone was working. Project time tracking answers which task the hours went to. A punch at 9:00 does not mean those hours belong to the homepage rewrite. A timer on the homepage does not prove the person was in the office, on shift, or not on leave.
Dayzen
Project management
Project access is three decisions stacked together: what someone may do in the organization, what they may do inside a workspace, and whether a single project, section, or task was shared with them. Mix those up and you will either lock out the people who run the work or show a client the wrong project.
Dayzen
