Summary and recommendation
GoTo Meeting user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
GoTo Meeting uses a fixed three-role model - Admin, Manager, and Member (Organizer) - managed entirely through the Admin Center at app.goto.com → Admin → Users. Permissions are role-level only; there are no per-user overrides or custom role creation available in GoTo Meeting standalone.
Every app in this category carries provisioning tradeoffs, and GoTo Meeting's key constraint is that native SCIM has been deprecated, leaving manual workflows or a migration to GoToConnect as the only supported paths.
Quick facts
| Admin console path | app.goto.com → Admin (left nav) → Users |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Business/Enterprise |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Full account management: add/remove/deactivate users, assign roles, manage billing, configure SSO, view reports, manage all meetings and recordings. | Cannot downgrade their own Admin role without another Admin present on the account. | All paid plans | Consumes an organizer seat | Admin role is account-wide; there is no scoped or department-level admin in GoTo Meeting standalone. |
| Manager | Can manage a subset of users assigned to them: add users, edit user settings, view usage reports for their group. Cannot access billing or account-level settings. | Cannot manage billing, configure SSO, or manage users outside their assigned group. | Business plan or higher | Consumes an organizer seat | Manager role availability and exact scope may vary; verify in Admin Center as GoTo has updated role definitions across product updates. |
| Member (Organizer) | Can schedule and host meetings, manage their own recordings, invite participants. No admin capabilities. | Cannot manage other users, access admin reports, or change account settings. | All paid plans | Consumes one organizer seat (licensed seat) | Each organizer seat is a paid license. Participants joining meetings do not require a seat or account. |
Permission model
- Model type: role-based
- Description: GoTo Meeting uses a fixed role-based model with predefined roles (Admin, Manager, Member/Organizer). Permissions are tied to roles and cannot be individually customized per user within GoTo Meeting standalone.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Role-level only; no per-user permission overrides or custom role creation available in GoTo Meeting standalone.
How to add users
- Sign in to app.goto.com with an Admin account.
- Navigate to Admin (left sidebar) → Users.
- Click 'Add Users' (or 'Invite Users') button.
- Enter the user's email address.
- Assign a role (Admin, Manager, or Member).
- Assign a product seat (GoTo Meeting organizer license).
- Click 'Send Invite'. The user receives an email invitation to activate their account.
Required fields: Email address, Role assignment, Product/seat assignment
Watch out for:
- Users must accept the email invitation before they appear as active in the Admin Center.
- Invitations expire; if a user does not accept, the admin must resend the invite.
- Adding a user immediately consumes an organizer seat and may trigger a billing change depending on plan.
- First and last name are not required at invite time; users set them during account activation.
- GoTo Meeting does not support domain-based auto-provisioning (domain whitelisting) natively.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Yes | Admin → Users → Add Users → Import via CSV (download template from the same screen) |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | SAML SSO is available on Professional and Business plans. Automated provisioning via SCIM is not natively available in GoTo Meeting standalone; GoToConnect (which bundles GoTo Meeting) supports SCIM provisioning via Okta. |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: GoTo Meeting's Admin Center supports both deactivating and deleting users. Deactivating suspends access while retaining the user record and associated data. Deleting permanently removes the user account. Deletion is irreversible. Some account configurations may only surface 'Deactivate' depending on plan or account type.
- Sign in to app.goto.com with an Admin account.
- Navigate to Admin → Users.
- Locate the user using search or the user list.
- Click the user's name or the action menu (three dots / kebab menu) next to their name.
- Select 'Deactivate User' (or 'Delete User' for permanent removal).
- Confirm the action in the dialog prompt.
| Data impact | Behavior |
|---|---|
| Owned records | Recordings owned by the deactivated/deleted user remain accessible in the account's recording storage for admins to retrieve, but the user loses access. Upon deletion, data retention depends on account storage settings. |
| Shared content | Scheduled meetings hosted by the removed user are cancelled or become inaccessible to participants. Recurring meetings are not automatically reassigned. |
| Integrations | Calendar integrations (Google Calendar, Outlook) linked to the removed user's account are disconnected. Any meeting links shared externally will no longer be valid. |
| License freed | Deactivating or deleting a user frees the organizer seat, making it available for reassignment. Billing adjustment timing depends on the billing cycle. |
Watch out for:
- Recurring meetings scheduled by a deleted user are not automatically transferred to another organizer; attendees will not receive cancellation notices unless manually handled.
- Recordings may be lost if not downloaded or transferred before account deletion, depending on storage configuration.
- Deactivated users still appear in the Admin Center user list with a 'Deactivated' status; they do not count against active seat usage.
- There is no bulk deactivation UI; each user must be deactivated individually through the Admin Center.
- Azure AD (Entra ID) automated provisioning/deprovisioning for GoTo Meeting standalone has been deprecated; admins relying on it must switch to manual or Okta-based workflows.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Organizer Seat (Professional) | Host meetings up to 150 participants, unlimited meeting duration, cloud recording, screen sharing, drawing tools. | $12/organizer/mo (annual) or $14/organizer/mo (monthly) |
| Organizer Seat (Business) | Host meetings up to 250 participants, all Professional features plus transcription, slide conversion, and Smart Assistant features. | $16/organizer/mo (annual) or $19/organizer/mo (monthly) |
| Organizer Seat (Enterprise) | Host meetings up to 3,000 participants, all Business features plus dedicated customer success and custom onboarding. | Custom pricing |
- Where to check usage: app.goto.com → Admin → Reports → Usage Reports (shows active organizers, meeting counts, and seat utilization by user)
- How to identify unused seats: Admin → Reports → Usage Reports; filter by date range to identify organizers with zero meetings hosted. No automated 'unused seat' alert exists natively; admins must manually review the report.
- Billing notes: Each invited (active) organizer consumes a paid seat regardless of whether they host meetings. Deactivating a user frees the seat but billing adjustment may not apply until the next billing cycle. Participant attendees do not require licenses. Free plan is limited to 3 participants and 40-minute sessions with no admin management features.
The cost of manual management
Each organizer seat is a paid license the moment an invite is accepted, regardless of whether that user ever hosts a meeting. There is no automated unused-seat alert; admins must manually pull Usage Reports (Admin → Reports → Usage Reports) and filter by date range to identify zero-activity organizers.
There is no bulk deactivation UI - every user must be deactivated individually, which compounds the overhead for any team managing more than a handful of seats. Billing adjustments for freed seats may not apply until the next billing cycle after deactivation.
What IT admins are saying
The loudest recurring complaint is the deprecation of Azure AD (Entra ID) automated provisioning for GoTo Meeting standalone, which forces teams that relied on it into fully manual workflows or a platform migration to GoToConnect.
Admins also flag that recurring meetings are not automatically reassigned or cancelled when an organizer is removed - broken meeting links reach attendees with no system-generated notice.
Invitation expiry is a quieter but consistent friction point: pending invites are only discoverable by auditing the full user list, and there is no proactive alert when an invite lapses.
Common complaints:
- Azure AD (Entra ID) automated provisioning for GoTo Meeting standalone has been deprecated, forcing admins to switch to manual user management or migrate to GoToConnect for SCIM support.
- No bulk deactivation option in the Admin Center; admins must deactivate users one at a time, which is time-consuming for large organizations.
- Recurring meetings are not automatically reassigned or cancelled when a user is removed, causing broken meeting links for attendees.
- Organizer seats are billed even for users who never host meetings, with no automated notification for unused seats.
- Invitation expiry is not prominently communicated; admins discover pending invites only by auditing the user list.
- SCIM provisioning is not available natively in GoTo Meeting standalone; it requires upgrading to or migrating to GoToConnect.
The decision
GoTo Meeting standalone is a practical fit for smaller teams comfortable with manual provisioning and a straightforward role model. Organizations that need automated lifecycle management for every app in their stack - onboarding, offboarding, and license reclamation - will hit the ceiling quickly: no SCIM, no bulk actions, no unused-seat alerts.
Teams already in the GoTo ecosystem should evaluate GoToConnect, which restores SCIM support via Okta and covers the same meeting functionality under a broader license.
Bottom line
GoTo Meeting's Admin Center is functional for day-to-day user management but was not designed for scale.
The deprecation of native SCIM and Entra ID provisioning means any team beyond a small headcount is operating without an automated safety net - seats accumulate, offboarding is manual step-by-step, and meeting continuity after user removal requires deliberate intervention.
Teams that need lifecycle automation across every app in their environment should treat the GoToConnect migration path as a prerequisite, not an upgrade option.
Automate GoTo Meeting workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
