Skip to main content
A project is a workspace for a piece of work your organisation is delivering. It holds tasks, its own set of task statuses and task types, optional objectives and goals, and its own people and roles. Every project has up to five views: Overview, Tasks, Board, Gantt (when the project uses due dates) and, once it has a description, About. Each person on a project holds one of four roles that decide what they can change. Built for committees, working groups and staff teams that plan work in Orgo rather than in a separate tool, so the people, groups and permissions are already there. Replaces a spreadsheet of action items or a standalone task tracker for internal work. It is not a client-facing or billable project tool: there is no time tracking, no budget and no external sharing.

Turning it on

Projects is a module, off by default: Settings → Modules → Projects → Enable Project Management (organization admins only). The same switch also enables project groups, described at the end of this page. A Projects section then appears in the sidebar listing the projects you can open, with a search button once there are more than two. Its label can be renamed in the menu organiser. The sidebar has a button for all projects and a plus button to create one. Projects module settings with the Enable Project Management switch turned on and its helper text

Who can do what

Every person on a project holds one of four fixed roles. Organization admins and HR managers hold the Admin role on every project without being added. The project owner is always an Admin. If someone has access several ways (individually and through a group, say), the highest role wins.

Creating a project

The Projects page with its Active and Archived tabs, the My tasks and Create project buttons, and a card per project showing its open task count and progress bar The sidebar plus button, or Projects → Create project, opens the New project form. Most of it can be changed later in project settings. Saving creates five task statuses: Backlog, To do, In Progress, Review and Done, with Done marked as closed.

Giving people access

Owner, individual members and group access stack. Add people and groups under Settings → Members, using the search box: pick a person or a group, then a role. Only active accounts qualify, and nobody twice. Changing a role, or removing someone, takes effect straight away. ADMIN_TENANT and HR_TENANT see every project as Admin regardless. The project header shows a stack of the people with access; click it for the full list, with each person’s role and the groups. Members of a group are not listed one by one. The owner is always an Admin and cannot be removed. To hand the project over, make the new person an Admin first, then use Change owner; the previous owner stays an Admin. The Members section of project settings listing the owner, the groups that have access and the individual people added, each with the role they hold Under Settings → Members, People with access lists the owner, every group and every individually added person, each with a role. Use Add to search people and groups; whatever you add starts as Member, and you change the role from the row. Remove access with the bin button. The owner is changed with Change owner, which offers the project’s other Admins, so make someone an Admin first. A What each role can do table on the same screen shows exactly what each role may do. Two options sit under it:
  • Contributors and viewers see: All tasks, or Only assigned, which limits those two roles to tasks they created or are assigned to (plus tasks that block or wait on one of theirs). Use it for volunteers or clients who should not see the whole backlog.
  • Viewers can comment: off by default.
Groups that include all members count too: once a group is set to include everyone, every active member gets that group’s role on the project. When you remove a person who still has open tasks on the project, Orgo asks who takes them over (Reassign open tasks), or you can leave them unassigned. Someone removed from a project no longer gets task emails for it. The row of avatars in the project header (In this project) shows who is on the project, with a Manage people and roles link for Admins.

Roles

Roles are fixed, so everyone knows what to expect. A person who reaches the project in several ways (owner, individually, through two groups) gets the highest role among them. A group with no role set is treated as Contributor, and so is anyone who was a project member before roles existed, so nobody lost or gained access when roles arrived. Own means tasks the person created or is assigned to, and files they uploaded. Deleting is the narrower case: only tasks the person created. Two options sit under the table:
  • Contributors see: All tasks, or Only assigned for volunteers or clients who should not see the whole backlog. With Only assigned, a Contributor sees just the tasks they created or are assigned to, in the lists, the board, the timeline and when opening a task by link.
  • Viewers can comment: off by default. When on, a Viewer can reply on tasks but not change them.
The interface hides what a role cannot do (a Viewer sees no Add task button), and the server refuses it anyway.

The project views

Opening a project returns you to the tab you used last in it, and on a first visit to the Overview. A project Overview with the open, overdue, due and unassigned tiles across the top, the Urgent and Needs attention cards on the left, and Workload and Recent activity on the right The assignee, type and objective filters are shared across Overview, Tasks, Board and Gantt, and live in the address bar (?assignee=, ?type=, ?objective=), so a filtered view can be linked. Each member lands on the tab they used last in a project; the first visit opens the Overview. Dropping files anywhere on a project opens the new task form with those files attached. The Board tab with a column per status, task cards carrying their ID, priority, type, due date and checklist progress, and an Add task action at the foot of each column Dropping files anywhere on a project opens a new task with those files attached.

Objectives and goals

Switch on Objectives in the project’s task options, then open Settings → Objectives (the old Objectives & Goals page now lives there, and its address redirects). An objective is a phase or milestone that tasks belong to: a name, a colour and optional start and end dates. Tasks then carry an Objective field, the task list filters by it, Overview tracks progress against it and dated objectives get their own bars on the Gantt. A goal sits a level above, for projects with several strands of work; turn on Group objectives under goals and drag objectives into them. With it off you get one flat list. Both reorder by dragging (or Alt with the arrow keys), and deleting a goal keeps its objectives.
The interface and the API swap the two words. What this page calls an objective is the Goal resource in the API, and a goal is the Objective resource.
For bigger projects you can group objectives under goals: choose Group objectives under goals, then Add goal, and move objectives between goals from each row. A goal has a name and a colour. Removing a goal keeps its objectives. Once goals exist, the task filters offer both Goal and Objective, and tasks can be grouped by goal. Tasks and the Overview then show progress per objective. The task list can group and filter by objective.

Project settings

The Settings button in the project header opens four tabs, for Admins: Changes save as you make them, and the tab shows All changes saved when they have. Task key is the prefix of every task ID in the project (ORG-145): 2 to 6 letters or digits, starting with a letter, unique across your organisation. New projects get one from their name. Changing it updates the ID shown on every task, and links that used the old key keep working. Each status has a name, a colour, a Closed switch and a circle that shows progress (from empty to full, or dashed for none). Closed statuses are hidden from Open tasks, and a project must keep at least one open and one closed status. A new project starts with Backlog, To do, In Progress, Review and Done, with Done closed. A type is a name and a colour. Deleting a status or type that tasks still use asks where to move those tasks first. Archive project moves it to the Archived tab, still readable and restorable from there. Its tasks stop sending assignment, status, comment and reminder emails and drop off the dashboard My Tasks card, but still appear in the daily task digest. Delete project is permanent, asks you to type the project name, and takes the tasks, objectives, goals, statuses and types with it.

Projects and project groups

The same module switch also turns on an older feature that uses the word project. A project group is an ordinary group with issue tracking switched on, created from Issues → New: it gains an Issues tab with its own issue statuses and types, lives with the group rather than on the Projects page, and issue tracking can only be set at group creation. See Issues. A project in the sense of this page is a separate record with its own people, tasks, board and Gantt, listed under Projects in the sidebar. It can grant access to groups, but it is not one. Starting fresh, use Projects; project groups remain for organisations already tracking issues inside their groups.
  • Tasks - everything a task holds and how the reminders work
  • Issues - the group issue tracker and project groups
  • Groups - the groups a project can grant access to
  • Permissions - what organization admins and HR managers unlock
  • Notifications - the member-side notification switches