We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is your feature request related to a problem? Please describe.
Currently, each Subscriber is limited to a single Google account, since we store the google_tkn in the Subscriber table.
Subscriber
google_tkn
However, it's likely that users may have multiple Google accounts that they want to connect to.
Describe the solution you'd like
google_*
Accounts
Calendar
(If it makes sense, we could also remove the owner field from the Calendar table, and derive that knowledge from the linked Accounts table)
owner
Describe alternatives you've considered
If multiple Google account support isn't on the roadmap, feel free to disregard this ticket!
The text was updated successfully, but these errors were encountered:
For #170 I've added an external connections table to generically handle oauth tokens. We should leverage that for this ticket.
Sorry, something went wrong.
Any update on this issue? Really an important feature given most have work and personal google accounts.
@umgpy yes, it's targeted for release by the end of May, however, we can prioritize this issue to see if we can get it in earlier.
Thanks @malini! Would be happy to test and debug whenever something is ready.
No branches or pull requests
Is your feature request related to a problem? Please describe.
Currently, each
Subscriber
is limited to a single Google account, since we store thegoogle_tkn
in theSubscriber
table.However, it's likely that users may have multiple Google accounts that they want to connect to.
Describe the solution you'd like
google_*
fields to a newAccounts
tableAccounts
table to theSubscriber
tableCalendar
table to theAccounts
table(If it makes sense, we could also remove the
owner
field from theCalendar
table, and derive that knowledge from the linkedAccounts
table)Describe alternatives you've considered
If multiple Google account support isn't on the roadmap, feel free to disregard this ticket!
The text was updated successfully, but these errors were encountered: