Let people browse their Google Drive and attach files to items as links.
Approach: Google's own Drive Picker shows the familiar Drive browser. Boards stores each chosen file's name, icon and link on the item.
Google sign-in helps, but doesn't cover it: today's sign-in only proves who someone is. Browsing Drive needs a Drive permission on top. Use the narrowest one, drive.file, which only grants access to the files a person picks.
Setup
Project: reuse the existing Google Cloud project and its Internal consent screen. Internal apps skip Google's app review, even for Drive permissions.
APIs: turn on the Google Drive API and the Google Picker API, and create an API key for the Picker.
Per person: each person approves Drive access once, the first time they attach a file.
Open question: should Drive links live in the existing Files column, or in a separate "Drive files" column type?
Shares its Google setup with the Google Sheets part of #8, and possibly with the Google Calendar connector in #3.
Let people browse their Google Drive and attach files to items as links.
**Approach:** Google's own Drive Picker shows the familiar Drive browser. Boards stores each chosen file's name, icon and link on the item.
**Google sign-in helps, but doesn't cover it:** today's sign-in only proves who someone is. Browsing Drive needs a Drive permission on top. Use the narrowest one, `drive.file`, which only grants access to the files a person picks.
**Setup**
1. **Project:** reuse the existing Google Cloud project and its Internal consent screen. Internal apps skip Google's app review, even for Drive permissions.
2. **APIs:** turn on the Google Drive API and the Google Picker API, and create an API key for the Picker.
3. **Per person:** each person approves Drive access once, the first time they attach a file.
**Open question:** should Drive links live in the existing Files column, or in a separate "Drive files" column type?
Shares its Google setup with the Google Sheets part of #8, and possibly with the Google Calendar connector in #3.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Let people browse their Google Drive and attach files to items as links.
Approach: Google's own Drive Picker shows the familiar Drive browser. Boards stores each chosen file's name, icon and link on the item.
Google sign-in helps, but doesn't cover it: today's sign-in only proves who someone is. Browsing Drive needs a Drive permission on top. Use the narrowest one,
drive.file, which only grants access to the files a person picks.Setup
Open question: should Drive links live in the existing Files column, or in a separate "Drive files" column type?
Shares its Google setup with the Google Sheets part of #8, and possibly with the Google Calendar connector in #3.