Troubleshoot Glass plugin connections

Overview

Early Access. For access information, see Request access to Glass.

Start with the account and message involved, not by disconnecting a plugin. A company restriction, a missing project grant, an expired plugin connection, and a website sign-in need different fixes.

Identify the Glass connection that needs attention

Before changing anything, note the app, exact message, affected chat or project, and whose account is involved. Check your own connection in personal plugin settings, or ask your Glass admin to check a company account in organization plugin settings.

For shared project access, review the account's Shared by, permissions, and status in the project's Plugins list. Follow project access review before granting broader access. A connected account does not establish that a project can use it for every action.

Resolve Glass plugin policy or approval blocks

Company policy or admin setup: If Glass says your company blocks the app or asks an admin to connect it, ask your Glass admin to review that plugin's company settings. Reconnecting your own account is not a substitute for company approval. Do not reset workspace setup to diagnose one person's problem.

Waiting for someone to approve access: Ask the person named in the request to review it in the affected chat. Check the account, actions, and project scope before approving. Use project plugin access review, not company-account disconnection, to resolve a missing project grant.

Finish or renew a Glass plugin connection

Not connected: Follow personal plugin connection setup. If Glass Desktop says Finish connecting in your browser, complete the provider authorization in the browser that opened.

Reconnect offered: Use Reconnect for the affected personal account and complete authorization. If it belongs to someone else, ask that owner to reconnect. For a company account, ask your Glass admin to use the affected account row's Reconnect when offered. Review the access request first: reconnecting from an approval card can also approve its waiting request.

Request expired: Distinguish an expired access request from an expired account connection. Ask Glass again for the task and review the new request; do not disconnect the account just because an old request expired.

Check provider permissions when connection succeeds

If a task still reports insufficient access after connection, review the account and permission involved before granting more. In a project, check whether you shared read-only access but requested a change. Read-only access and permission to make changes are different; choose the access needed for the task rather than automatically allowing every action.

Change read-only project access: Ask Glass in the affected chat to request permission for the specific change using the intended account. Ask the account owner to review and approve access for that project. Select Allow only after reviewing the account, proposed actions, and project scope. Keep the request unapproved if you do not want broader access.

For a provider permission error, check that you are using the intended account and follow the provider's message about the resource or action it rejected. Do not paste passwords, API keys, or client secrets into ordinary chat, or grant unrelated permissions just to test whether the error clears.

A website asking you to sign in inside the Glass browser is separate from the app's plugin connection. Do not disconnect an otherwise working plugin to fix website sign-in.

Check the website and account requested in the affected browser task. When Glass presents a sign-in request to you, use that request's fields or its Enter password securely action when offered, rather than posting credentials in ordinary chat. A request addressed to another account owner needs that owner's response.

If you imported logged-in sites, open the intended website in the affected browser task and check whether it actually accepts the sign-in. Import completion alone is not a test of website authentication. Do not infer website sign-in lifetime from how long you have been signed in to Glass, or assume a new workflow starts with a fresh browser profile.

Retry a Glass plugin list that did not load

If the plugin list cannot load, use Try again to retry the list request. A failed status read is not proof that an account was disconnected. If an API-key form reports that you are offline, restore your network connection before retrying. Follow the specific message instead of disconnecting, resetting workspace setup, or broadening permissions as a general repair.