Enable takeout for profile users
See original GitHub issueThe takeout feature for Profile Users should be implemented once proper authentication flow for them is in place.
(A TODO for this job is included in the core/domain/takeout_service.py
file)
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Export your organization's data - Google Workspace Admin Help
The Data Export tool exports all supported data for all users. ... To let your users download their data, allow Google Takeout and...
Read more >Transfer your Gmail and Drive with Google Takeout for Schools
This video covers how to transfer your Gmail and your Google Drive files from your school account to another account. This is useful...
Read more >Whole-tenant Google Takeout (for all users) - without needing ...
I'm closing an old free G Suite tenant org, and I want to bulk export the Google Drive files for all users as...
Read more >How to Use Google Takeout to Download Your Google Data
Google Takeout is a service that backs up all of your Google account's data into one file, which you can then download.
Read more >New Consolidated Controls Page for Google Takeout
Beginning November 15, 2022, admins can manage Takeout settings from ... a list of those services: Allow or block Google Takeout for users)....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Let’s close this & handle this later. Thanks @sajalasati – that context will be really helpful when we tackle this part of the broader wipeout/takeout support in Android. See: https://github.com/oppia/oppia-android/issues/2127.
Thanks @sajalasati. I’ll follow up with @BenHenning on this.