MKS Implementer 2006 Administration Guide

In the IFS file owner field, type QNOTES.
3 Press ENTER.
Lotus Domino Integration
4 Repeat these steps for each *PRD, *TST, and *QAC environment defined for this feature.
Defining ACL Directives
You define the ACL directives as a series of commands, either in a source physical file
(maintainable with SEU) or in the Implementer promotion request comments. You should
use a source physical file when the directives are static or unchanging and apply to one or
more Notes databases in an environment. This recommended method provides maximum
control when assigning ACL access rights. For examples of this method, see page 346.
When the directives are more dynamic and varying in nature, you can use the Implementer
promotion request comments; however, this method renders less control due to its free-form
structure.
For setting an ACL in check out, you must define the directives in a source physical file
member. The format of the directives is as follows:
where:
**STRDOMACL
addrole
removerole
removeallrole
addacl :::
removeacl
removeallacl
**ENDDOMACL
NOTE The **STRDOMACL and **ENDDOMACL markers are only used when the ACL
directives are embedded in the promotion request comments.
Value Description
Domino access identifier the ACL applies to.
= Domino access identifier type being set. Valid values are mixedgroup, person,
persongroup, server, servergroup, and unspecified. This value is validated.
Access level to grant. Valid values are noaccess, depositor, reader, author, editor,
designer, and manager. This value is validated.
Comma-delimited list of roles to assign to the ACL entry. If the role does not exist
for the ACL it is added automatically.
345