SmartERP Documentation An Ashewa Technology Solutions Platform

Signer Roles, Approval Order & Multi-Party Signoff

Configuring sequential vs parallel signing workflows, CC copy recipients, and executive sign-off hierarchies.

1. Overview & Business Value#

Enterprise agreements frequently require multi-party sequential sign-off (e.g., Vendor $\rightarrow$ Procurement Manager $\rightarrow$ Chief Executive Officer).

Module map showing dependencies between SmartERP Supply Chain Core, Tenders, Store Vouchers, Landed Costs, and WMS.
SmartERP Supply Chain and Sourcing architectural module map.

SmartERP Application Interface and Dashboard

1. Sequential Routing Logic#

When Sequential Signing Order is enabled:

  • Step 1: Document is routed to Signer 1.
  • Step 2: Upon completion by Signer 1, the system automatically emails Signer 2 with the partially executed PDF.
  • Step 3: Once all parties have signed, all participants and CC recipients receive the fully certified document and tamper-evident audit report.

2. Prerequisites & Access Permissions#

  • Required Modules: smarterp_sign, base, web
  • Security Group: Internal User (Technical ID: base.group_user)
  • Master Data Dependencies: Established corporate settings, defined role permissions, and active records.

3. Step-by-Step UI Execution & Verification#

Step 1: Navigating to the Module Interface#

  1. Access your SmartERP instance at https://smarterp.et/odoo.
  2. Open the main App Switcher and select the operational application.
  3. Select the target view or configuration form.

Step 2: Executing Transactional Operations#

  1. Fill in required parameters according to institutional procedures.
  2. Validate entries and confirm execution.
  3. Review updated record state in the chatter audit trail.

4. Advanced Configuration Points#

  • Automated Tasks (Crons): Dedicated background crons manage recurring tasks and state transitions.
  • Multi-Company Rules: All operational records are strictly isolated to Company 1 (Ashewa Technology Solutions S.C.).

5. Comprehensive Troubleshooting Matrix#

Symptom / ErrorProbable Root CauseResolution Action
Access Rights Error: Operation not allowedUser lacks required operational permissions.Assign user to the designated security group under Settings → Users.
Document state locked or read-onlyTransaction is in validated or closed state.Reopen document if permitted or contact designated manager.
Last updated: 2026-11-15