Create user roles hierarchy #10

New Issue

aadil · 2024-01-31T10:18:02Z

aadil commented

2024-01-31 10:18:02 +00:00

Define what kind of user hierarchy we want
Figure out how to implement in payload

- [ ] Define what kind of user hierarchy we want - [ ] Figure out how to implement in payload

aadil added this to the Nieuwe Institut fellowship prototyping project 2024-01-31 10:20:12 +00:00

aadil added the

needs r&d

label 2024-01-31 10:25:14 +00:00

aadil commented

2024-01-31 10:50:53 +00:00

Relevant: https://payloadcms.com/blog/build-your-own-rbac

aadil added the

needs info

label 2024-02-25 14:14:54 +00:00

aadil commented

2024-02-25 14:36:08 +00:00

Generally, we should have 3 types of users:

Admins: People from kois team such as Ajeng, Elaine who would be doing the actual data entry. They would have complete edit access
Makers: They should be able to edit only their name, and what products they want to sell, and request routes
Retailers: They should be able to edit their name, and what products they would like to sell, and request routes.
Couriers: Should be able to edit their name, location, itinerary, weight allowance

The hard part here is linking a specific maker/retailer/courier to a user. Perhaps we could add a "type" field to the user collection, and then move all the fields for maker/retailer/courier there?

Generally, we should have 3 types of users: - **Admins**: People from kois team such as Ajeng, Elaine who would be doing the actual data entry. They would have complete edit access - **Makers**: They should be able to edit only their name, and what products they want to sell, and request routes - **Retailers**: They should be able to edit their name, and what products they would like to sell, and request routes. - **Couriers**: Should be able to edit their name, location, itinerary, weight allowance The hard part here is linking a specific maker/retailer/courier to a user. Perhaps we could add a "type" field to the user collection, and then move all the fields for maker/retailer/courier there?

aadil referenced this issue from a commit

2024-02-25 14:52:17 +00:00

add courier fields (#10)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: ruangrupa/lumbung-kios-cms#10