UrbanLoop Signage · IT help
Connect Google content with your IT team.
Resolve organization-policy blocks while keeping Google account access, app approval and source sharing clear.
Can UrbanLoop use a Google Workspace account? Yes. The connected account needs access to the source, and your Workspace administrator may need to approve the app under your organization’s policy.
Identify the account and the blocked connection.
Your UrbanLoop sign-in and the Google account connected to a content source are separate. Start in the management app with the Google account that should supply the presentation, calendar or folder. Confirm that account can open the source in Google itself.
If Google says an administrator has blocked access, record the management platform and app version, the displayed app name and the OAuth client ID from its error details when available. Share those details with your Workspace administrator. Do not send the full sign-in URL, authorization codes or tokens.
An empty picker after a successful connection can be a source-sharing issue instead of an app-policy block. Use the matching Slides, Calendar or Drive folder guide to check that part.
Ask your Workspace administrator to review app access.
An administrator with the appropriate privileges can review this in Google Admin:
- Open Security → Access and data control → API controls → Manage App Access.
- Find the matching configured app, or use Configure new app and search by app name or OAuth client ID. Confirm the identity rather than choosing a similar name.
- Select the organizational units that need access. Review the requested services and choose the access level appropriate to your policy. Specific Google data supports scope-level approval; Trusted permits broader access.
- Review and finish the configuration, then retry the connection with an affected user.
Education accounts can have additional restrictions. Follow Google’s current app-access instructions for the exact controls available in your tenant. UrbanLoop does not require you to turn off third-party app controls for your entire organization.
Use the OAuth identity for the app you are running.
The web management app and native management apps can use different Google OAuth clients. The Google consent or error details and your administrator’s app record identify the client involved. Check every management platform your team actually uses.
An Apple bundle identifier is not a Google OAuth client ID. Older EZ Plus help mentions bnm.eztv-phone. That identifies an Apple app for deployment; do not paste it into an OAuth client-ID field and assume Google access is configured.
If the identity is unclear, ask UrbanLoop to confirm it with the platform, app version and displayed client ID before approval. Installed legacy versions can differ from current builds. Recheck the match when upgrading rather than removing all existing app rules at once.
Review the permissions for the content workflow.
The current management connection requests these permissions. Your administrator should compare them with the actual consent request and installed version:
| Permission | Why it appears |
|---|---|
email | Identify the connected Google account. |
drive.file | Access files selected or used through the app’s file-selection flow. This is not a request for unrestricted access to every Drive file. |
presentations.readonly | Read Google Slides presentation content. |
calendar.readonly and calendar.events.readonly | Read calendar information and events for calendar displays. |
Several permissions can appear together because the same connection supports Slides, Calendar and Drive workflows. Approving an OAuth app does not give its user access to a file they could not otherwise open.
Do not make private presentations or calendars public to work around an authorization error. Connect the intended account and review the source’s access instead.
Treat folder sharing as a separate step.
For Google Drive folder sync, UrbanLoop may show a service account that needs Viewer access to the intended signage folder. Use the exact account shown in the app. Workspace external-sharing and Shared Drive rules can affect this step separately from OAuth approval.
Give access only to the folder and content intended for signage. If your policy prevents the required sharing, ask the Drive administrator or UrbanLoop for help rather than opening a whole Shared Drive or changing domain-wide sharing rules.
Confirm access with one source and one screen.
Connect again
After the administrator’s review, retry Google sign-in in the same management app. Check the connected account and complete the consent flow offered there.
Select and preview the source
Open a test presentation, calendar or folder in its matching slide form. Confirm the expected content loads before saving.
Check playback and an update
Save the slide, add it to a playlist and assign it to a linked TV. Check playback, make a small source update, then confirm a later refresh reaches the screen.
If only one user or one platform fails, compare the account’s source access, organizational unit, OAuth client and app version. If the preview works but the TV does not, also check media and network access and the assigned playlist.
Keep the connection maintainable.
Use a Google account that will retain access to the content under your organization’s policy. Review affected slides when a staff member leaves, source ownership changes or Google access is revoked. Reconnect or reselect the source where required; a saved thumbnail does not establish continuing access.
For help, send the platform, app version, error wording and OAuth client ID if shown. A cropped screenshot without account secrets is useful. Never send passwords, refresh tokens, authorization codes or generated organization secrets.