Hi
The 'access' field is obsoleted and not
planned to implement for Klish 3.
The Klish 3 will get nested COND tag
for the similar task. Unfortunately it's planned but not
implemented yet. It will work like 'access' but dynamically. The
documentation has a description for the COND.
Right now you can use multi-ACTIONs to
restrict access.
<COMMAND name="my command"...>
<ACTION sym="my_check_access"/>
<ACTION ...>#real action
here</ACTION>
</COMMAND>
If the first ACTION returns not-null
return code it considered as failed. By default if the first
ACTION failed the second will not be executed. The difference
between unimplemented COND and checking ACTION is the restricted
user can get help and completion for this command. In a case of
COND user will not see such command at all.
The multi-ACTION works for the COMMAND
but don't works for the whole VIEW.