136 kitchen staff view permission page adding categories and appropriate filtering

[idavoong]

Developer: Ida Voong

Closes #136

Pull Request Summary

• make sure kitchen staff cannot create/edit/delete recipes (and publish drafts?)
• filter by user role in permissions page
• sort users in permissions page

Modifications

• src/app/drafts/page.tsx: move client code into src/components/DraftsPageClient.tsx, fetch user role
• src/app/permissions/page.tsx: move client code into src/components/PermissionsClient.tsx, edit test users
• src/components/PermissionsClient.tsx: filter and sort users
• src/app/recipe/page.tsx: fetch user role
• src/components/CardGrid.tsx: pass user role to components
• src/components/CategoryToggle.tsx: accept RoleValue as a type to reuse code from recipe page
• src/components/ComboCard.tsx: only admin can edit, publish, and delete draft combos
• src/components/MealBrowser.tsx: only admin can create new recipe; pass user role to components
• src/components/RecipeCard.tsx: only admin can edit, publish, and delete draft recipes
• src/components/RecipePageClient.tsx: pass user role to components
• src/components/SortPermissionsButton.tsx: edit onSortChange to expose the selected sort type to parent component
• src/components/ViewRecipePopUp.tsx: only admin can edit recipes (pop ups in recipe page)
• src/lib/types.ts: add new type for user roles
• src/components/menuPlanning/RecipeDatabase.tsx: edit component type

Testing Considerations

• only admin can create/edit/publish/delete combos and recipes
• filtering on permissions page
• sorting on permissions page

Pull Request Checklist

• Code is neat, readable, and works
• Comments are appropriate
• The commit messages follows our guidelines
• The developer name is specified
• The summary is completed
• Assign reviewers

Screenshots/Screencast

• I think on Haixin's branch she moved the checkboxes and stuff to the left side so I didn't do it here

- view for dining site staff and not logged in

Notes:

• "can only view allergen/filter tags only when clicked on recipe or combo cards on Recipe page" not implemented yet

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
meals-that-connect-25	Ready	Preview, Comment	May 11, 2026 2:57am

[idavoong]

I implemented permissions based on Admin/Kitchen Staff role, but I noticed that on the permissions page that there is a yes/no option. Sorting is based on the schema in mongodb because theres a createdAt and updatedAt. I think how we're currently showing users and perms deviates from schema so lmk what to do with merge conflicts.

[soramicha]

I implemented permissions based on Admin/Kitchen Staff role, but I noticed that on the permissions page that there is a yes/no option. Sorting is based on the schema in mongodb because theres a createdAt and updatedAt. I think how we're currently showing users and perms deviates from schema so lmk what to do with merge conflicts.

will get back to you after our client meeting tomorrow!

[anvch]

Hi Ida, we discussed and for permissions in order of most restrictive to least restrictive here are the actions that each should be able to do. In my opinion, the yes/no flags are not necessary and permissions should just be role-based.

logged out/viewer – menu calendar and allergen/restrictions/etc. flags
dining site staff – view NOT edit recipes
kitchen/nutrition staff – edit recipes and calendar
admin – can edit permissions