odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/services/project/tasks/recurring_tasks.md

@@ -0,0 +1,50 @@
+---
+title: "Recurring tasks"
+source_url: "https://docs.odoo.sbggai.top/applications/services/project/tasks/recurring_tasks.html"
+---
+
+===============
+# Recurring tasks
+
+When handling a project, the same task often needs to be performed several times: for example,
+weekly meetings or status reports. The **recurring tasks** feature allows you to automate the
+creation of those tasks.
+
+.. seealso::
+   [Odoo Tutorials: Recurring tasks ](https://www.odoo.com/slides/slide/recurring-tasks-1946)
+
+# Configuration
+
+To enable recurring tasks, go to :menuselection:`Project --> Configuration --> Settings`, then
+activate :guilabel:`Recurring Tasks`, and press :guilabel:`Save`.
+
+## Set up task recurrence
+
+In an existing task, click the :icon:`fa-repeat` (:guilabel:`Recurrent`) button next to the
+:guilabel:`Deadline` field. Then, configure the :guilabel:`Repeat Every` field according to your
+needs.
+
+A new task in recurrence will be created once the status of the previous task is set to
+:guilabel:`Done` or :guilabel:`Canceled`.
+
+The new task is created on the project dashboard with the following configuration:
+
+- :guilabel:`Stage`: is set to the first stage of the project dashboard (:guilabel:`New` or
+  equivalent);
+- :guilabel:`Name`, :guilabel:`Description`, :guilabel:`Project`, :guilabel:`Assignees`,
+  :guilabel:`Customer`, :guilabel:`Tags`: are copied from the original task;
+- :guilabel:`Deadline`: is updated based on the :guilabel:`Repeat Every` field (e.g., if the task is
+  set to repeat once a week, 7 days will be added to the deadline);
+- :guilabel:`Milestones`, :guilabel:`Timesheets`, :guilabel:`Chatter`,
+  :guilabel:`Activities`, :guilabel:`Subtasks`: are **not** copied from the original task.
+
+Once a recurrence is configured, a **smart button** on the task displays the total number of
+existing recurrences.
+
+## Edit or stop task recurrence
+
+**To edit** the recurrence, open the last task in recurrence. Any changes made on the task will be
+applied to the tasks that will be created in the future.
+
+**To stop** the recurrence, open the last task in recurrence and press the :guilabel:`Recurrent`
+button next to the :guilabel:`Planned date`.

package/payload/skills/odoo18-docs/references/docs/applications/services/project/tasks/sub-tasks.md

@@ -0,0 +1,53 @@
+---
+title: "Sub-tasks"
+source_url: "https://docs.odoo.sbggai.top/applications/services/project/tasks/sub-tasks.html"
+---
+
+=========
+# Sub-tasks
+
+When handling project tasks, you can often benefit from splitting the workload into smaller
+**sub-tasks**, making it easier to track progress and manage the work.
+
+Odoo’s sub-task feature is particularly useful in some of the following cases:
+
+- The task workload is too big to handle in one record.
+- There’s a clear sequence of steps to follow.
+- Some parts of the workload fall under the scope of different projects and/or assignees.
+
+The original task to which sub-tasks are linked is referred to as the **parent task**. The sub-tasks
+of the parent task are known as **child tasks**.
+
+# Creating sub-tasks
+
+To create a sub-task:
+
+#. Open the Project app, then go into your desired project.
+#. Click the task where you want to add the sub-task, then click the :guilabel:`Sub-tasks` tab.
+#. Click :guilabel:`Add a line`, then fill in the :guilabel:`Title`.
+#. Click the :icon:`fa-cloud-upload` (:guilabel:`save`) icon to save the task manually.
+
+> **tip**:
+>    You can edit several fields of a sub-task directly from the parent task’s sub-task tab without
+   opening the individual sub-task. By default, those are: :guilabel:`Title`, :guilabel:`Priority`,
+   :guilabel:`Status`, and :guilabel:`Assignees`. Use the :icon:`fa-sliders` (:guilabel:`sliders`)
+   icon to add or remove fields.
+
+Once the new sub-task is created, the following changes occur in the parent task:
+
+- A **smart button** displays the total number of sub-tasks, as well as the number of closed
+  (**done** or **canceled**) sub-tasks. Click the smart button to access the list of the sub-tasks.
+- The :guilabel:`Allocated time` displays the amount of time allocated to the parent task, as well
+  as time allocated to the sub-tasks. This can be used to ensure that the time allocated to
+  sub-tasks does not exceed time allocated to the parent task.
+- The :guilabel:`Timesheets` tab includes a breakdown of time spent on the parent task as well as
+  sub-tasks.
+
+Click :guilabel:`View` to open the sub-task you created. The sub-task form is identical to the
+:ref:`task form <task_creation/task-configuration>`.
+
+> **tip**:
+>  - A **smart button** allows to navigate back to the :guilabel:`Parent task`.
+ - The :guilabel:`Sub-tasks` tab allows for further creation of sub-tasks.
+ - Selecting a :guilabel:`Project` will trigger this sub-task to be displayed in the Kanban view of
+   the selected project.

package/payload/skills/odoo18-docs/references/docs/applications/services/project/tasks/task_creation.md

@@ -0,0 +1,124 @@
+---
+title: "Task creation"
+source_url: "https://docs.odoo.sbggai.top/applications/services/project/tasks/task_creation.html"
+---
+
+=============
+# Task creation
+
+Tasks in Odoo Project can be created manually or automatically, including from emails or website
+forms.
+
+# Manual task creation
+
+Open the Project app and choose the desired project. Create a new task by doing one of the
+following:
+
+ - Clicking the :icon:`fa-plus` (:guilabel:`plus`) button in the upper left corner. This creates
+   a new task in the first stage of your Kanban view.
+ - Pressing the :icon:`fa-plus` (:guilabel:`plus`) button next to the Kanban stage name. This
+   creates a new task in this Kanban stage.
+
+Fill in the :guilabel:`Task Title` and add one or more :guilabel:`Assignees`, then click
+:guilabel:`Add`.
+
+.. _task_creation/task-configuration:
+
+## Task configuration
+
+Click the task to open it. The task form includes the following fields that you can fill in:
+
+ - :guilabel:`Task Title`: title of the task.
+ - :icon:`fa-star-o` (:guilabel:`Star`): click the :icon:`fa-star-o` (:guilabel:`star`) icon to mark
+   the task as high priority. The icon will turn yellow. Click it again to remove the high priority.
+ - :guilabel:`Project`: the project that this task belongs to.
+ - :guilabel:`Assignees`: the person(s) in charge of handling the work on this task.
+ - :guilabel:`Tags`: custom labels allowing to categorize and filter your tasks.
+ - :guilabel:`Customer`: the person or company that will be billed for this task. This field only
+   appears in tasks that belong to billable projects.
+ - :guilabel:`Sales Order Item`: this can be either the sales order that was used to create this
+   task, or a sales order that was linked to this task manually. This field only appears in tasks
+   linked to billable projects.
+ - :guilabel:`Allocated Time`: the amount of time that the work on this task is expected to last,
+   tracked by timesheets.
+ - :guilabel:`Deadline`: the expected end date of the task. Once this field is filled in, you can
+   also add a start date to designate the entire time frame of the tasks' duration.
+
+> **tip**:
+>    - You can also create new tasks by switching to the list or Gantt view and clicking
+     :guilabel:`New`.
+   - The following fields can also be edited directly from the Kanban view without opening the
+     individual task: :icon:`fa-star-o` (**priority**), :guilabel:`Allocated hours`,
+     :guilabel:`Assignees`, and **task status**. You can also **color code** or :guilabel:`Set a
+     Cover image` to your task by clicking the :icon:`fa-ellipsis-v` (**vertical ellipsis**).
+   - You can use the following keyboard shortcuts in the task title to configure new tasks (modify
+     the values in the examples below according to your needs):
+
+     - **30h**: to allocate 30 hours to the task.
+     - **#tags**: to add tags to the task.
+     - **@user**: to assign the task to a user.
+     - **!**: to star the task as high priority.
+
+     Along with using the correct format, follow this order: the task's name, followed by the
+     allocated time, the tags, the assignee, and then the priority.
+
+     For example, if you want to create a task named "Prepare workshop", allocate 5h hours to it,
+     add the "School" tag, assign it to Audrey and set its priority to :guilabel:`High`, enter the
+     following task title: Prepare workshop 5h #school @Audrey !
+
+     .. image:: task_creation/task-shortcuts.png
+        :alt: Using keyboard shortcuts to create a task in Project.
+
+.. _task_creation/email_alias:
+
+# Creating tasks from an email alias
+
+This feature allows for project tasks to be automatically created once an email is delivered to a
+designated email address.
+
+To configure it, open the Project app, then click the :icon:`fa-ellipsis-v` (:guilabel:`vertical
+ellipsis`) icon next to the desired project's name. Select :guilabel:`Settings`, then open the
+:guilabel:`Settings` tab.
+
+Fill in the :guilabel:`Create tasks by sending an email to` field as follows:
+
+ - **Section of the alias before the @ symbol**: type the name of the email alias, e.g. `contact`,
+   `help`, `jobs`.
+ - **Domain**: in most cases, this is filled in by default with your :doc:`domain
+   <../../../general/email_communication>`.
+ - **Accept Emails From**: refine the senders whose emails will create tasks in the project.
+
+.. image:: task_creation/email-configuration.png
+   :alt: View of the email alias chosen on the dashboard view in Odoo Project
+
+Once configured, the email alias can be seen under the name of your project on the Kanban dashboard.
+
+When an email is sent to the alias, the email is automatically converted into a project task. The
+following rules apply:
+
+- The email sender is displayed in the :guilabel:`Customer` field.
+- The email subject is displayed in the :guilabel:`Task Title` field.
+- The email body is displayed in the :guilabel:`Description` field.
+- The whole content of the email is additionally displayed in the **chatter**.
+- All the recipients of the email (To/Cc/Bcc) that are Odoo users are automatically added as
+  **followers** of the task.
+
+# Creating tasks from a website form
+
+If you have the Website app installed in your database, you can configure any form on your
+website to trigger the creation of tasks in a project.
+
+#. Go to the website page where you wish to add the the form and
+   :ref:`add the Form building block <websites/website/web_design/building_blocks>`.
+#. In the website editor, edit the following fields:
+
+   - :guilabel:`Action`: select :guilabel:`Create a Task`.
+   - :guilabel:`Project`: choose the project that you want the new tasks to be created in.
+
+#. :ref:`Customize the form <website/dynamic_content/form>`.
+
+When the form is submitted, it automatically creates a project task. The task's content is defined
+by the form's corresponding fields.
+
+.. seealso::
+   :doc:`Dynamic website content <../../../websites/website/web_design/building_blocks/dynamic_content>`

package/payload/skills/odoo18-docs/references/docs/applications/services/project/tasks/task_dependencies.md

@@ -0,0 +1,46 @@
+---
+title: "Task dependencies"
+source_url: "https://docs.odoo.sbggai.top/applications/services/project/tasks/task_dependencies.html"
+---
+
+=================
+# Task dependencies
+
+Odoo Project allows you to break down projects into tasks and establish relationships between those
+tasks to determine the order in which they are executed. Task dependencies ensure that certain tasks
+begin only after the preceding tasks are completed.
+
+To enable task dependencies in projects, go to :menuselection:`Project --> Configuration -->
+Settings`, enable :guilabel:`Task Dependencies`, and click :guilabel:`Save`.
+
+# Set task dependencies
+
+Task dependencies can be created from the task form or the project's Gantt view by linking the
+successor task (i.e., the task blocked by other tasks) to its predecessor task(s) (i.e., the tasks
+blocking the successor task).
+
+To create task dependencies from the task form, access the desired task and, in the
+:guilabel:`Blocked by` tab, click :guilabel:`Add a line`. Click :guilabel:`View` to access the
+predecessor task. To access the successor tasks from the predecessor task, click the
+:guilabel:`Blocked Tasks` smart button.
+
+To create a task dependency from the Gantt view, hover your mouse over the predecessor task, then
+click one of the dots that appear around it. Drag and drop the dot onto the successor task. An arrow
+appears, indicating the dependency from the predecessor task to the successor.
+
+.. image:: task_dependencies/task-dependency.png
+   :scale: 80%
+   :alt: Task dependency
+
+Odoo automatically manages task progress based on their dependency. Successor tasks are assigned the
+:guilabel:`Waiting` status and cannot be moved to :guilabel:`In Progress` until their predecessor
+task(s) are marked as :guilabel:`Approved`, :guilabel:`Cancelled`, or :guilabel:`Done`.
+
+# Remove dependencies
+
+To remove a task dependency, proceed as follows:
+
+- From the task form, go to the **Blocked by** tab and click the :icon:`fa-times`
+  (:guilabel:`times`) button.
+- From the Gantt view, click the red :icon:`fa-times` (:guilabel:`times`) button that appears at the
+  center of the arrow when you hover your mouse over it.

package/payload/skills/odoo18-docs/references/docs/applications/services/project/tasks/task_stages_statuses.md

@@ -0,0 +1,74 @@
+---
+title: "Task stages and statuses"
+source_url: "https://docs.odoo.sbggai.top/applications/services/project/tasks/task_stages_statuses.html"
+---
+
+========================
+# Task stages and statuses
+
+# Task stages
+
+Task stages are displayed as columns in the project's Kanban view, and allow you to update the
+progress of its tasks with a drag-and-drop. In most projects, the stages will be akin to **New**,
+**In progress**, **Backlog**, etc.
+
+By default, task stages are project-specific but can be shared across multiple projects that follow
+the same workflow.
+
+## Creating task stages
+
+Odoo Project doesn’t provide default stages but instead allows you to create custom stages tailored
+to your specific business needs. You are prompted to do so immediately after :ref:`creating a new
+project <project_management/configuration>`.
+
+To create a stage, type its name into the :guilabel:`Stage...` field, then click :guilabel:`Add`.
+
+> **tip**:
+>    Click :guilabel:`See examples` to find ideas for stage names applicable to your line of business.
+
+## Editing task stages
+
+To edit the task stage, click the :icon:`fa-cog` (:guilabel:`cog`) icon next to its name. From
+there, click one of the following:
+
+ - :guilabel:`Fold`: to hide the task stage and all of the tasks in this stage from the Kanban view.
+ - :guilabel:`Edit`:
+
+   - :guilabel:`Name`: to change the name of the stage.
+   - :guilabel:`SMS/Email Template`: to automatically send an email or SMS notification to the
+     customer when a task reaches this stage.
+   - :guilabel:`Folded in Kanban`: to hide the task stage and all of the tasks in this stage from
+     the Kanban view.
+   - :guilabel:`Projects`: to share this task stage between several projects.
+   - :guilabel:`Automations`: to create :doc:`custom rules that trigger automatic actions
+     <../../../studio/automated_actions>` (e.g., creating activities, adding followers, or sending
+     webhook notifications). Note that this will activate Studio in your database, which may impact
+     your pricing plan.
+
+ - :guilabel:`Delete`: to delete this stage.
+ - :guilabel:`Archive/Unarchive all`: to archive or unarchive all of the tasks in this stage.
+
+.. _project/tasks/task_stages_statuses/statuses:
+
+# Task statuses
+
+Task statuses are used to track the status of tasks within the Kanban stage, as well as to close the
+task when it’s done or canceled. Unlike Kanban stages, they cannot be customized; five task statuses
+exist in Odoo and are used as follows:
+
+ - :guilabel:`In Progress`: this is the default state of all tasks, meaning that work required for
+   the task to move to the next Kanban stage is ongoing.
+ - :guilabel:`Changes Requested`: to highlight that changes, either requested by the customer or
+   internally, are needed before the task is moved to the next Kanban stage.
+ - :guilabel:`Approved`: to highlight that the task is ready to be moved to the next stage.
+ - :guilabel:`Canceled`: to cancel the task.
+ - :guilabel:`Done`: to close the task once it's been completed.
+
+> **note**:
+>    - The :guilabel:`Changes Requested` and :guilabel:`Approved` task statuses are cleared as soon as
+     the task is moved to another Kanban stage. The task status reverts to the default :guilabel:`In
+     Progress` status so that :guilabel:`Changes Requested` or :guilabel:`Approved` status can be
+     applied again once the necessary work has been completed in this Kanban stage.
+   - The :guilabel:`Done` and :guilabel:`Canceled` statuses are independent from the Kanban stage.
+     Once a task is marked as :guilabel:`Done` or :guilabel:`Canceled`, it is closed. If needed, it
+     can be reopened by changing its status.

package/payload/skills/odoo18-docs/references/docs/applications/services/project/tasks.md

@@ -0,0 +1,17 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/services/project/tasks.html"
+---
+
+:nosearch:
+# 
+# Task management
+
+.. toctree::
+   :titlesonly:
+
+   tasks/task_stages_statuses
+   tasks/task_creation
+   tasks/recurring_tasks
+   tasks/sub-tasks
+   tasks/task_dependencies

package/payload/skills/odoo18-docs/references/docs/applications/services/project.md

@@ -0,0 +1,23 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/services/project.html"
+---
+
+:show-content:
+:nosearch:
+:hide-page-toc:
+:show-toc:
+# 
+# Project
+
+Odoo Project is a tool to manage your ongoing projects. Schedule tasks, assign activities to
+coworkers, and keep track of each project's profitability.
+
+.. seealso::
+   [Odoo Tutorials: Project and Timesheets ](https://www.odoo.com/slides/project-and-timesheets-21)
+
+.. toctree::
+   :titlesonly:
+
+   project/project_management
+   project/tasks

package/payload/skills/odoo18-docs/references/docs/applications/services/timesheets/overview/time_off.md

@@ -0,0 +1,50 @@
+---
+title: "Create Timesheets upon Time Off Validation"
+source_url: "https://docs.odoo.sbggai.top/applications/services/timesheets/overview/time_off.html"
+---
+
+==========================================
+# Create Timesheets upon Time Off Validation
+
+Odoo automatically timesheets on project/tasks upon time off requests. This allows for better
+overall control over the validation of timesheets, as it does not leave place for forgetfulness
+and questions after hours that have not been timesheeted by the employee.
+
+Activate the :ref:`developer mode <developer-mode>`, go to *Timesheets*, and change the *Project*
+and *Task* set by default, if you like.
+
+.. image:: time_off/record_time_off.png
+   :align: center
+   :alt: View of Timesheets setting enabling the feature record time off in Odoo Timesheets
+
+Go to :menuselection:`Time Off --> Configuration --> Time Off Types`. Select or create the
+needed type, and decide if you would like the requests to be validated or not.
+
+.. image:: time_off/time_off_types.png
+   :align: center
+   :alt: View of a time off types form emphasizing the time off requests and timesheets section in
+         Odoo Time Off
+
+| Now, once the employee has requested his time off and the request has been validated (or not,
+  depending on the setting chosen), the time is automatically allocated on *Timesheets*, under the
+  respective project and task.
+| On the example below, the user requested *Paid Time off* from July 13th to 15th.
+
+.. image:: time_off/time_off_request.png
+   :align: center
+   :alt: View of the time off request form in Odoo Time Off
+
+Considering that validation is not required, the requested time off is automatically displayed in
+*Timesheets*. If validation is necessary, the time is automatically allocated after the responsible
+person for validating does it so.
+
+.. image:: time_off/timesheets.png
+   :align: center
+   :alt: Video of timesheets emphasizing the requested time off from the employee in Odoo Timesheets
+
+Click on the magnifying glass, hovering over the concerned cell, to access all the aggregated data
+on that cell (day), and see details regarding the project/task.
+
+.. image:: time_off/timesheet_description.png
+   :align: center
+   :alt: View of the details of a project/task in Odoo Timeheets

package/payload/skills/odoo18-docs/references/docs/applications/services/timesheets/overview.md

@@ -0,0 +1,13 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/services/timesheets/overview.html"
+---
+
+:nosearch:
+# 
+# Overview
+
+.. toctree::
+   :titlesonly:
+
+   overview/time_off

package/payload/skills/odoo18-docs/references/docs/applications/services/timesheets.md

@@ -0,0 +1,20 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/services/timesheets.html"
+---
+
+:nosearch:
+:show-content:
+:hide-page-toc:
+:show-toc:
+# 
+# Timesheets
+
+.. seealso::
+   - [Odoo Tutorials: Project and Timesheets
+     ](https://www.odoo.com/slides/project-and-timesheets-21)
+
+.. toctree::
+   :titlesonly:
+
+   timesheets/overview

package/payload/skills/odoo18-docs/references/docs/applications/services.md

@@ -0,0 +1,17 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/services.html"
+---
+
+:nosearch:
+# 
+# Services
+
+
+.. toctree::
+
+    services/project
+    services/timesheets
+    services/planning
+    services/field_service
+    services/helpdesk

package/payload/skills/odoo18-docs/references/docs/applications/studio/approval_rules.md

@@ -0,0 +1,95 @@
+---
+title: "Approval rules"
+source_url: "https://docs.odoo.sbggai.top/applications/studio/approval_rules.html"
+---
+
+==============
+# Approval rules
+
+Approval rules are used to automate approval processes for actions. They allow you to define
+the criteria for when an approval is required before an action can be performed using a button.
+
+# Configuration
+
+To add approval rules with Studio, proceed as follows:
+
+#. :ref:`Open Studio <studio/access>` and switch to the required :doc:`view <views>`.
+#. Select the button to which the rule should be applied.
+#. Click :icon:`fa-plus` :guilabel:`Add an approval step` in the :icon:`fa-server`
+   :guilabel:`Properties` tab.
+#. Specify which users are responsible for approving the action by using one of the following fields
+   or both:
+
+    - :guilabel:`Approvers` to specify one or several users;
+    - :guilabel:`Approver Group` to specify one user group.
+
+      > **note**:
+>          An activity is created for all users set as :guilabel:`Approvers` when their approval is
+         requested.
+
+#. (*optional*) Select the :guilabel:`Users to Notify` via an internal note when the action is
+   approved or rejected.
+#. (*optional*) Add a :guilabel:`Description` to be displayed on the button.
+
+> **tip**:
+>    You can specify under which condition(s) an approval step should be applied by clicking the
+   :icon:`fa-filter` (:guilabel:`filter`) icon next to the :guilabel:`Approvers` field.
+
+To add another approval step, click :icon:`fa-plus` :guilabel:`Add an approval step`. When there are
+multiple steps, you can:
+
+- Enable :guilabel:`Exclusive Approval` on any step so that a user who approves a step cannot
+  approve another step for the same record.
+- Change the :guilabel:`Approval Order` of the steps by selecting a number, `1` being the first
+  step, `2` the second step, and so on. A user responsible for a higher step can approve/reject
+  previous step(s) unless :guilabel:`Exclusive Approval` is selected.
+
+Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the :guilabel:`Approvers` field to
+remove an approval step.
+
+> **tip**:
+>    You can create :ref:`user groups <access-rights/groups>` specifically for approvals.
+
+.. _approval-rules/use:
+
+# Use
+
+Once an approval rule has been defined for a button, a **user avatar** icon is displayed next to the
+button's label for each approval step. Clicking an icon reveals the step(s).
+
+.. image:: approval_rules/approval-button.png
+   :alt: Confirm button with two approval steps
+
+> **note**:
+>    If an unauthorized user clicks the button, an error message is displayed and an activity is
+   created for the users specified in the :guilabel:`Approvers` field, if any.
+
+Authorized users can:
+
+- Perform the action directly by clicking the button if it is the last/only approval step.
+- Approve the action and let another user perform it - or move it to the next approval step - by
+  clicking the **user avatar** icon next to the button's label, then clicking the :icon:`fa-check`
+  (:guilabel:`approve`).
+- Reject the action by clicking the **user avatar** icon next to the button's label and then the
+  :icon:`fa-times` (:guilabel:`reject`) button.
+- (only for users selected under the :guilabel:`Approvers` field) Delegate their approval rights to
+  one or several users for **all records** by:
+
+  - Clicking the :icon:`oi-view-kanban` (:guilabel:`kanban view`) icon and then
+    :guilabel:`Delegate`.
+  - Selecting one or several :guilabel:`Approvers`, :guilabel:`Until` when they will have approval
+    rights (forever if left empty), and, optionally, the user(s) who should be notified via an
+    internal note using the :guilabel:`Notify to` field.
+
+    .. image:: approval_rules/delegate-dialog.png
+       :alt: Delegate to dialog
+
+> **tip**:
+>    - A user who approves/rejects an action can revoke their decision by clicking the **user avatar**
+     icon next to the button's label and then the :icon:`fa-undo` (:guilabel:`revoke`) button. They
+     can also revoke the decision of other users for steps with a lower :guilabel:`Approval Order`
+     unless :guilabel:`Exclusive Approval` is enabled.
+   - Approvals are tracked in the record's chatter. An approval entry is also created every time
+     a Studio approval-related action is performed. To access approval entries, :doc:`activate the
+     developer mode </applications/general/developer_mode>` and go to :menuselection:`Settings -->
+     Technical --> Studio Approval Entries`.