> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rdrive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Difference Between Process and Form Permissions

> A Process must include at least one Form, but it can have multiple Forms. When a Process is created, it automatically generates the associated Form(s) since the

# **Understanding the Relationship Between Process and Form**

A **Process** must include at least one **Form**, but it can have multiple Forms. When a Process is created, it automatically generates the associated Form(s) since they are linked as a single entity. However, actions on the Process and the Form can be managed separately.

<img src="https://mintcdn.com/rdrive/BVSE_UjBxwO8d3yO/images/kb/103000336139/sfbdiRn23ikFjgme02iZdslQKdBL1RJssg.png?fit=max&auto=format&n=BVSE_UjBxwO8d3yO&q=85&s=430f5dc57629551cf16504c0e1659937" alt="Difference Between Process and Form Permissions" width="526" height="681" data-path="images/kb/103000336139/sfbdiRn23ikFjgme02iZdslQKdBL1RJssg.png" />

***

**TABLE OF CONTENTS**

* [Understanding the Relationship Between Process and Form](#understanding-the-relationship-between-process-and-form)
  * [Common Actions](#common-actions)

    * [Create](#create)

    * [Read](#read)

    * [Share](#share)

    * [Unshare](#unshare)

    * [Differences in Actions](#differences-in-actions)
  * [Process-Specific Actions](#process-specific-actions)

    * [Change Controller](#%e2%80%8bchange-controller)
    * [Move](#%e2%80%8b%e2%80%8bmove)
    * [Delete](#%e2%80%8b%e2%80%8bdelete)
  * [Form-Specific Actions](#form-specific-actions)

    * [Edit](#edit)
    * [Change Status](#change-status)
    * [Close](#close)
    * [Reopen](#reopen)
    * [Assign](#assign)
    * [Assign](#assign-1)

***

## **Common Actions**

Both Process and Form permissions share the following common actions:

* **Create**

* **Read**

* **Share**

* **Unshare**

### Differences in Actions

| Action      | Process Permission                                                                                                  | Form Permission                                                                                                                |
| ----------- | ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **Create**  | Creating a Process automatically generates its associated Form(s).                                                  | Allows users to add additional Forms to an existing Process. By default, all Forms in the Process are available for selection. |
| **Read**    | Grants permission to read the Process.                                                                              | Grants permission to read the Form(s).                                                                                         |
| **Share**   | Sharing a Process assigns **Read** permission for the entire Process.                                               | Sharing a Form assigns **Read** permission only for that specific Form.                                                        |
| **Unshare** | Removing sharing revokes **Read** permission for the Process unless the user has explicit read permission assigned. | Removing sharing revokes **Read** permission for the Form unless the user has explicit read permission assigned.               |

### Important Notes on Read Permission

* If a user has **Read Process** permission but lacks **Read Form** permission, they will not be able to view the Process. The process will only become visible if **at least one form is shared** with them, and the shared form will be displayed within the process.

* If a user has **Read Form** permission but lacks **Read Process** permission, they will also be unable to view any Process details. Only if a Form is shared with them **along with Read Process permission** will they gain access to the entire Process.

***

## **Process-Specific Actions**

The following actions apply **only to Processes**:

* **Change Controller**
* **Move**
* **Delete**

<table><tbody><tr><td><span><span>Action</span></span></td><td><span><span>Description</span></span></td></tr><tr><td><span><span><strong>Change Controller</strong></span></span></td><td><span><span>Allows changing the Process controller.</span></span></td></tr><tr><td><span><span><strong>Move</strong></span></span></td><td><span><span>Enables moving the Process’s drawing/location and editing external references.</span></span></td></tr><tr><td><span><span><strong>Delete</strong></span></span></td><td><span><span>Deletes the entire Process.</span></span></td></tr></tbody></table>

***

## **Form-Specific Actions**

The following actions apply **only to Forms**:

* **Edit**
* **Change Status**
* **Close**
* **Reopen**
* **Assign**

<table><tbody><tr><td><span><span>Action</span></span></td><td><span><span>Description</span></span></td></tr><tr><td><span><span><strong>Edit</strong></span></span></td><td><span><span>Allows users to modify Form fields.</span></span></td></tr><tr><td><span><span><strong>Change Status</strong></span></span></td><td><span><span>Enables users to update the Form status.</span></span></td></tr><tr><td><span><span><strong>Close</strong></span></span></td><td><span><span>Changes the Form status to a terminal (closed) state.</span></span></td></tr><tr><td><span><span><strong>Reopen</strong></span></span></td><td><span><span>Moves the Form status from a terminal (closed) state back to an active state.</span></span></td></tr><tr><td><h4 id="Assign-1"><span><span><strong>Assign</strong></span></span></h4></td><td><span><span>Assigns the Form to a user or team for follow-up actions. <strong>Assignment also includes sharing the Form.</strong></span></span></td></tr></tbody></table>

**Note on Assignments:**

* Assigning a Form to a **team** makes all team members participants, granting them access. 

* Assigning a Form to an **individual user** makes them a subscriber, meaning they will receive status notifications.

This document clarifies the differences in permissions between **Process** and **Form** to ensure proper access control and workflow management.

***

If you're unsure how to start setting up Permission Policies, find ideas and tips [**here**](https://docs.rdrive.io/setup/project/permission-policies-and-team-profiles/what-is-edit-usage-in-permission-policies)**.** 

For a detailed guide on designing organized Permission Policies, click [**here**](https://docs.rdrive.io/setup/project/permission-policies-and-team-profiles/manage-the-permission-policy)**.**

To understanding Permission Policies and Rules, click [](https://docs.rdrive.io/setup/project/permission-policies-and-team-profiles/difference-between-process-and-form-permissions)[**here**](https://docs.rdrive.io/setup/project/permission-policies-and-team-profiles/understanding-permission-policies-and-rules)**.**