Bring your current business identifiers, responsible users, policy decisions, representative documents and authorized connection details. Keep credentials in the designated secure configuration rather than in a spreadsheet, prompt or source repository.
Implementation
Configure the system around your business records and responsibilities.
Implementation phases
Phase 1 · Team and ERP.ai
Define the operating scope
Use Proto to select the business entities, core processes and responsible roles.
| Role | Screens |
|---|---|
| Owner / Admin | 12 |
| Bookkeeper | 12 |
| Assistant | 6 |
| Viewer | 4 |
| Client | 1 |
Role permissionsRoles and permissions →
Phase 2 · Team and ERP.ai
Prepare existing data
Resolve identities and preserve original document references, dates and opening positions.
Phase 3 · Team and ERP.ai
Configure the workflow
Apply permissions, approval rules, calculated fields and any required integrations.
Phase 4 · Team and ERP.ai
Verify the result
Exercise ordinary work, denied access, a correction, a conflicting edit and a repeated command.
Phase 5 · Team and ERP.ai
Invite the team
Begin with the agreed business scope and reconcile the first operating cycle before extending it.
Use Proto to propose a change on a reviewed configuration branch. Check its effect on existing records, role boundaries, automation and reports before release. Preserve the previous source revision and the migration decisions needed to explain historical work.
1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.