Provide portal owners, brand assets, active project mappings, authorized client contacts, identity-provider settings, document-storage access, signature requirements, callback mappings and approved retention/notification policies.
Implementation
Configure identity, audiences and decision evidence before inviting clients.
Implementation phases
Phase 1 · Team and ERP.ai
Agree audiences
Identify portal owners, permitted projects, client roles and the required decision makers.
| Role | Screens |
|---|---|
| Portal Manager | 11 |
| Project Manager | 6 |
| Account Manager | 5 |
| Internal Collaborator | 1 |
| Client User — Approver | 3 |
| Client User — Collaborator | 2 |
| Client User — Viewer | 2 |
Role permissionsRoles and permissions →
Phase 2 · Team and ERP.ai
Configure connections
Set up approved identity, document-storage and source callback mappings without publishing private URLs.
Phase 3 · Team and ERP.ai
Verify collaboration
Exercise invitation, protected download, explicit acknowledgment, requested changes and callback reconciliation with scoped test users.
| Role | Screens |
|---|---|
| Portal Manager | 11 |
| Project Manager | 6 |
| Account Manager | 5 |
| Internal Collaborator | 1 |
| Client User — Approver | 3 |
| Client User — Collaborator | 2 |
| Client User — Viewer | 2 |
Role permissionsRoles and permissions →
Phase 4 · Team and ERP.ai
Invite clients
Review branding and notification content, then activate the approved audience and monitor failed deliveries.
Version live branding and approval evidence. Audience changes recheck open requests, existing links and notification recipients. Preserve prior decisions; a new review round uses a new request revision. Revoke memberships and tokens promptly, retain historical audit evidence, and repeat direct-API and download checks after changes.
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.