Skip to content
New issue

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

Add page for managing exports #17497

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

edith007
Copy link
Collaborator

@edith007 edith007 commented Mar 5, 2021

What is this PR for

This PR aims to solve the following issues: #10798 and #12992.
I have taken the work done by @whoodes and applied it against the current master.

Currently, we have a model called UserExportConsent which will be used to store consent information from the user. This class has a fields called reponse which is by default NO. It also has a field called export_id which tracks the users who has consented for organization export. And also an endpoint userexportconsent has been added for organisation realm export.

TO-DO :

  • Add a Consent Button in Data Exports Field in Organization Settings
  • Make two-column table with name and consent status.
  • Collecting Users consent flow should be live only for 7 days.
  • Update the Documentation

Add UserExportConsent class to help the admin to collect consent for
organisation export from the users.
This commit adds a field in RealmAuditLog callled
USER_EXPORT_CONSENT_CHANGED, which log the users consent at the time of
Organization Export.
@edith007 edith007 changed the title Add page for managing exports [WIP]Add page for managing exports Mar 5, 2021
@edith007 edith007 changed the title [WIP]Add page for managing exports Add page for managing exports Apr 3, 2021
@zulipbot
Copy link
Member

Heads up @edith007, we just merged some commits that conflict with the changes your made in this pull request! You can review this repository's recent commits to see where the conflicts occur. Please rebase your feature branch against the upstream/main branch and resolve your pull request's merge conflicts accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants