An administrator can create profiles in the repository to customize and simplify the PowerDesigner interface for users by hiding types of models, objects, and object properties, by reconfiguring menus, toolbars, and toolboxes, and by setting appropriate defaults for options and preferences. You can define multiple profiles to customize the interface in different ways for different kinds of users and apply them as appropriate to individual user accounts or to repository groups.
Three types of profiles are available to administrators to customize the PowerDesigner interface for users:
- Object permissions profiles - to hide types of models or make them read-only, and to hide model objects and object properties. Use these profiles to simplify the modeling environment by presenting users with only the concepts that they need:
- Hiding a module - prevents the creation or opening of models of this type.
- Hiding an object - removes it from the Toolbox, Browser, Model menu, New contextual menu, and property sheets.
- Hiding an attribute or collection - removes it from object symbols and property sheets.
- UI preferences profiles - to customize the commands available in menus, toolbars, and toolboxes. Use these profiles to reorganize and simplify the PowerDesigner interface for users. They provide the same kind of customization as users can perform using the command (see Customizing Menus, Toolbars, and Toolboxes).
- General preferences profiles - to set default display preferences and model and general options. Use these profiles to guide users toward making appropriate option and preference choices. They provide the same kind of customization as users can perform using user profiles (see User Profiles).
Note: Permissions profiles are enforced (the user cannot access types of models or objects that are hidden from her), but UI and general preference profiles provide only defaults, which can be overridden by the user. The defaults can be reapplied at any time using the command (see
Applying a User Profile).