OperationsP2Reference

Documents & Approvals

Full nameRestaurant Organization Documents and Approvals Micro ERP

Requested files, versions, review decisions and approved records need a common history.

Application configurations3

Extension mappings6

LifecycleReference

About this erp

Purpose and scope

Requested files, versions, review decisions and approved records need a common history.

Source: ERP_Full_Hierarchy_Catalogue.html
Family: Documents and approvals
Family ID: documents
Configuration scope: Shared business operations
Standalone scope: Own document categories, parties, reviewers, access roles. Run organization document requests, versioned uploads, reviewer decisions, approved records and templates. Maintain record history and role permissions.
Core records: Document categories, parties, reviewers, access roles
ERP connections: Customer records, projects, finance, operations
Primary workflow: Organization document requests → Versioned uploads → Reviewer decisions → Approved records and templates
Readiness: Source-defined reference configuration; runtime unverified.

AI brief

Written by Claude from this ERP's record. Check the details before you rely on them.

Connected catalog

Follow each relationship to its full catalog record.

3 linked records

Full nameRestaurant Document Submission App

Upload requested documents and track review status.

Full nameRestaurant Document Reviewer App

Review document versions, request corrections and approve final records.

Full nameRestaurant Document Administrator App

Manage versions, access groups and approved document templates.