An administrator can define object permissions profiles to hide models, objects, and properties, or make models available in read-only form for users or group of users. By default, all types of models, objects, and properties are available and you hide them (or make them read-only) by adding entries to an object permissions profile.
For detailed information about working with this dialog, see Merging Models. You can repeat this step as many times as necessary to import additional profiles.
In this example, the OOM, DMM, LDM, and PDM are added to the profile to hide them from business users:
In this example, the Application Architecture Diagram and Service Oriented Diagram metaclasses are added to the profile to hide them from business users:
In this example, the entity Code attribute is added to the profile to hide it from business users: