@group -? help building back ACL after migrating from core to scale

Hello,

I followed the migration checklist from core to scale and then did a fresh install of scale 24.10.1 after importing my pool and recreating all users and groups that i had with the new range of 3000 to avoid futurs problem, i now have to remap all ACL from all datasets. for the most part i just go to my notes and refer the old user 1001 to the one that match in the new higher number.

where i block is for this expression group@ - ? what does it mean really chatGPT says that it is unsupported group, but how to i figure out what it was. must be important since it has full access

You don’t appear to have an owner group defined for that acl, so the ? is probably telling you that it doesn’t know what group the perms apply to

You can create a group with the required GID or simply change the owning group.

@DjP-iX that sounds about right. thanks

quick follow up question as it looks a bit different from when i create those ACL back in the days.

the way i understood owner in the past was if i put “@owner with full control” in the “access Control List” not the owner the one on the top of the page. Regardless what default access for a folder one user have, if it create a new file, the user have full controll over this file. and same for the primary group of this user if i put owner’s group

the way it shows up when i do it in SCALE, feels like it just put the owner of the whole dataset in this case “Family” will have full access instead of the primary group of the user that create the file.

did the way it handle it changed, or i just never understood it correctly?