GoTo Connect

Connect GoTo Connect to collect communications platforms evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In GoTo Connect:

   1. In the GoTo Developer Center, choose OAuth Clients from the menu and select Create a client (or Create a New Client if clients already exist).
   2. On the Details page enter a client name and at least one Redirect URI, then click Next.
   3. Select the products and functions the client may use, then click Save. On the credentials page copy the client ID and the client secret (GoTo displays the secret only once), check I have stored the client secret, and click Done.
   4. In a browser, open https://authentication.logmeininc.com/oauth/authorize?client_id=\{clientID\}&response_type=code&redirect_uri=\{redirectUri\}, sign in as a GoTo Connect admin user, and click Allow.
   5. Copy the authorization code from the redirect URI and POST it with grant_type=authorization_code to https://authentication.logmeininc.com/oauth/token. Paste the returned access_token into Safeguard.

   Where to find the other values:

   • Account ID: Not confirmed from a fetched page. The token response does not include it (it returns only access_token, token_type, refresh_token, expires_in, scope and principal).

   GoTo Connect shows the secret only once, so copy it before you leave the page.

   GoTo Connect's public documentation does not cover every step.

   one_time_display refers to the OAuth client secret. GoTo access tokens expire (expires_in) and must be refreshed with the refresh_token. The exact product/function labels that map to the identity: scope, and where the GoTo Admin UI shows the Account ID, were not confirmed.

   Source: developer.goto.com, developer.goto.com, checked 2026-10-07.

   The permissions Safeguard needs: identity:, admin user.

2. On Compliance › Connectors, open GoTo Connect, click Connect, choose API token and fill in:

   Field	What to enter
   Access token	Required. Stored encrypted and never shown again.
   Account ID	Required. For example: 1234567890123456789

3. Click Connect with token.

Frameworks

Safeguard's automated tests read GoTo Connect and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Communications Platforms connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks