read-only user

[pfedan]

• I have searched the issues of this repository and believe that this is not a duplicate.

Summary

Possibility to create a "read-only" user. Right now, the lowest level user can still send downstream-messages.

What is the use-case?

Ideally, Chirpstack will be transparent in many use cases. However, a maintenance level user could use the UI to troubleshoot (e.g. see if a gateway is online, ...).

Implementation description

Add another checkbox when Organization Users are created, to prevent them from being able to send payloads to devices (or make any active interaction/configuration).

Can you implement this by yourself and make a pull request?

Unfortunately not.