<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tt/onlinemanual/000056" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">To define library authorizations</Title>
		<Keyword ContextSensitive="No"><Level1>User authorizations</Level1>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>Roles</Level1>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph class="Default">Normal users have only restricted authorizations in <GUIRef href="/baanerp/tt" role="package">Tools</GUIRef>. 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 <Link href="/baanerp/tt/glossary/glossary#100003" role="glossary">library authorizations</Link>. They contain a set of sessions that can be used to print, display, maintain, and convert the authorizations for specific <Link href="/baanerp/tt/glossary/glossary#dll.tt" role="glossary">dynamically linked</Link> libraries.</Paragraph>
		<Paragraph class="Default">The type of library authorization must also be specified for all <Link href="/baanerp/tt/glossary/glossary#100003" role="glossary">library authorizations</Link>. For example, authorized or not authorized. <GUIRef href="/baanerp/tt" role="package">Tools</GUIRef> 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.</Paragraph>
		<List><ListIntro>You can specify the library authorizations at several levels. For example:</ListIntro>
			<ListItem>At package level. Exceptions can be maintained at module and library level.</ListItem>
			<ListItem>At module level. This is an exception to the package level, and exceptions can be maintained at library level.</ListItem>
			<ListItem>At library level. This is an exception to the package level, and exceptions can be maintained at library level.</ListItem>
		</List>
		<Paragraph class="Default">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.</Paragraph>
		<Paragraph class="Default">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.</Paragraph>
	</GeneralSection>
	<RelatedTopics><SectionTitle>
                              Related topics
                           </SectionTitle>
		<RelTopic><Link href="/baanerp/tt/onlinemanual/000051" role="manual">To create an ERP LN user</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tt/onlinemanual/000052" role="manual">To define authorizations</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tt/onlinemanual/000053" role="manual">To define templates for AMS</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tt/onlinemanual/000054" role="manual">To define session authorizations</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tt/onlinemanual/000055" role="manual">To define database authorizations</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
