Image upload fails when external sharing is disabled

[nansui01230]

In Google Workspace organization where external sharing is disabled, uploading image files fails with the following error.

Error: failed to apply page: failed to upload image: failed to set permission for image: google api: Error 403: The user does not have sufficient permissions for this file., insufficientFilePermissions

The current process attempts to grant reader access to anyone.

deck/preload.go

Lines 216 to 235 in d4cdbb7

	uploaded, err := d.driveSrv.Files.Create(df).Media(bytes.NewBuffer(image.Bytes())).SupportsAllDrives(true).Do()
	if err != nil {
	image.SetUploadResult("", fmt.Errorf("failed to upload image: %w", err))
	return nil
	}
	// Set permission
	if _, err := d.driveSrv.Permissions.Create(uploaded.Id, &drive.Permission{
	Type: "anyone",
	Role: "reader",
	}).SupportsAllDrives(true).Do(); err != nil {
	// Clean up uploaded file on permission error
	if deleteErr := d.deleteOrTrashFile(ctx, uploaded.Id); deleteErr != nil {
	d.logger.Error("failed to delete uploaded file after permission error",
	slog.String("id", uploaded.Id),
	slog.Any("error", deleteErr))
	}
	image.SetUploadResult("", fmt.Errorf("failed to set permission for image: %w", err))
	return nil
	}

It would be great if the upload process could handle restricted environments.

Related Reference:

• Manage external sharing for your organization - Google Workspace Admin Help

[Songmu]

Since the deck requires the public URL of the image, this isn't easy to resolve fundamentally. Suppose you cannot change the permissions for Google Drive in your organization's policy. In that case, you can create a folder on your personal account, add shared editors to it, and specify --folder-id as a workaround. However, temporary image files will be uploaded to that folder, so this solution is only acceptable if that is acceptable.

[Songmu]

We apologize, but due to organizational policy, there is not enough permission for Deck to function. We may document this at a later date, but for now, we will close this issue.

If you would like, please use the workaround using --folder-id.