Deprecated: Function get_magic_quotes_gpc() is deprecated in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 99

Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 619

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1169

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176
Configure GoToMeeting user provisioning - Google Workspace Admin Help
Nothing Special   »   [go: up one dir, main page]

Configure GoToMeeting user provisioning

You can set up automated user provisioning (autoprovisioning) so that any changes you make to user accounts in Google Workspace are automatically synced with this third-party app.

Automated user provisioning operates only on active, suspended, or deleted users. It doesn't include archived users.

Before you begin

Before you can set up automated user provisioning, you need to set up SSO for GoToMeeting. For the steps, go to GoToMeeting cloud app.

Set up automated user provisioning

Expand section  |  Collapse all

Set up autoprovisioning for app

You must be signed in as a super administrator for this task.

  1. Sign in with a super administrator account to the Google Admin console.

    If you aren’t using a super administrator account, you can’t complete these steps.

  2. Click GoToMeeting.
  3. For Autoprovisioning, click Configure autoprovisioning.
  4. Click Authorize. You're asked for an authorization by GoToMeeting. If you haven't signed in to your GoToMeeting administrator account before clicking Authorize, you're prompted to sign in.
    Important: You might have to reauthorize if the admin password for GoToMeeting changes. Changing the admin password causes the original authorization to be revoked.
  5. For Endpoint URL, replace {AccountKey} with your GoToMeeting AccountKey. data-outlined="false">Note: In your signed-in GoToMeeting Admin Center URL, the AccountKey is the number that appears after #accounts/ in the URL.
  6. data-outlined="false">Click Continue.
  7. For App attributes, verify that all mandatory attributes—those marked with an asterisk (*)—are mapped to Google directory attributes. If not, click the Down arrow  and map them to their appropriate attribute.

  8. Click Continue.
  9. (Optional) To limit autoprovisioning to specific groups of users:
    1. For Search groups, enter one or more letters of the group name, select the group name, and choose a scope.
    2. Add any additional groups.
    3. (Optional) To remove a group, click Remove .

      If a group has users from a secondary domain or from outside of your organization, those users are not provisioned.

  10. Click Continue.
  11. Decide how long users have access to the app after the app is turned off for them or their Google Workspace account is suspended or deleted. You can decide to suspend their account in GoToMeeting. You can set the time frame individually for each option and choose within 24 hours or after one, 7, or 21 days.
    1. Choose options for each of these settings, as needed:
      • When an app is turned off for a user
      • When a user is suspended from Google
      • When a user is deleted from Google
    2. Click Finish.
  12. Turn on Autoprovisioning.
  13. Click Turn on to confirm.

Edit provisioning information

Expand section  |  Collapse all & go to top

Edit user groups subject to autoprovisioning

If you turned on the app for certain organizational units, only users in the added groups who are also members of those organizational units are subject to autoprovisioning.

You must be signed in as a super administrator for this task.

  1. Sign in with a super administrator account to the Google Admin console.

    If you aren’t using a super administrator account, you can’t complete these steps.

  2. Click GoToMeeting.
  3. Click Autoprovisioning.
  4. For Provisioning scope, click Edit.
  5. For Search groups, enter one or more letters of the group name, select the group name, and choose a scope.

  6. Add any additional groups.
  7. (Optional) To remove a group, click Remove .

    If a group has users from a secondary domain or from outside of your organization, those users are not provisioned.

  8. Click Update.
Edit deprovisioning time frames

You must be signed in as a super administrator for this task.

  1. Sign in with a super administrator account to the Google Admin console.

    If you aren’t using a super administrator account, you can’t complete these steps.

  2. Click GoToMeeting.
  3. Click Autoprovisioning.
  4. For Deprovisioning, click Edit.
  5. Decide how long users have access to the app after the app is turned off for them or their Google Workspace account is suspended or deleted. You can suspend their account in GoToMeeting. You can set the time frame individually for each option and choose within 24 hours or after one, 7, or 21 days.
    Choose options for each of these settings, as needed:
    • When an app is turned off for a user
    • When a user is suspended from Google
    • When a user is deleted from Google
  6. Click Update.

Turn off autoprovisioning & delete configuration information

Expand section  |  Collapse all & go to top

You can turn off autoprovisioning for the app without losing configuration information. Or, you can turn off autoprovisioning and remove all configuration information.

Turn off autoprovisioning

You must be signed in as a super administrator for this task.

To turn off autoprovisioning for the app and keep the configuration information:

  1. Sign in with a super administrator account to the Google Admin console.

    If you aren’t using a super administrator account, you can’t complete these steps.

  2. Click GoToMeeting.
  3. Choose an option:
    • Turn off Autoprovisioning.
    •  Click Autoprovisioningand thenStatusand thenTurn off.
  4. Click Turn off to confirm.
Turn off autoprovisioning & delete configuration information
You must be signed in as a super administrator for this task.
  1. Sign in with a super administrator account to the Google Admin console.

    If you aren’t using a super administrator account, you can’t complete these steps.

  2. Click GoToMeeting.
  3. Click Autoprovisioning.
  4. For Delete configuration, click Delete.
  5. Click Delete to turn off autoprovisioning and remove all the configuration information.
    Existing users will not be removed from GoToMeeting and can still use the app.

Review usage information

  • After you turn on autoprovisioning, you can review usage information. For details, go to Monitor automated user provisioning.
  • You can review the following usage information for the last 30 days:

Admin log event

Description

Create User By Auto Provisioning

Users created by autoprovisioning

Update Auto Provisioned User

Users updated by autoprovisioning

Suspend Auto Provisioned User

Users suspended by autoprovisioning

Unsuspend Auto Provisioned User Users reactivated by autoprovisioning
Hard Delete Auto Provisioned User Users deleted by autoprovisioning

Failures

Failed requests

If autoprovisioning stops working...

Sometimes, due to account inactivity or if the admin password for GoToMeeting changes, autoprovisioning stops working. To continue syncing user accounts in Google Workspace to the app, you need to reauthorize autoprovisioning.

You must be signed in as a super administrator for this task.

  1. Sign in with a super administrator account to the Google Admin console.

    If you aren’t using a super administrator account, you can’t complete these steps.

  2. Click GoToMeeting.
  3. Click Autoprovisioning.
  4. For App authorization, click Reauthorize.
  5. Click Re-authorize.

For details on other reasons why autoprovisioning might stop working, refer to the app’s documentation.


Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Main menu
13426007101547829697
true
Search Help Center
false
true
true
true
true
true
73010
false
false
false
false