Setup page

[julienfortin]

On the first run, setup tutorial step by step to create the first user, choose to import from a data base or not. Etc..

Setup the new database.

[mitar]

Also, do not forget that we should support multiple units. So there is a setup page for initial installation. But also setup page for each unit.

[brianashpugh]

initial setup page:
create first user: email, password, and name (becomes site-level admin)
set first user as admin
allow db import (seems like csv is the most flexible, but the use cases here aren't quite clear to me)
send to unit setup page

unit setup page (accessible only by site admins):
define name of unit: name
(would be nice to define the first workshift manager or unit-level admin on this page, but we can't assume they are already registered, so instead the first user to register or get transferred into the unit will become a unit-level admin)

[mitar]

I do not think this is critical. For now we should have good documentation.

I think more important is to be able to create users from a CSV files.

So how I would do it:

• if there is no user in the database, user can register themself and that user becomes site admin
• afterwards, there is no user registration possible
• site admin has a form to create units
• and form to create other users
• and then you have house admins who can import CSV list of e-mails which are then created as accounts if there are not yet there
• users get e-mail invitation
• users can configure their username and password (and other stuff)

[mitar]

Importing of old data I would not support for now.

[brianashpugh]

that makes the most sense if getting a CSV of residents is easy. csv member adding is already in place. I'll check the status of the email invitations.