user's access and limitations

Dears,
please advise, is there any way to make “MODIFY” button in assets view not available for a user and at the same time to have possibility to modify some attributes?
and a second question - how to hide a Consoles for users?

Hi!

To modify attribute values you need the read:assets and write:attributes permission.
They do not need anything else, so you can remove the write:assets permission.
See the screenshot below of the /users page;

image

.
Onto your second question; “how to hide consoles for users?”
I’m not sure if you can. @Don @Pierre any idea?

Hi, Martin
Thanks a lot for a prompt response.
I need to keep possibility to add assets for users as well (so write:assets is On). If i do like this a user has an access to Modify as well. Is there a way to hide a button modify or to have permission to add an asset with write:assets Off?

Hi!

No, we expect users with the ability to add assets, are also allowed modify assets.

The only option is to use “restricted access”, and limit the assets linked to a user.
You can specify for each user what assets they are allowed to view and modify.
For example; Light asset #1 can be edited by User A, but not by User B.
See the restricted access documentation for this.

Maybe that could help :+1:

I have the opposite problem, after updating openremote the “consoles” of all realms except master have disappeared. Now if I try to access the app via localhost:8888/ourgrid/?realm=mycity it gives a login error and redirects me to localhost:8080/auth/realms/mycity/protocol/openid-connect/auth?..etc… and the only difference I see from when it worked was that I did have “consoles”, so in the user I created I had my custom asset and “console” linked. I don’t know if it has something to do with the problem. Well, probably the problem must be somewhere else, but I’ve been trying to fix it for half a day now, so upgrading is definitely not a good idea.