Trimble Connect Administrator Troubleshooting: Permission & Authorization Errors – LP360

No License Requirements. User requires an LP360 Online account and a Trimble Connect account, with appropriate licensing from Trimble.

📌 Problem

Administrators may encounter permission, authorization, licensing, OAuth, storage, or resource-access errors when configuring Trimble Connect or performing transfer operations with LP360 Cloud.

This article provides troubleshooting guidance for the following symptoms:

403 Forbidden: Integration Not Enabled for Organization
401 Unauthorized: Invalid or Expired OAuth Token
Project List Empty / Missing Expected Projects
403 Forbidden: Insufficient Project Permissions (Upload/Push)
Storage Quota Exceeded / 413 Payload Too Large
402 Payment Required: No Cloud Seat Assigned
OAuth Error: App Not Authorized for Tenant
404 Resource Not Found: Folder ID Inaccessible

🔍 Root Cause

The reported errors have different causes depending on where they occur.

Error or Symptom	Where It Occurs	Root Cause
`403 Forbidden: Integration Not Enabled for Organization`	LP360 Cloud User Interface when clicking Trimble Connect	The Trimble Connect integration switch is toggled off at the organization/tenant level in LP360 Portal.
`401 Unauthorized: Invalid or Expired OAuth Token`	File Browser / Project List	The user's Trimble OAuth refresh token has expired, was revoked in Trimble Identity Management, or the session timed out.
`Project List Empty / Missing Expected Projects`	Trimble Connect Browser Modal	The user's Trimble ID is either not an invited member of the project, or the project was created in a different regional data center.
`403 Forbidden: Insufficient Project Permissions (Upload/Push)`	Push to Trimble Connect Modal	The user has Read-Only / Viewer permissions in the target Trimble Connect project or folder.
`Storage Quota Exceeded / 413 Payload Too Large`	Copy to Cloud while a transfer is in progress	The organization has reached its allocated LP360 Cloud storage capacity, or the file exceeds the cloud license limits.
`402 Payment Required: No Cloud Seat Assigned`	Initial connection or transfer action	The user account exists in the organization, but no LP360 Collaborate seat is assigned.
`OAuth Error: App Not Authorized for Tenant`	Trimble ID Login Window at `identity.trimble.com`	The enterprise's Trimble administrator has restricted third-party application consents in the Trimble Admin Console.
`404 Resource Not Found: Folder ID Inaccessible`	File Browser or transfer initiation	The target folder in Trimble Connect was moved, deleted, or had its access inheritance broken by another team member.

🧠 What is Trimble Connect Authorization?

LP360 Cloud uses Trimble Connect access and authorization when users connect to Trimble Connect projects or perform supported transfer operations.

Access can be affected by several administrative controls, including:

LP360 organization-level integration settings
LP360 Cloud licensing or seat assignments
Trimble OAuth authentication
Trimble Connect project membership
Project and folder permissions
Trimble project region
Enterprise application authorization
LP360 Cloud storage capacity
Availability of the selected Trimble Connect resource

Because these controls are administered in different locations, use the exact error or symptom to identify the appropriate resolution below.

Author note: Confirm whether additional OAuth or Trimble Connect integration background should be included before publishing.

✅ Probable Resolutions

1. Re-authenticate an Invalid or Expired OAuth Token

Use for: 401 Unauthorized: Invalid or Expired OAuth Token

Have the user click Re-authenticate with Trimble in the prompt.
If re-authentication continues to fail in a loop, navigate to Profile > Linked Integrations in LP360 Cloud.
Click Disconnect / Revoke Token.
Perform a fresh login.

2. Verify Project Membership and Region

Use for: Project List Empty / Missing Expected Projects

Open the Trimble Connect Web App.
Confirm the user's email is an active member under Project Settings > Team.
Verify the server region: North America, Europe, or Asia-Pacific.
Ensure the project region matches the tenant location configured in Trimble ID.

3. Grant Upload or Write Permissions

Use for: 403 Forbidden: Insufficient Project Permissions (Upload/Push)

In Trimble Connect, open the destination project.
Go to Team.
Upgrade the user from Viewer to User or Admin.
If folder-level permissions are enabled, inspect the destination directory's access list.
Grant Write / Upload permissions.

Trimble Connect folder-level access permissions

4. Resolve Storage Quota or File-Size Limits

⚠️ Important:
Online Storage Usage monitoring is not yet available in the LP360 Portal ...but is coming soon!

Use for: Storage Quota Exceeded / 413 Payload Too Large

Open LP360 Portal Admin > Storage Usage.
Check whether total usage has met or exceeded the subscription ceiling.
Clean up unneeded point cloud datasets or contact your account manager to add additional cloud storage pool capacity.

5. Authorize LP360 Cloud for the Trimble Enterprise Tenant

Use for: OAuth Error: App Not Authorized for Tenant

Have the Trimble Enterprise Admin sign in to the Trimble Cloud Console.
Under Applications / API Access, approve the LP360 Cloud client application for the organization's enterprise tenant.

6. Refresh an Inaccessible Trimble Connect Folder

Use for: 404 Resource Not Found: Folder ID Inaccessible

In LP360 Cloud, click Refresh Directory or Return to Project Root.
Verify in Trimble Connect that the folder path still exists and has not been archived.

LP360 Cloud File Browser showing Refresh Directory or Return to Project Root

📚 Additional Notes

Trimble Connect Integration in LP360 Cloud

Trimble Connect Integration: Administrative Configuration Guide

📬 Need Help?

If you're still stuck, please Contact Support for assistance.

Related to