@Tom-Elliott or anyone else:
The Type: MAIN_MENU
The parent: main
The node
The value: tasktypeedit
Anything wrong with that? It does not seem to work for me.
Please, let me know if I am being too demanding for so little.
.

@Sebastian-Roth I shall take that piece of advice, try putting the pieces together. Thank you again, so much for your responsivity!

Hello!
Do you recon it could be a bit easier if you forwarded me to a full documentation of FOG and its file system? As I still struggle to implement all the functionnalities I need to in order to have FOG work the way I want.

@Tom-Elliott said in Permissions management server side:
Thank you so much Tom, you just allowed me to understand how the accesscontrol module works!
I guess I can from now on do the same with every little bit that could be missing in order to match my needs. I feel extatic and relieved. Living to learn a little bit every day!

@Wayne-Workman @Tom-Elliott So my new issue is that the technician view has access to the accesscontrol area and I am not able to tick it off. Any suggestions?

@Tom-Elliott Thank you for pointing this out, I feel that this solution has an immense potential and I am only scratching the surface of it. Kudos to you and @Fernando-Gietz for working on such a thourough product!

@Sebastian-Roth in new ipxe entry:

@6rilT @george1421 @jflippen Why not just use the AccesControl plugin as suggested in the other thread? If that is not yet suiting all the needs we might just modify that. It’s all there, why not use it instead of coming up with completely new things?

This is amazing! Am looking into this just now.

@george1421 in new ipxe entry:

I get the impression you are using the FOG server as some kind of backup tool. If you are doing that, there are better (free) tools out there than FOG, such as Veeam Endpoint Backup (free).
There are surely risks in proceeding with your plan. Uncontrolled disc consumption is one that comes to mind.

Veeam Agent for Linux could be somewhat interesting, although I have to implement a DBAN in between backup and restore phases AND more importantly keep a log of what has been backed up and deployed, thanx to GDPR.

@jflippen in new ipxe entry:

@george1421 @Sebastian-Roth what about a compromise? Is it possible to have accounts for logging into the fog web UI that have limited access? Like only the hosts tab and image / capture from the list of clients. You can protect certain images from being written over already, so he can protect anything he doesn’t want modified and unlock as needed for his lower tier staff.
I think it was back in 1.4.x that FOG had limited user accounts that could deploy images, it seems they were removed though.

That sounds like a great idea only way, way, WAY beyond my knowledge and comprehension of the system. I am just an apprentice after all.
Thank you so much for your attention and leads!

@Tom-Elliott @Wayne-Workman : could not find it on the wiki page but I was not looking on the right page. found it and am looking into it just now. Thank you again and my apologies for being such a noob!

@Wayne-Workman Thank you! I will look into that straight away!.. NOOOOOOOOOO! It is unfortunately not available anymore! such a shame. I guess it is too much hassle maintaining this module.

Hello!
I need to set a “standard user” profile that does not have any access to the “Fog Configuration” menu in order not to mess with my settings. Does anyone have any idea how I can achieve this?