Document number: 16218

 

Access Control Lists for databases should not contain long lists of individual names. The standard is to use distribution lists wherever possible. If a group does not exist that fits the purpose, a new group should be created. For additional information, see Eureka! document 12052 — How to use Group Modifications in Northstar web (creating a new group link). The only individual names will be those of the database manager(s) to help with easy identification of whom to contact for help or problems with the database. No groups should be created for the Managers or Designers as only individuals will be given these access levels. For additional information, see Eureka! document 16217 — Access control list (ACL) standards for Lotus Notes database development.

The group name should contain 'db' in addition to the shortened name of the database so people will understand this group is for a specific Notes database. Sometimes the database will naturally have a short name/acronym, like APRD, or the short name will be created from the database title. Group names will typically be hyphenated without spaces. Either the access level or role will follow the hyphen:

'Short Name of the dB + ' dB + access level/role

Examples:

Database Name	Access or Role	Group Name
PSHE Product Consulting Schedule	Authors	PSHE Schedule dB-Authors
Application Product Release Database	Create Bundles	APRD-Create Bundles
Product Strategy Issues & Info	Editors	Product Strategy Issues dB-Editors

 

 

 

 

 

Created by the PeopleSoft Knowledge Management Team.
Copyright © 2003 All rights reserved.
Created: dcb 05/12/2003
Revised: dcb 08/11/2004
Reviewed: 08/11/2004