The important detail here is the scope of the failure: A user can open files in a Shared Drive but the New and Upload options are missing or denied. First determine which part still works before changing any settings.
What is actually failing?
Observed behavior: A user can open files in a Shared Drive but the New and Upload options are missing or denied. Record the exact app or device build, affected account or file, and the first time this happened. A screenshot of the error state or a short log excerpt is useful when it contains no sensitive information.
Control comparison: Check the user’s assigned Shared Drive role and whether the target folder has external-sharing restrictions. Keep the account, file, network and hardware unchanged wherever the comparison permits. If the control works, the difference between the two paths is your most useful clue.
- Does this reproduce every attempt, or only after a reboot, resume, update or account switch?
- Can the affected action complete through another supported route without changing the original data?
- Is the problem limited to one file, one profile, one device or every user of the service?
Separate possible causes
A Google Drive item can be visible but not writable. Check role and ownership of the exact shared folder before considering an account-wide issue.
Focused investigation: Review organizational shared-drive restrictions and inherited permissions rather than adding wide domain access. Treat this as a way to test a cause, not proof that the cause has already been established.
| What you observe | What to check next |
|---|---|
| The controlled comparison succeeds | Compare the settings, permissions or content specific to the failing path. |
| Both original and control fail | Check the shared device, account, network or service dependencies before changing the application. |
| It works only after a fresh start | Inspect background processes, cache state, session expiry or a reconnect sequence. |
Protect the current setup
Verify the active account and sharing scope before changing cloud settings. Use a harmless test file or message rather than a sensitive document.
Save the current configuration, note its values, and use a harmless test item where possible. Avoid combining this repair with unrelated updates. In particular, Do not change a Shared Drive to public access to work around a role mismatch.
Choose Beginner for reversible checks or Advanced for targeted diagnostics. A user can open files in a Shared Drive but the New and Upload options are missing or denied. Confirm the affected product, user account, file or device, then record the time and a screenshot without private account information. This is the baseline; do not change settings yet. Check the user's assigned Shared Drive role and whether the target folder has external-sharing restrictions. Perform the comparison with one harmless test item. Write down both the successful and failing paths so that the next action targets the actual difference. Ask a manager for Contributor access when uploading in Drive web, or Content manager access for Drive for desktop, then retry with a tiny harmless document. Change one setting or workflow at a time. Preserve an easy route back to the previous configuration and allow any synchronization, indexing or activation step to complete before retesting. The intended collaborator uploads a test file while viewers retain read-only access. Test the original failing situation rather than an unrelated feature. If it passes, repeat after one normal restart or reconnect; if it fails, restore temporary diagnostic settings and use the Advanced track. Review organizational shared-drive restrictions and inherited permissions rather than adding wide domain access. Note which component provides the first observable failure. Avoid logging secrets, account recovery keys, authentication cookies or the contents of private documents. Use the least invasive diagnostic appropriate to Google Workspace Shared Drive Member Can View but Cannot Upload. Compare the result with the supported control path: Check the user's assigned Shared Drive role and whether the target folder has external-sharing restrictions. If there are policy restrictions, involve the administrator rather than bypassing them. Ask a manager for Contributor access when uploading in Drive web, or Content manager access for Drive for desktop, then retry with a tiny harmless document. Tie any configuration change to a specific observation. If the result is ambiguous, collect additional evidence instead of layering new resets onto an unexplained problem. The intended collaborator uploads a test file while viewers retain read-only access. If this does not pass, reverse temporary changes. Safety limit: Do not change a Shared Drive to public access to work around a role mismatch. Provide support with the error text, environment version and reproducible comparison; do not submit private tokens or user data.Step-by-Step Troubleshooting
Capture the exact symptom
Use a supported comparison
Apply the narrow repair
Test the original workflow
Establish the failing boundary
Collect focused diagnostics
Validate the likely cause
Restore and escalate safely
Solution Checklist
Avoid these shortcuts
- Do not change a Shared Drive to public access to work around a role mismatch.
- Do not treat a successful unrelated feature as evidence that the failing action is fixed; run the original comparison again.
- Do not erase logs, synced files or working credentials before you know which layer was responsible.
Confirm the outcome
Pass condition: The intended collaborator uploads a test file while viewers retain read-only access. Repeat the same test using the original account, document, peripheral or network path; a passing test on a substitute is useful evidence but is not the final result.
For intermittent problems, repeat the operation after a normal application restart and again after the state change that originally triggered it, such as reconnecting a dock, signing in, or resuming from sleep. Check for new errors in the same location as the original symptom.
When troubleshooting does not help
If the controlled test still fails, return temporary settings to their earlier state and collect the minimum relevant evidence. Next diagnostic: Review organizational shared-drive restrictions and inherited permissions rather than adding wide domain access. Note exactly which comparison failed and what changed after the attempted repair.
For managed devices, privacy-sensitive files, damaged storage or account security concerns, escalate to the responsible administrator or vendor with timestamps and non-sensitive logs rather than attempting a broad reset.
Keep this configuration reliable
Use least-privilege sharing, stable time zones and a small test change when migrating accounts or modifying synchronization rules.
When the system is stable, record the specific working change: Ask a manager for Contributor access when uploading in Drive web, or Content manager access for Drive for desktop, then retry with a tiny harmless document. Keep this as a reversible troubleshooting record so a later upgrade does not require repeating unrelated repair attempts.
Official Resources
For product-specific procedures and limitations, consult Google Workspace — How file access works in shared drives.
Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.