User roles

Instead of the granular security that existed in the old directory, the new directory employs a new role-based strategy. Here are the roles:

Basic user - This user can only read from the database, but can't actually make or approve any changes to pilgrim info, week info, or community info. Going forward, there shouldn't be much use for this kind of user, so I didn't prioritize providing a way to create new basic users. The current basic users that are in the system were users in the old system that didn't have enough privileges to qualify for any of the new roles and can probably be removed from the system.

Week administrator - This user can create, modify, and approve changes to pilgrim info and can make changes to week information for weeks that they have been assigned as an administrator for. This user can create other week administrator users for weeks that they have been assigned as an administrator for.

Community administrator - This user can:

- create, modify, and approve changes to pilgrim info.

- create and modify weeks and fully administrate them

- fully administrate communities that they are assigned as administrators for.

Site administrator - This user has all the rights of a community administrator with the additional ability to create new communities and create basic users. This user also received emails when someone submits feedback using the feedback link in the footer of every page.

The replatform job that was run on the old database data automatically took users that were "admins" and made them community administrators for NCPP. The job also took users that were not admins but still had some sort of editing capability that had an email address that matched the email address of the rector for a given week and made them week administrators for those weeks. So while there were around 30 people with editing capabilities in the old directory, they have now been sorted into one of these three roles: basic user, week administrator, and community administrator.