chore: automated commit

This commit is contained in:
munja 2022-07-09 23:48:49 +01:00
parent 0acbd660f5
commit 5e63360b35
2 changed files with 5 additions and 0 deletions

View File

@ -9,6 +9,10 @@ og_image: https://docs.datacontroller.io/img/cls_table.png
Column level security is implemented by mapping _allowed_ columns to a list of SAS groups. In VIEW mode, only allowed columns are visible. In EDIT mode, allowed columns are _editable_ - the remaining columns are read-only. Column level security is implemented by mapping _allowed_ columns to a list of SAS groups. In VIEW mode, only allowed columns are visible. In EDIT mode, allowed columns are _editable_ - the remaining columns are read-only.
Below is an example of an EDIT table with only one column enabled for editing:
![lockanytable example](/img/cls_example.png)
## Configuration ## Configuration
The variables in MPE_COLUMN_LEVEL_SECURITY should be configured as follows: The variables in MPE_COLUMN_LEVEL_SECURITY should be configured as follows:
@ -35,6 +39,7 @@ The SAS Group to which the rule applies. The user could also be a member of a [
- If a user is in ANY of the groups, the columns will be restricted. - If a user is in ANY of the groups, the columns will be restricted.
- If a user is in NONE of the groups, no restrictions apply (all columns available). - If a user is in NONE of the groups, no restrictions apply (all columns available).
- If a user is in MULTIPLE groups, they will see all allowed columns across all groups. - If a user is in MULTIPLE groups, they will see all allowed columns across all groups.
- If a user is in the [Data Controller Admin Group](/dcc-groups/#data-controller-admin-group), CLS rules DO NOT APPLY.
### CLS_LIBREF ### CLS_LIBREF
The library of the target table against which the security rule will be applied The library of the target table against which the security rule will be applied

BIN
docs/img/cls_example.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 444 KiB