Who can use this
- Admins and setup owners coordinating the rollout.
- Users completing personal connections after shared systems are ready.
- Spectators or managers who need limited access to meetings or reporting.
Before you start
- Decide who owns Ergo account setup before inviting the broader team.
- Confirm whether you are setting up shared systems, personal connections, or limited access.
- Confirm whether you are a user, admin, super admin, or spectator.
- Keep gated areas such as CRM fields, field mapping, pricing, reporting, and organization defaults with the right admin owner.
Steps
- Complete shared setup first: CRM connection, field mapping, pipeline stages, company details, meeting-title phrases, collaboration tools, notetaker defaults, email templates, and reporting or pricing setup when enabled.
- Then complete personal setup: email/calendar connection, notetaker or desktop capture path, collaboration access, and any sync-from-admin step that applies to the user.
- Use Setup by role when someone only needs the part of the setup path they own.
- Verify one controlled workflow before broad rollout: one meeting or call, dashboard visibility, expected processing state, and CRM, reporting, or draft output when configured.
What to expect
- The setup path can differ by role, spectator status, feature availability, and reporting access.
- Admin-owned setup can unlock source context for users, but each user may still need personal email/calendar, notetaker, or collaboration access.
- Downstream outputs depend on connected sources, permissions, field mapping, filters, and processing state.
Common issues
- A required source is disconnected, stale, or not matched to the right account.
- A user expects to change an admin-owned setting.
- A spectator or shared-link viewer expects broader access than their scope grants.
- A filter, permission, or setting hides the expected result.
- A meeting is detected but the notetaker, desktop capture, processing, or downstream output did not complete.