[Bug]: User role permissions

[cadtoolbox]

Bug Description

A normal user per the documentation should not be allowed to edit printer settings. It appears that a normal user has all the same permissions as an admin including adding and deleting printers.

Expected Behavior

The expectation would be normal users should not be able to:

• Add printers
• Delete printers
• Reorder the queue
• Delete from the queue jobs they do not own
• Delete archive files they do not own

Steps to Reproduce

1. Enable user authentication.
2. Create a user with the role assigned as 'user'
3. Login as the new user
4. Add or delete a printer.

Printer Model

X1

Bambuddy Version

0.1.6b11

Printer Firmware Version

na

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

Screenshots

No response

Additional Context

No response

Checklist

• I have searched existing issues to ensure this bug hasn't already been reported
• I am using the latest version of Bambuddy
• My printer is set to LAN Only mode

[maziggy]

@JesseFPV can you please check? Thanks!

[maziggy]

Looks to me like only the settings menu requires admin permissions.

[cadtoolbox]

If what features were available to normal users were configurable by the admin that would be ideal. Beyond that, having different roles with different options available would further enhance the user experience.

In my scenario, we wouldn't want normal users to be able to add or remove new printers, delete someone else's print job or re-order the queue. An admin should be allowed to add and remove printers. Additionally, an in-between type of role might be allowed to adjust the queue order.

[JesseFPV]

Currently it only handles the page access but not real roles in the background as the system was not made with this in mind. It could be done but requires a lot of rework. As it is an open source project you are totally free to take on this job!

[maziggy]

Now where we have a build-in authentication it makes sense to extend it as suggested. That's at least my opinion. I'll put it on the open task list. If you don't have the time @JesseFPV I'll look into it.

[JesseFPV]

I totally agree, but it is not a bug but future request and requires a lot of work on the main architecture. I think its something for the roadmap.