Groups¶
A group models the access control list (ACL) for different resources. A group represents a set of users with permissions for accessing to an object. E.g. A user can be granted to modify Workflow Tasks; however, this user will just allowed to do it if this Task belongs to one of his groups; so, we are protecting instances of a resource to be edited by other users.
Groups can be part of a system configuration for an application.
All groups created by a user must be assigned to an specific application; for custom groups (not IsSystem) the Key must starts by the ApplicationKey+"."
All applications have to define a group with the name Public. This is used as a default group; this is commonly used to protect actions in controllers where ACLs concept is not implemented.
| Property | Description |
|---|---|
| Key | String. Unique Key. Required Original implementation was defining the Id as integer. In the new implementation we need to convert it to string to |
| ApplicationKey | String. Application.Key where this group is defined. Required |
| Name | String. Friendly name to refer the Application. Optional |
| AutomaticallyCreated | Boolean. Flags if this group manages automatically created users. |
| IsSystem | Boolean. Flags if this group is defined by the system or customized by the user. Required. System groups cannot be edited using the Security UI. |
How to manage groups¶
Roles can be managed from the API resource \Authentication\Groups and also from Administration website (/applications/{ApplicationKey}/groups). Both offers the same functionality and are protected by securable Sec.Group.
API¶
Administration site¶
