{"id":9383,"date":"2026-08-27T11:38:47","date_gmt":"2026-08-27T08:38:47","guid":{"rendered":"https:\/\/machinser.com\/?p=9383"},"modified":"2026-08-27T13:33:12","modified_gmt":"2026-08-27T10:33:12","slug":"how-to-configure-approval-rules-in-odoo-19-using-studio","status":"publish","type":"post","link":"https:\/\/machinser.com\/ar\/how-to-configure-approval-rules-in-odoo-19-using-studio\/","title":{"rendered":"How to Configure Approval Rules in Odoo 19 Using Studio"},"content":{"rendered":"

In many businesses, certain operations should not be completed by every user without authorization. For example, a sales quotation may need to be reviewed by a sales manager before it can be confirmed, or a sensitive transaction may require approval from a specific department.<\/p>\n

Instead of handling these approvals through emails, messages, or manual follow-ups, Odoo 19 Studio<\/strong> allows approval controls to be added directly to existing buttons and workflows.<\/p>\n

With Studio approval rules, you can decide who is allowed to authorize an action, whether approval should come from a particular user or user group, and whether additional approval steps are required before the action can be completed.<\/p>\n

This article explains how to configure such an approval workflow in Odoo 19 using a sales order confirmation as an example.<\/p>\n

What Are Approval Rules in Odoo 19?<\/strong><\/h2>\n

Approval rules allow an organization to place an authorization layer on top of an existing Odoo operation.<\/p>\n

For instance, suppose sales employees are allowed to create quotations, but management wants every quotation to be reviewed before it becomes a confirmed sales order.<\/p>\n

Instead of restricting access to the entire Sales Order form, an approval rule can be attached specifically to the Confirm<\/strong> button.<\/p>\n

This provides a more controlled workflow:<\/p>\n

Sales User \u2192 Creates Quotation \u2192 Requests Confirmation \u2192 Approver Reviews \u2192 Order Confirmed<\/strong><\/p>\n

The same concept can be applied to different buttons and business operations depending on the requirements of the organization.<\/p>\n

Odoo 19 Studio also supports multiple approval stages, allowing businesses to create workflows where more than one person or group must authorize an operation.<\/p>\n

Why Use Approval Rules?<\/strong><\/h2>\n

Approval rules can be useful when a company wants tighter control over important transactions without introducing a complicated custom development process.<\/p>\n

Some common scenarios include:<\/p>\n

    \n
  • Sales orders requiring management approval<\/li>\n
  • Purchase transactions requiring department authorization<\/li>\n
  • Discount approvals<\/li>\n
  • Expense approvals<\/li>\n
  • Important record status changes<\/li>\n
  • Financial or operational actions requiring management review<\/li>\n
  • Multi-level authorization workflows<\/li>\n<\/ul>\n

    The main advantage is that the approval requirement becomes part of the Odoo workflow itself rather than being managed separately.<\/p>\n

    Step 1: Open the Sales Order Form<\/strong><\/h3>\n

    First, open the Sales<\/strong> application and create or open a quotation.<\/p>\n

    The quotation form contains the Confirm<\/strong> button that normally changes the quotation into a confirmed sales order.<\/p>\n

    To configure an approval rule for this action, activate Studio<\/strong> from the Odoo interface.<\/p>\n

    \"\"<\/p>\n

    Step 2: Select the Button That Requires Approval
    \n<\/strong><\/h3>\n

    Once Studio is active, click the Confirm<\/strong> button on the sales order form.<\/p>\n

    Odoo Studio will display configuration options for the selected button.<\/p>\n

    Look for the option related to configuring approval rules and choose:<\/p>\n

    Add an approval step<\/strong><\/p>\n

    This allows an approval layer to be attached to the selected button.<\/p>\n

    \"\"<\/p>\n

    Step 3: Define the Approver<\/strong><\/h3>\n

    After adding an approval step, Odoo provides options for deciding who should authorize the action.<\/p>\n

    Depending on the company’s workflow, the approval can be assigned to:<\/p>\n

      \n
    • A specific Odoo user<\/li>\n
    • A user group<\/li>\n<\/ul>\n

      For example, if all sales orders must be reviewed by the Sales Manager, the appropriate user or group can be selected as the approver.<\/p>\n

      This is particularly useful when the approval responsibility belongs to a department rather than one individual employee.<\/p>\n

      \"\"<\/p>\n

       <\/p>\n

      Step 4: Configure Notifications<\/strong><\/h3>\n

      The approval configuration can also be used to notify the relevant users when their approval is required.<\/p>\n

      This is useful in situations where the person responsible for approval may not be actively monitoring the transaction.<\/p>\n

      For example:<\/p>\n

      Salesperson creates quotation \u2192 Confirmation requested \u2192 Manager receives notification \u2192 Manager reviews quotation<\/strong><\/p>\n

      This keeps the approval process inside Odoo and reduces the need for manual communication.<\/p>\n

      \"\"<\/p>\n

       <\/p>\n

      Step 5: Add Additional Approval Levels<\/strong><\/h3>\n

      A business may require more than one person to authorize a transaction.<\/p>\n

      For example, a company could have the following approval structure:<\/p>\n

      Level 1:<\/strong> Sales Manager
      \nLevel 2:<\/strong> Finance Manager
      \nLevel 3:<\/strong> General Manager<\/p>\n

      Odoo Studio allows additional approval steps to be added to the same button.<\/p>\n

      Use the option to add another approval step and configure the next responsible user or group.<\/p>\n

      You can therefore create a sequential approval workflow without creating a separate custom approval application.<\/p>\n

      \"\"<\/p>\n

       <\/p>\n

      Step 6: Save the Approval Configuration<\/strong><\/h3>\n

      After defining the required approvers and approval levels, save the Studio customization.<\/p>\n

      It is recommended to test the configuration with a normal user account rather than immediately testing with an administrator account.<\/p>\n

      This helps confirm that the approval restriction is actually being applied to users who are not authorized to perform the action directly.<\/p>\n

      \"Odoo<\/p>\n

      Step 7: Test the Workflow as a Normal User<\/strong><\/h3>\n

      Now log in using a user who is not configured as an approver.<\/p>\n

      Create a new quotation and enter the required sales information.<\/p>\n

      When the user attempts to click Confirm<\/strong>, Odoo will recognize that the action requires approval.<\/p>\n

      Instead of allowing the transaction to proceed immediately, the system will display the approval requirement.<\/p>\n

      This ensures that the configured authorization process is enforced at the point where the restricted action is attempted.<\/p>\n

      \"\"<\/p>\n

       <\/p>\n

      Step 8: Review the Approval Status<\/strong><\/h3>\n

      Odoo provides visibility into the approval process from the transaction itself.<\/p>\n

      An approval indicator can be used to inspect the current approval status and understand whether the required authorization has been completed.<\/p>\n

      This makes it easier for users to identify why an operation has not yet been completed.<\/p>\n

      Step 9: Open the Approval Details<\/strong><\/h3>\n

      Clicking the approval information allows users to see additional details about the configured approval step.<\/p>\n

      Depending on the configuration, this can show information such as:<\/p>\n

        \n
      • Approval responsibility<\/li>\n
      • Assigned approver<\/li>\n
      • Current approval status<\/li>\n
      • Approval stage<\/li>\n
      • Pending approvals<\/li>\n<\/ul>\n

        This provides better visibility into where the transaction currently stands.<\/p>\n

        \"\"<\/p>\n

         <\/p>\n

        Step 10: Approver Reviews the Request<\/strong><\/h3>\n

        The designated approver can now review the transaction before authorizing it.<\/p>\n

        For example, the Sales Manager may check:<\/p>\n

          \n
        • Customer information<\/li>\n
        • \u0645\u0646\u062a\u062c\u0627\u062a<\/li>\n
        • Quantities<\/li>\n
        • Pricing<\/li>\n
        • Discounts<\/li>\n
        • Payment terms<\/li>\n
        • Delivery information<\/li>\n<\/ul>\n

          After reviewing the transaction, the approver can complete the assigned approval.<\/p>\n

          Step 11: Track the Approval in the Chatter<\/strong><\/h3>\n

          Odoo’s chatter provides a useful audit trail for the approval process.<\/p>\n

          Once an approval has been completed, the related activity or approval information can be reflected in the chatter.<\/p>\n

          This gives users a historical view of the workflow and makes it easier to understand who participated in the authorization process.<\/p>\n

          \"\"<\/p>\n

           <\/p>\n

          Advantages of Using Studio Approval Rules<\/strong><\/h2>\n

          Using Studio for approval control provides several practical benefits.<\/p>\n

          1. No Custom Development<\/strong><\/h3>\n

          Approval rules can be configured through the Odoo Studio interface without writing custom Python code.<\/p>\n

          2. Better Transaction Control<\/strong><\/h3>\n

          Important operations can be protected from being completed without the required authorization.<\/p>\n

          3. Multiple Approval Levels<\/strong><\/h3>\n

          Businesses can establish sequential approval workflows involving multiple users or groups.<\/p>\n

          4. Improved Visibility<\/strong><\/h3>\n

          Users can see whether an action is waiting for approval and identify the relevant approval stage.<\/p>\n

          5. Centralized Workflow<\/strong><\/h3>\n

          The approval process remains inside Odoo instead of depending on external emails or informal communication.<\/p>\n

          6. Better Accountability<\/strong><\/h3>\n

          Approval activities provide greater visibility into who was responsible for reviewing an operation.<\/p>","protected":false},"excerpt":{"rendered":"

          In many businesses, certain operations should not be completed by every user without authorization. For example, a sales quotation may need to be reviewed by a sales manager before it can be confirmed, or a sensitive transaction may require approval from a specific department. Instead of handling these approvals through emails, messages, or manual follow-ups, […]<\/p>\n","protected":false},"author":4,"featured_media":9393,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[313,192],"tags":[260,317,258],"class_list":["post-9383","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-odoo-configuration","category-odoo-erp","tag-erp-customization","tag-erp-customization-erp-customization","tag-erp-implementation"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/machinser.com\/wp-content\/uploads\/2026\/08\/Odoo-studio.jpeg","_links":{"self":[{"href":"https:\/\/machinser.com\/ar\/wp-json\/wp\/v2\/posts\/9383","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/machinser.com\/ar\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/machinser.com\/ar\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/machinser.com\/ar\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/machinser.com\/ar\/wp-json\/wp\/v2\/comments?post=9383"}],"version-history":[{"count":3,"href":"https:\/\/machinser.com\/ar\/wp-json\/wp\/v2\/posts\/9383\/revisions"}],"predecessor-version":[{"id":9406,"href":"https:\/\/machinser.com\/ar\/wp-json\/wp\/v2\/posts\/9383\/revisions\/9406"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/machinser.com\/ar\/wp-json\/wp\/v2\/media\/9393"}],"wp:attachment":[{"href":"https:\/\/machinser.com\/ar\/wp-json\/wp\/v2\/media?parent=9383"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/machinser.com\/ar\/wp-json\/wp\/v2\/categories?post=9383"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/machinser.com\/ar\/wp-json\/wp\/v2\/tags?post=9383"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}