I created a service which creates devices on a local DB and also uses the ChirpStack grpc API to create them in ChirpStack (I save additional information on the local DB).
Now I want to hide or better remove the ability to use the ChirpStack UI for those functions, so there would be no conflicts with the local DB. I still want to have the frontend to e.g. see all device and gateways.
What would be the best way to stop “interactions” through the ChirpStack UI?
Is there a config where I could just deactivate the UI functions?
Add a user as a “Tenant user”. Then you get three options which will disable/enable write capabilities to various sections of the UI for a user logging in.
If you hover over the ‘?’ besides each permission type it tells you what they do. If you login as that user then you can test what they can do. Although I believe they shouldn’t be able to do anything other than view the data associated with that tenant. The admin user ( not a tenant user ) has access to do anything.