Skip to main content
Version: 6.0

Project Management — user documentation

This documentation describes how to work in the Projects section (Project Management): creating and managing projects, creating and controlling tasks, working with the team and roles, tracking effort via time entries, and using basic views to monitor progress.

Contents

Sections:

Quick start

A typical scenario “create a project → create tasks → assign assignees → track time”:

  1. Open Projects → Operations → Projects.
  2. Create a project and fill in the main fields:
    • type;
    • name;
    • start and end dates (if known);
    • status;
    • company and manager.
  3. Go to the project tasks and create tasks for the team.
  4. Assign assignees and due dates.
  5. While working, record effort using time entries (either directly or via timesheets).
  6. Monitor progress by task statuses and, if needed, use Kanban and the Gantt chart views available within the task list.

Typical scenarios

“Start a project from scratch”

  1. Create a project and fill in key fields (type, name, dates, company, manager).
  2. Prepare the team: add participants and roles, or assign a team to the project (if your organization uses teams).
  3. Create tasks and assign assignees and due dates.
  4. Agree on status rules (who changes statuses, when, and by which criteria).
  5. Establish time tracking discipline: record time entries daily or when work is completed.

Details: see Projects, Tasks, Team and roles on a project, Time entries.

“Manage project communication”

  1. Record agreements and decisions in project and task comments.
  2. When changing due dates and priorities, leave an explanation so participants understand the reason.
  3. For disputed cases, use the task change history.

The Projects section typically includes groups:

  • Operations — day-to-day work (projects, tasks, time entries, shifts). Kanban and the Gantt chart are views available within the task list, not separate menu items. Assignments are managed on the project card.
  • Processesemployee and supervisor timesheets for entering and controlling effort by days.
  • Reporting — entry point for project-related reports. In the base configuration this folder is typically populated by integrations with neighbouring modules (Sales, Manufacturing) rather than by stand-alone PM reports.
  • Configuration — directories and rules: project and task types, statuses, priorities, tags, workflow, project roles, and teams.

The exact menu set and action availability depend on configuration and user permissions.

User roles and permissions

The exact set of permissions depends on your organization’s configuration. A typical responsibility split:

  • Project manager — responsible for project dates and status, team composition, and task progress control.
  • Assignee — works with tasks: changes statuses within available transitions, leaves comments, and records time entries.
  • Observer/approver (if used) — views the project and tasks, participates in discussions, and may confirm completion according to internal rules.

If some actions are not available (for example, changing a status or creating a time entry), it is usually due to permission restrictions or workflow rules.

Terms

Project

A project is a planning unit: contains dates, status, the responsible person (manager), and combines related tasks, team, and effort.

Task

A task is a work unit within a project: what needs to be done, by what due date, and what the current execution status is.

Assignment

An assignment links a participant (employee or team) to a project with a project role and a participation period. A task does not have a separate assignment record — it references one assignee directly via its assignee field.

Time entry

A time entry is a record of actual time spent on work (usually by task/project) for effort control and reporting.

Shift

A shift is a planned work shift of an employee: a date, a time interval, the assigned employee, and optionally a project.

Status

A status is the state of a project or a task. See project statuses and task statuses.

Workflow

The workflow defines rules for task status transitions: what changes are allowed, in what order, and by whom.