ruangrupa/lumbung-kios-cms
0
0
Fork 0
Code Issues 13 Pull Requests Packages Projects 1 Releases Wiki Activity

Create user roles hierarchy #10

New Issue
Open
opened 2024-01-31 10:18:02 +00:00 by aadil · 2 comments
aadil commented 2024-01-31 10:18:02 +00:00
Owner
Copy Link
Copy Source
  • 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
Author
Owner
Copy Link
Copy Source

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

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
Author
Owner
Copy Link
Copy Source

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.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 needs design
needs info
Need to ask client for more information or elaborate the task more clearly.
 needs r&d
No labels needs info needs r&d
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Nieuwe Institut fellowship prototyping
Ready
Assignees
Clear assignees
aadil (Aadil Ayub) autono-bot (Autono-bot) autonomic chocobozzz christoph decentral1se (decentral1se) Esthetech fahad knoflook r (rra) simoon tma
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ruangrupa/lumbung-kios-cms#10