You can filter schema access to specific users, depending on their permissions. System filters let you manage the read and write permissions of entities detailed in schemas, using readAccess and writeAccess parameters.
This restriction applies only to non technical users: a technical user, with related permissions, or using a workflow, will be able to retrieve and update data.
readAccess: provides read only access to schema data.
Warning - All linked tables must be set with the same restriction. This configuration can impact performances.
writeAccess: provides write access to schema data.
These filters are entered at the main element level of the schemas and, as shown in the following examples, can be formed to restrict access.
Restrict WRITE permissions
Here, the filter is used to disallow WRITE permissions on the schema for operators without the ADMINISTRATION permission. This means that only administrators will have write permissions on entities described by this schema.
<sysFilter name="writeAccess"> <condition enabledIf="hasNamedRight('admin')=false" expr="FALSE"/> </sysFilter>
Restrict READ and WRITE permissions:
Here, the filter is used to disallow both READ and WRITE permissions on the schema for all operators. Only the internal account, represented by the expression “$(loginId)!=0”, has these permissions.
<sysFilter name="readAccess"> <condition enabledIf="$(loginId)!=0" expr="FALSE"/> </sysFilter> <sysFilter name="writeAccess"> <condition enabledIf="$(loginId)!=0" expr="FALSE"/> </sysFilter>
Possible expr attribute values used to define the condition are TRUE or FALSE.
If no filter is specified, all operators will have read and write permissions to the schema.
By default, built-in schemas are only accessible with WRITE permissions for operators with ADMINISTRATION rights:
READ and WRITE permissions for the xtk:sessionInfo schema are only accessible by the internal account of an Adobe Campaign instance.
You can still modify the system filters of the out-of-the-box schemas which are by default protected due to compatibility issues with older versions.
However, Adobe recommends you not to modify the default parameters to guarantee optimal security.
<sysfilter name="<filter name>" _operation="delete"/>in the main element to delete application of the filter under the same in the origin schema.