---
title: "Get started with Comala Document Approval for Cloud"
canonical: "https://support.appfire.com/space/CDACL/629575049/Get%20started%20with%20Comala%20Document%20Approval%20for%20Cloud"
format: markdown
---
> Macro (aura-html)
The [Basic Approval Workflow](https://appfire.atlassian.net/wiki/spaces/CDALS/pages/649560387) above consists of three states - **Review**, **Rejected** and **Approved**** **- and one or more transitions from a state to one or more of the other states.
The applied workflow manages the document approval process with content moving from one state to another.
- the **Review** state is a state for draft content and allows one or more users to approve or reject the page or bog post content
- the **Approved** state is our final content that has been approved
- if the **Approved** content is updated the workflow moves back to the **Review** state
> ℹ️ The **Approved** state is defined as the **final state** for your reviewed and approved document.
The Comala Document Approval workflow has different workflow states and approval process that is used to
- ensure that page content is reviewed and signed-off
- assign specific users as reviewers for the content review in a workflow state
> ℹ️ Only one approval workflow can be active on an individual page or blog post at any one time.
## Adding a workflow to pages and blog posts
You can add the approval workflow to your documents in two ways
- [individually to each page or blog post](https://appfire.atlassian.net/wiki/spaces/CAD/pages/613515321)
- [across all the pages and blog posts in a space](https://appfire.atlassian.net/wiki/spaces/CAD/pages/613515327)
Applying a workflow to all space content using the [Comala Document Approval app space settings](https://appfire.atlassian.net/wiki/spaces/CAD/pages/613516220) allows greater central management of your content. This is the recommended use of a Comala Document Approval workflow in a production environment.
### Permissions
You must have at least view and edit permission to apply the approval workflow to a document. In addition, you must have space administrator permission to apply the apporval workflow to all the pages and blog posts in the space.
Page-level restrictions can affect the successful application of the approval workflow. If the page-level restrictions do not include the Comala Document Approval app add-on user, page activity is not processed by the approval workflow, for example, if the page is updated or a page is created with restrictions.
The approval workflow cannot be added to archived documents and documents in the trash.
### Approval workflow added to a page
Once a workflow is added and applied to a document, the approval workflow automatically defines the document as approved or draft depending on the approval state.
Pages and blog posts with an applied workflow have an approval workflow state breadcrumb added to the document page sub-title.
> ℹ️ If the page or blog post has previously been approved, a **View approved** byline link to the last approved version is also displayed.
Choose the **View approved** to view the last approved version.
When viewing this last approved version of the document, the following are displayed on the page
- the byline :check_mark: **Approved (Compare versions)** is displayed, confirming this is an approved version
- a link **View pending approval** to the current draft state version
> 📝 A user with **view-only** permission will be able to access the byline links on the draft content version to view the latest approved version.
### Using the approval workflow on the page
A page editor’s key interaction with the workflow added to a page is through the approval workflow popup accessed using the state byline.
The [approval workflow popup](https://appfire.atlassian.net/wiki/spaces/CAD/pages/613515456) includes options for moving the workflow from the current state to a destination state.
The popup progress tracker bar displays the states in the workflow and the destination state for the approval decision
The movement between these states is called a [transition](https://appfire.atlassian.net/wiki/spaces/CAD/pages/613515472). In the **Review** and **Rejected** states, these transitions occur based on a user approving, rejecting, or updating the page.
### Add a workflow on a page-by-page basis to each page or blog post
You add a workflow on a page-by-page basis by choosing the **Add Workflow** byline on a page.
### Add the workflow to all the pages and blog posts
A space administrator can use the [document approval space settings](https://appfire.atlassian.net/wiki/spaces/CDACL/pages/689735195) to add and apply the approval workflow to all pages and blog posts in a space.
In the app space settings:
- move the **Basic Approval Workflow** grey slider to blue to make the workflow active
When active, the approval workflow is applied to all the pages and blog posts in the space.
### Approving documents
When the approval workflow is applied, the [approval state byline breadcrumb](https://appfire.atlassian.net/wiki/spaces/CDACL/pages/689570358) is added to the page or blog post. This is the [initial state of the approval workflow](https://appfire.atlassian.net/wiki/spaces/CDACL/pages/689504699)—the **Review **state.
A single reviewer can approve the document using the **Approve** button. You can also assign one or more reviewers using the **Add reviewer **option.
Only assigned users can undertake the approval and all the assigned reviewers must agree.
## Reporting approval workflow activity
> Macro (excerpt-include)
> Macro (excerpt-include)
> Macro (excerpt-include)
> Macro (excerpt-include)