Uses of Package
com.kingsrook.qqq.backend.core.actions.permissions

Packages that use com.kingsrook.qqq.backend.core.actions.permissions

Package	Description
com.kingsrook.qqq.backend.core.actions.ai.tools
com.kingsrook.qqq.backend.core.actions.permissions
com.kingsrook.qqq.backend.core.jobs.progress
com.kingsrook.qqq.backend.core.model.actions
com.kingsrook.qqq.backend.core.model.actions.tables.query
com.kingsrook.qqq.backend.core.model.metadata.permissions

Classes in com.kingsrook.qqq.backend.core.actions.permissions used by com.kingsrook.qqq.backend.core.actions.ai.tools

Class	Description
TablePermissionSubType

Classes in com.kingsrook.qqq.backend.core.actions.permissions used by com.kingsrook.qqq.backend.core.actions.permissions

Class	Description
AvailablePermission
CorePermissionEnforcer.AuthorizedScope	AutoCloseable handle on an authorized action scope.
CustomPermissionChecker	For special cases of applying permissions, an application can implement a custom permission checker via this interface - and place it on a table, process, report, app, or widget via QPermissionRules.withCustomPermissionChecker(QCodeReference).
PermissionCheckResult
PermissionEnforcement	How a core action (Query, Get, Count, Aggregate, Insert, Update, Delete, Replace, RunProcess, RenderWidget, GenerateReport, Export) should treat table/process/widget/report permissions and field security locks for the current session.
PermissionSubType
TablePermissionSubType
UseOtherPermissionNameCustomPermissionChecker	Simple implementation of a Custom Permission Checker, that takes a permissionName property, and just checks if the session has that permission.
UseTablePermissionCustomPermissionChecker	Simple implementation of a Custom Permission Checker, that takes tableName and TablePermissionSubType name properties, and checks if the session has that table-permission-sub-type for the specified table name.

Classes in com.kingsrook.qqq.backend.core.actions.permissions used by com.kingsrook.qqq.backend.core.jobs.progress

Class	Description
CustomPermissionChecker	For special cases of applying permissions, an application can implement a custom permission checker via this interface - and place it on a table, process, report, app, or widget via QPermissionRules.withCustomPermissionChecker(QCodeReference).

Classes in com.kingsrook.qqq.backend.core.actions.permissions used by com.kingsrook.qqq.backend.core.model.actions

Class	Description
PermissionEnforcement	How a core action (Query, Get, Count, Aggregate, Insert, Update, Delete, Replace, RunProcess, RenderWidget, GenerateReport, Export) should treat table/process/widget/report permissions and field security locks for the current session.

Classes in com.kingsrook.qqq.backend.core.actions.permissions used by com.kingsrook.qqq.backend.core.model.actions.tables.query

Class	Description
CustomPermissionChecker	For special cases of applying permissions, an application can implement a custom permission checker via this interface - and place it on a table, process, report, app, or widget via QPermissionRules.withCustomPermissionChecker(QCodeReference).

Classes in com.kingsrook.qqq.backend.core.actions.permissions used by com.kingsrook.qqq.backend.core.model.metadata.permissions

Class	Description
TablePermissionSubType