Data Access Control and Stamps in a Global Project

Data Access Control (DAC) and stamps are described in the AVEVA Administrator User Guide. There are a few points to note if using DAC and stamps in a Global project.

• ROLE elements can only be created at the Hub of a Global project: the other DAC elements (Scopes, Access Control Rights, etc.) are created locally. They are not propagated from the Hub.

• The Hub Administrator is responsible for switching Data Access Control on and off for the whole project. Make sure that there are no General users in the project at any location before switching DAC on.

• STAMP elements can only be created at the Hub of a Global project. It is therefore recommended that any satellite primary databases have been synchronised with the Hub before a Stamp is applied.

• The Transfer To Parent and Child functionality fully complies with Data Access Control as applied by the Project Administrator. Transfer To Parent adheres to rules defined by the OpIssue access and Transfer To Child adheres to rules defined by the OpClaim access. If either access is denied, then the operation to Transfer the item will fail.

  Note:
  Remote database queries (refer to Querying Remote Databases) can be used to verify whether databases are up-to-date.

  Note:
  Refer to Database Access Control at Satellites for further detail about satellite DAC administration.