---
title: "Status"
source: https://dev.pageseeder.com/reference/glossary/status.html
description: "Status represents the current state of tasks or document workflows in PageSeeder. Configurable by role, statuses follow a natural lifecycle order and indicate whether work is active or complete."
last_updated: 2026-09-05T17:33:51+10:00
tokens: ~1235
---

# Status

Is a value that can be given to a [task](/reference/glossary/task.md) or a document [workflow](/reference/glossary/workflow.md) to represent their current state. The status values, and [roles](/reference/glossary/role.md) that can use them, are configurable in the [group properties](/reference/glossary/group_properties.md).

## Document and task status

**Workflow status**

The [document status](/reference/glossary/document_status.md) applies to the workflow associated with the document. The status of the last workflow step is the status of the document.

**Task status**

The [task status](/reference/glossary/task_status.md) applies to comments in a discussion. The status of the last comment is the status of the task.

**Status icons**

As of PageSeeder v6, the icon used in the user interface for each status is configurable using the `statusIcon` and `documentStatusIcon` [group properties](/guide/configuration/properties/group_properties.md). The value associated with an icon is configured in the [group properties form](/reference/glossary/group_properties.md) in the UI, on either the **Group configuration** page or **Project configuration** page. The currently supported icons are as follows:

| status-open | For active tasks and workflows (see following section) |
| --- | --- |
| status-resolved | For resolved tasks and workflows |
| status-approved | For approved workflows |
| status-closed | When tasks and workflows no longer require any action |
| status-unknown | Indicates an unconfigured status |

### Status and roles

The status that a member can set on a document workflow or task is based on their role within a group. Each role can be associated with a list of statuses that appear as an option.

Only the Approver is able to set any document status.

| Role | Permissions and workflow options |
| --- | --- |
| Approver | Full editorial control – can manage documents and workflows |
| Manager | Limited editorial control – can manage documents and workflows |
| Contributor | Limited editorial control – can edit documents and only start or end work on a document |
| Reviewer | No editorial control – can only comment on documents and start or end work on a document |


When [configuring status](/reference/glossary/status.md), start with the ‘Approver’ role, and remove statuses that other roles are not allowed to set.


### Status order

The document or task status has a natural lifecycle order. The list of [workflow](/reference/glossary/document_status.md) or [task](/reference/glossary/task_status.md) values must be entered in the same order and reflect the order in which the document or task status is naturally changed.

## Active

A status is considered ‘active’ when there are activities associated with the task or workflow. In other words, an active task or workflow indicates work to be done.

PageSeeder displays active tasks and workflows by default in the user interface so that its easier to see which items require action.

The default active statuses are:

- **Task** – Open
- **Workflow** – Initiated, In Progress, Complete

### Locked state

Managers can configure which workflow status can mark a document as ‘locked’, making it uneditable until the status is changed (**workflow statuses only**).

## Default statuses

Unless a manager configures the group to use a different set of statuses, PageSeeder provides default statuses following a basic approval process that relies on the [roles](/_external/ps/doc/help/help/2_terms_and_explanations/term/role.md) of group members. 

- [Default task statuses](/reference/glossary/task_status.md)
- [Default workflow statuses](/reference/glossary/document_status.md)

## Configuration

Set in the [group properties](/reference/glossary/group_properties.md), the document workflow and task statuses depend on the role that a member has in the group.

> **Tip:** The maximum number of status is 12 task and 12 workflow statuses. However, apart from the consequence for the UI, it’s harder to get users to use statuses correctly when there are too many. The recommended setting is: 1. Consider whether you really need to use custom status first. 2. If you do, keep status names short and meaningful. 3. Ideally under 8 statuses each for tasks and workflows. 4. Configure custom statuses in the [global template](/reference/glossary/global_template.md) project, so that the correct statuses appear on the **My tasks & workflows** page.

### Allowing reviewers to update workflows

Only [administrators](/reference/glossary/administrator.md) can allow *reviewers* to update workflows by editing the [global properties](/guide/configuration/properties/global_properties.md).

> **Note:** This cannot be enabled using the UI; the administrator must have access to the server file system to edit the *global properties*.

To allow reviewers to update workflows, add the `create-workflow` value to the `reviewerEnable` property.