New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: Dedicated User Management for vis #94
Comments
Is there anything new or a schedule? It will probably be built into vis-2. So I switched to vis-2, still the same error so far? |
This is great news any ETA planned? So it could be that we will soon have iobroker permissions, roles throughout. |
I think the version with the permissions on project level will be released on Monday in beta. For the further stuff no ETA always depends if there is more important things going on in some projects and how I have time besides my main job 😬 |
@foxriver76 Just to understand, what is the use-case to have such permissions on widget level? To have this feature on view level I can understand but I can't currently imagine in which use cases it is really helpfull on widget level. |
I could imagine eg having a button to open a door which should only be visible to specific users. |
Please check with 2.9.18. Has permissions for projects and views. Please report bugs in separate issues. We will check if permissions on widget level are really desirable. |
I find this very reasonable:
think about guest or kids, so you prevent that important things are password protected. |
with 2.9.20 the permission integration is finished, also for single widgets. |
Is your feature request related to a problem? Please describe.
Today I am not able to easily distinct which users or groups should be able to access runtime/editor and then which of them is able to see a project, view, etc. A long discussion regarding this is here: https://forum.iobroker.net/topic/54281/vis-views-benutzer-zugriffsberechtigung/21
Describe the solution you'd like
A clear, dedicated (and documented ;)) mechanism to administrate users for what I produce with the help of the vis(2) adapter.
Meaning:
Describe alternatives you've considered
Workarounds found in the net that are either tedious or not feasable.
The text was updated successfully, but these errors were encountered: