stereo.cat/backend
2
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

Roles/plans #7

New issue
Open
opened 2025-06-22 11:20:02 +00:00 by hex · 6 comments
hex commented 2025-06-22 11:20:02 +00:00
Owner
Copy link

We need to add user roles/plans

We need to add user roles/plans
grng commented 2025-07-24 16:43:20 +00:00
Owner
Copy link

wdym

wdym
hex commented 2025-07-30 16:13:01 +00:00
Author
Owner
Copy link

image

this. also admin/moderator roles w/ permission to like do shit yk

![image](/attachments/c977be4f-c522-4f72-bf48-6099d2272f77) this. also admin/moderator roles w/ permission to like do shit yk
image.png
23 KiB
👍 1
grng commented 2025-07-31 20:54:50 +00:00
Owner
Copy link

being worked on now

being worked on now
hex commented 2025-08-01 11:30:47 +00:00
Author
Owner
Copy link

fire

fire
hex commented 2025-08-08 18:17:40 +00:00
Author
Owner
Copy link

Idea for roles:

  • Roles can be applied to one or more users
  • It describes the limits of those users (e.g. how much can be stored simultaneously)
  • It describes the permissions of those users (currently should only be a toggle "Administrator", in the future may be individual permissions like Discord, e.g. "Ban User" and "Delete Upload")
  • Backend comes with a default admin role that is automatically applied to everyone registering for the instance
Idea for roles: - Roles can be applied to one or more users - It describes the limits of those users (e.g. how much can be stored simultaneously) - It describes the permissions of those users (currently should only be a toggle "Administrator", in the future may be individual permissions like Discord, e.g. "Ban User" and "Delete Upload") - Backend comes with a default admin role that is automatically applied to everyone registering for the instance
hex commented 2025-08-09 20:02:54 +00:00
Author
Owner
Copy link

Also to add: A user can have more than one roles, so roles should have some kind of priority indicator (e.g. a number ranging from 1 to 100, 1 being the role taking precedence over all other roles, and 100 being the lowest role).

Store roles as some kind of array (probably impossible with sql shenanigans) or use a many-to-many relationship table.

Also to add: A user can have more than one roles, so roles should have some kind of priority indicator (e.g. a number ranging from 1 to 100, 1 being the role taking precedence over all other roles, and 100 being the lowest role). Store roles as some kind of array (probably impossible with sql shenanigans) or use a many-to-many relationship table.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
boxy-integration
state
fix-file-serving
auth-uploads
authentication
file-serving
uploading
No results found.
Labels
Clear labels   
Priority: HIGH

Priority: HIGH

  
TODO

Issue label for things that need to be added or fixed.

No labels
Priority: HIGH
TODO
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: stereo.cat/backend#7
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?