Organisations
An organisation is the top-level workspace where your team, projects, and operational data are managed. Every project, member, and attendance record belongs to a single organisation.
Organisation-level roles include:
- Owner - Full control over the organisation, including administrative and configuration settings.
- Admin - Manages members, settings, and day-to-day operations.
- Member - Accesses projects and performs assigned work based on their permissions.
Projects
A project is a dedicated workspace for a specific initiative, such as a product launch, client engagement, or internal project.
Each project can have its own:
- Task board
- Sprint cycles
- Project members
- Roles and permissions
- Settings and workflows
This keeps project-specific work organised while giving teams the flexibility to manage each initiative independently.
Project roles
- Owner - Has full control of the project, including project deletion and configuration.
- Admin - Manages project members, settings, and all project tasks.
- Member - Creates and manages tasks, participates in discussions, and logs time.
- Viewer - Has read-only access to project boards and reports.
Tasks & subtasks
A task represents a specific piece of work that needs to be completed. Tasks provide the foundation for planning, assigning, and tracking work.
Depending on your project setup, tasks can include:
- Subtasks for breaking work into smaller steps
- Custom fields for project-specific information
- File attachments
- Comments and discussions
- Dependencies on other tasks
- Due dates and time tracking
Subtasks make complex work easier to manage by giving teams a clear view of individual deliverables and progress.
Statuses
Statuses show where a task currently stands in the workflow. A typical workflow may include:
To Do, In Progress, and Done
However, every project can customise its statuses to match the team's workflow. For example, a development team might use Backlog ,Development, Code Review, Testing and ,Released
Assignees
Assignees are the project members responsible for completing a task. A task can be assigned to one or multiple project members, depending on how your team works.
Assignees receive relevant notifications for activity such as:
- New comments
- Status changes
- Approaching due dates
- Task updates
Clear ownership helps teams understand who is responsible for each piece of work and reduces ambiguity.
Sprints
Sprints are an optional layer for teams that work in time-boxed development or delivery cycles.
A sprint groups related tasks around a defined goal and timeframe. Teams can use sprints to:
- Set sprint goals
- Plan and prioritise work
- Track completion
- Monitor progress with burndown charts
- Review performance at the end of the cycle
Sprints are particularly useful for Agile teams, but they are not required for every project.
Start Simple, Add Structure as You Grow
You don't need to configure everything before getting started. A project can operate with a simple task board and no sprints, custom fields, or complex workflows.
Start with the structure your team needs today, then introduce additional features as your projects become more complex.
Keep it simple. Stay organised. Add structure when it creates value.