What does scoped ACL mean?

[Harshit Sharma1]

If we create ACLs on a table within a scoped application, will those ACL checks apply only if the user is in the scope of the table? If user is in some other scope, will access to whole table will be restricted even if user has roles for CRUD on the table?

[Maik Skoddow]

You are mixing topics. A user cannot be in the scope of a table. Therefore, you can skip this for your considerations regarding ACLs. Instead a user has roles and these roles have to be granted in your scoped application. That's it in a simple way.

[Maddysunil]

@Harshit Sharma1 

Access Control Lists (ACLs) define the permissions and restrictions for records and fields within tables. When ACLs are created on a table within a scoped application, they typically apply only within the scope of that application. This means that the ACL checks will apply to users who are operating within the scope of the table governed by the ACL.

If a user is in a different scope, the ACLs defined within another scoped application won't directly apply to them. However, the overall access to the table might still be controlled by other factors such as roles assigned to the user.

So, if a user is in a different scope and they have roles granting them CRUD (Create, Read, Update, Delete) access to the table, they should still have access to the table as permitted by those roles, unless there are specific ACLs or other restrictions in place that limit their access further.

In summary, ACLs within a scoped application primarily affect users within that scope, but the overall access to the table may also be influenced by roles and permissions outside the scope.

Please Mark ✅Correct if this solves your query and also mark 👍Helpful if you find my response worthy based on the impact.

Thanks

[Abhay Kumar1]

@Harshit Sharma1  have you got any answer in this, if yes pls share other let me know if not as i can help you with live scenario,thanks