Access Control Build Out

[amandahmeng]

Build out more fine grained user access to Aggie content

[tdat314]

#109 Initial start of buildout

created doc area for access control

fixed attachment limit issue

fixed minor existing permissions issues with User access to destructive edits #

[tdat314]

#116 Continued build out

Populates the teams field when returning users.
Applies this to the user list, manageable user list, and individual user detail response.
Normalizes older users without assigned teams so they return teams: [] instead of leaving the field undefined.

This does not add any team-based enforcement yet. It only makes team membership visible through the existing user API so we can build membership management and scoped access on top of it later.

[tdat314]

#111 Foundational backend changes for Team API setup as well as some more bug fixes for attachment upload limit

[tdat314]

#118 Continued build out of front end and permissions

Adds team data to the frontend user type.
Adds a Teams column to the user settings page.
Displays None when a user does not belong to any teams yet.

Adds a manageable teams endpoint.
Lets admins access all teams for assignment.
Lets team leads access only the teams they belong to.
Allows team leads to assign viewer/monitor users to their own teams.
Preserves any team memberships outside the team lead’s scope.
Keeps initial team lead assignment admin-controlled.
Prevents team leads from managing their own team membership or assigning admin/team_lead users.

[tdat314]

#119 Created Teams dedicated page for management of user teams

allows admin to assign members to teams and assign team leads
allows creation of teams from within a dedicated page rather just API calls
adds simple UI for team management