This section contains a sample task list that must be completed to enforce encyclopedia access control to a fictional System Architect user.
Suppose that you need to grant a new employee permission to work on an entity relation diagram, and also to view physical data models. You also need to make it so this new employee does not accidentally execute any of the System Architect macros or menu commands, such as those under the Tools menu, that could impact the work of others.
Though not necessarily in the order shown here, these are the tasks that must be performed before the new employee (named Lia for this example), is allowed to launch System Architect and begin work on the diagram:
•Attach the encyclopedia with the entity relation diagram Lia will work on (named Corporate Data Model 1 for this example).
•Create a user named Lia in System Architect Catalog Manager — without this step, Lia would not be able to see cataloged encyclopedias when she attempts to open encyclopedias in System Architect.
•Create a custom role named Data Modeler-ER Only — to this role you will add the read/write permission to the diagram type entity relation, and add the read permission the diagram type physical data model. You will be able to reuse this role should another data modeler be hired later.
•Assign to Lia the role Data Modeler-ER Only on the Corporate Data Model 1 encyclopedia.
With the above tasks completed, Lia can now launch System Architect and System Architect Catalog Manager will enforce access control on the encyclopedia that she opens. She has read/write access to entity relation diagrams and read permission for physical data models. Lia cannot see any of the other diagrams in the encyclopedia, and she cannot access any options under the System Architect Tools menu.