Previous Topic: Security

Next Topic: Open the Security Manager

Security Management

When you first create the mart, you assign the Administrator security profile to your database user name (the dbo for Microsoft SQL Server or Sybase or the schema owner for Oracle). You can also assign administrator permission to another database user for day-to-day security management.

You can assign users to the predefined security profiles or create customized profiles to fit your environment. You must assign at least one security profile to each user, but you can define an unlimited number of new security profiles and customize the permissions in each profile to manipulate different objects in the mart. For example, you can assign a user to the Architect profile, which grants extensive read or write privileges, in one library and assign the same user to the Viewer profile, which grants no permissions, in a second library.

The following diagram shows the permissions that are granted to the default security profiles:

Security Profile Permissions

The role-based security provides complete control over model access and updates, with the flexibility to restrict users by library, model, subject area, and entity. When you assign a security profile to a user, the user is automatically granted equivalent permissions on all lower-level objects unless you specifically assign that user to a different profile for a specific object class.

As the administrator, you can also add and delete users from the mart. Security administration is performed using Security Manager when you are connected to the mart.