Membership (scoped access by email domain)

[paula-berman]

@santisiri would it be possible to deploy the university urls in a way that only allows users that register with the respective university e-mail to vote? So you could only vote at ucberkeley.democracy.earth if you register with a @berkeley.edu e-mail.

This would enable all kinds of university pilots.

[LucasIsasmendi]

regarding univesity...we have this permissioned branch

[santisiri]

Merged now.

[paula-berman]

ok, can we have that already working on the deployment of our new manual university jurisdictions? @LucasIsasmendi @santisiri

yale.democracy.earth - #yale - only users with @yale.edu e-mails can vote

ucberkeley.democracy.earth - #ucberkeley - only users with @berkeley.edu e-mails can vote

uva.democracy.earth - #uva - only users with @virginia.edu e-mails can vote

cornell.democracy.earth - #cornell only users with @cornell.edu e-mails u can vote

northwestern.democracy.earth - #northwestern only users with @u.northwestern.edu e-mails can vote

[LucasIsasmendi]

We need to create independent instances for each university.
Regarding database we have 2 options:

1. create independent mongodb instances for each university (not shared database)
2. implement the concept of scope(~) and use shared database. The app will know if the user is available to vote in that scope ~yale, ~ucberkeley, ~uva, ~cornell, ~northwestern

Option 2 is long term approach feature.
Option 1 is good to get some analytics insights

[paula-berman]

@LucasIsasmendi does that mean that those users wouldn't be connected to vote.democracy.earth?

[santisiri]

Option 2. they will be connected.