#13 User/permission notes

[Gary Gocek]

- Consider users and permissions.
- Admin (can do all menu/meal/recipe things, and can
customize the tool and modify users)
- Menu Read/Write/none (for grouping meals)
- Meal Read/Write/none (for grouping recipes)
- Recipe Read/Write/none (for working with recipe
details)
- Meal/Recipe Scheduler (can tell the cook when to
cook it, but can’t control what is cookable)
- Shopper (can generate a shopping list; would compare
inventory vs. schedule)
[A restaurant customer would have read access to
menus and meals, but no access to recipes.]
[A cookbook reader would have read access to menus,
meals and recipes.]
[Might need special access, e.g., a meal reader might
be able to see the names and descriptions and
nutritional info of the recipes in the meals, but not the
ingredients. Might need fields on each class that list
the permission needed. So, a recipe name is readable
if the user can read the parent meal, i.e., some child
object fields are readable when the parent object is
readable.]
[Upward mobility – a user who can read a recipe can
read the parent meals, and a user who can read a meal
can read the parent menus. A person who can read
menus will see the child meal names and descriptions,
but not necessarily the recipes in the meals.]