01
Tenant isolation
Use at least two organisations and prove that records, search, reports and commands never cross the boundary.
Preparing public route
Preparing public route
Implementation method
The current implementation path is intentionally narrow: understand one customer workflow, configure the organisation and permissions, migrate the required records, validate the released CRM end to end and expand only after acceptance.
Step 1
Document the users, companies, branches, records, handoffs, decisions, exceptions and evidence required for one customer workflow.
Step 2
Create the organisation, primary company, branch, user accounts, verified email path and active operating context in the secure ERP application.
Step 3
Clean and import only the master data and CRM records required by the pilot. Invalid rows are isolated so valid rows can continue safely.
Step 4
Grant only the actions each role needs and verify denied paths as deliberately as successful ones.
The current release does not claim a generic multi-level approval designer or delegated approval chains.
Step 5
Acceptance sequence
Capture or import a lead
Apply ownership, source, campaign, tags and scoring
Qualify the lead and resolve duplicate evidence
Convert exactly once into partner, contact and opportunity records
Schedule activities and progress the opportunity
Request a governed command when approval is required
Decide the request with version and separation-of-duties checks
Inspect reports, notifications, audit history and mobile behaviour
Step 6
Use at least two organisations and prove that records, search, reports and commands never cross the boundary.
Use a restricted user to verify hidden controls and rejected direct API mutations.
Confirm supported CRM views and mutations on responsive web, Android and iOS export paths.
Exercise invalid input, unavailable providers, retries, rate limits and safe error messages.
Run tests, lint, TypeScript, production builds, database checks and deployment smoke before promotion.
Record acceptance results, known limitations, production configuration and rollback steps.
Step 7
Promote only the workflow that passed acceptance. Monitor data quality, permission usage, failed jobs, provider delivery and the questions users still need answered.
Roadmap boundary
Accounting, Procurement, Sales, Stock, Manufacturing, Projects, Assets, Point of Sale, Quality, Support and HR & Payroll remain roadmap scope.
They are not added to an implementation plan as available modules until each one passes its own end-to-end release gate.
Next step
The strongest next step is a narrow scenario with named users, realistic records, explicit denials and measurable acceptance criteria.