...
The attribute read
defines a list of permission strings the currently logged-in user must match at least one of. By default such a permission string is the name of a required role. In this example, the user must be assigned to ROLE_DEVELOPER in order to see this form inside the app.
PIPEFORCE URIs as permissions
Status | ||||
---|---|---|---|---|
|
Furthermore, also PIPEFORCE URI prefixes are supported to define permissions such as:
$uri:user:<username> = Logged-in user must have this username.
$uri:group:<groupname> = Logged-in user must be member of group with name <groupname>.
$uri:role:<rolename> = Logged-in user must have assigned this role (this is used by default also if no such prefix is used.)
Example:
Code Block | ||
---|---|---|
| ||
{
...
"permissions": {
"read": ["$uri:group:supervisors"]
}
} |
schema
The schema
attribute defines a PIPEFORCE URI which is called in order to retrieve the Form schema for this form.
...