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

Spike: Background data access permission/storage #6688

Closed
1 task
charlag opened this issue Mar 11, 2024 · 0 comments
Closed
1 task

Spike: Background data access permission/storage #6688

charlag opened this issue Mar 11, 2024 · 0 comments
Labels
spike issues that won't result in code but in knowledge when done state:done meets our definition of done

Comments

@charlag
Copy link
Contributor

charlag commented Mar 11, 2024

For implementing preview in mail notifications we need to access to auth token and mail keys info in the background.

We need to communicate this to our users and get their consent.

  1. How to we explain/enable this during onboarding?
  2. How does the setting for it might look like?
  3. What and how should we store for background access to minimize the amount of data that can be accessed (user password, offline db key, mail group key, private keys)?

Tasks

  • Document the plan
@charlag charlag added the spike issues that won't result in code but in knowledge when done label Mar 11, 2024
@kib42 kib42 closed this as completed Apr 16, 2024
@kib42 kib42 added the state:done meets our definition of done label Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spike issues that won't result in code but in knowledge when done state:done meets our definition of done
Projects
None yet
Development

No branches or pull requests

2 participants