| # To define library authorizations Normal users have only restricted authorizations in Tools. The authorizations that a group of users, who are linked to a role in an organization, have for a specific library in a company are defined in the library authorizations. They contain a set of sessions that can be used to print, display, maintain, and convert the authorizations for specific dynamically linked libraries. The type of library authorization must also be specified for all library authorizations. For example, authorized or not authorized. Tools uses this data to determine whether a user is authorized to use the functions in a library. If no library authorizations are specified for a user, the user will has no permission at all. You can specify the library authorizations at several levels. For example: At package level. Exceptions can be maintained at module and library level. At module level. This is an exception to the package level, and exceptions can be maintained at library level. At library level. This is an exception to the package level, and exceptions can be maintained at library level. The authorization that is stated at the most specific level has the highest priority. This is the library authorization by library. The lowest priority is the authorization that is stated at the most global level. This is the library authorization by package. Besides the above-mentioned levels, the library authorizations for a user can be specified in several roles. For example, a user has two roles. If one role states that the user has permission for a library, and another role states that the user has no permission, the user will ultimately have permission for that library. Related topics Creating an LN user Defining authorizations To define templates for AMS To define session authorizations To define database authorizations |