Google Drive permission scope change
Based on the latest status provided by Google on 2025/09/12, Google has made additional changes to its campus security policies, with further updates still possible. We will review and adjust our integration approach in alignment with Google’s latest policies on a rolling basis.
Background
To comply with Google’s new campus security authorization policy requirements and to ensure service stability and compliance, we have adjusted myViewBoard’s access to Google Drive from Full access to Read-only Access.
Affected file types include:
- Files imported directly from Google Drive.
- Files shared with you by others.
- Files created by other applications and stored in Google Drive.
Impact on users
Files can no longer be overwritten directly, but you can still open and edit all of the affected files from Google Drive, with the following changes:
- Open an existing OLF file or import files via File Management
- When working with these files, use Save As and rename the file to store a new copy into your Google Drive.
- The new copy will be considered as “created by myViewBoard”, with the file ownership transferred to you.
- You can reopen this new copy later, and then use Save directly to overwrite.
- FYI: If you attempt to use Save (instead of Save As) to overwrite the original file, the system will:
- Automatically create a copy
- Append the current date to the file name
- Show a toast message to inform users of the new file name
- Export image files, PDFs, or other presentation formats from File Management
- When a user opens a PDF, image file, or presentation file from Google Drive through File Management, they must use a unique file name when exporting in order to create a new file.
- If you save a file with the same file name and type as one that already exists in the Google Drive folder, Google will interpret this action as an attempt to overwrite the existing file. The system will instead automatically create a copy of the file, and append the current date to the file name of this new copy.
Open file
Save as
Binding solution for Google Workspace Enterprise
In response to Google’s latest policy changes, we are also providing a new binding solution for Google Workspace Enterprise users.
Domain-wide delegation
-
Simplified Process.
School IT Admins can enable permissions for all teachers in one step. When teachers link their accounts, they will completely bypass Google’s authorization consent screen, resulting in a smoother and simpler account linking experience.
-
Automatic Drive Permissions.
Google Drive access permissions will be automatically selected, preventing users from overlooking checkboxes that could otherwise cause access issues.
-
Centralized Management.
This allows IT departments to more efficiently manage application authorizations for all staff, ensuring organizational security and compliance.
How to set up?
Please refer to our support document here:
FAQs
A collection of your most common questions.
Is the Google admin no longer required to provide the ViewSonic connect and myViewBoard APIs?
Yes, the Google admin no longer needs to manually enter the API details for the ViewSonic Connect and myViewBoard apps.
However, the manual configuration still offers a key benefit for enterprise users:
- It allows the IT administrator to bypass the user consent screen entirely for all users in the organization.
- This creates a smoother, more seamless onboarding experience for employees, as they won't have to manually check the consent box the first time they connect their accounts.
So, while the manual setup is no longer a mandatory workaround to make the app function, it remains a recommended convenience for Google Workspace admins who want to streamline the user experience for their entire organization. It has transitioned from being a required fix to an optional feature.
If the permission is now read-only, how can someone use "Save as" to save to the drive? Please explain.
The new read-only permission applies primarily to accessing and editing existing files on Google Drive.
- What is restricted: Users cannot directly edit or overwrite files in Google Drive that were not originally created through myViewBoard (e.g., shared documents or older files).
- What is still possible: When a user chooses “Save as”, myViewBoard creates a new file copy in the user’s Google Drive. This action does not modify existing files and is therefore fully supported under the read-only permission.
In short, “Save as” adds a new file rather than editing an old one, which is why it continues to work even with read-only access.