Enable creating documents as logged-in user (take 2) #526
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up to #508 to (hopefully!) enable creating documents on behalf of logged-in Hermes users when running Hermes as a service account with domain-wide authority.
Shared drive permissions and Google Docs notification settings are fun, and hopefully this can create documents with the same notification settings as when a user creates their own Google Docs, by first copying the template to a new temporary drafts folder as the logged-in user, and then using the service user to copy the file to the drafts folder (which should have less permissive permissions - will submit another PR for these doc updates).
New config attribute