<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tt/onlinemanual/000054" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">To define session 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 session authorizations that a group of users, who are linked to a role in an organization, have for specific sessions in a company are defined in the <Link href="/baanerp/tt/glossary/glossary#100000" role="glossary">session authorizations</Link>. They contain a set of sessions that can be used to print, display, maintain, and convert the authorizations for specific sessions in a company.</Paragraph>
		<Paragraph class="Default">The type of session authorization must also be specified for all session authorizations. You must at least specify one session authorization type. For example, delete, insert, modify, display, and print. <GUIRef href="/baanerp/tt" role="package">Tools</GUIRef> uses this data to determine if a user is authorized to start a session. The data is also used by the 4GL engine to determine which options are accessible to the user. If no session authorizations are specified for a user, the user has no session permissions at all.</Paragraph>
		<Paragraph class="Default">You can specify the <Link href="/baanerp/tt/glossary/glossary#100000" role="glossary">session authorizations</Link> for specific companies, or for all companies. The authorizations for a specific company have the highest priority.</Paragraph>
		<List><ListIntro>You can specify the session authorizations at several levels. For example:</ListIntro>
			<ListItem>At company level. Exceptions can be maintained at package, module, and session level.</ListItem>
			<ListItem>At package level. This is an exception to the company level, and exceptions can be maintained at module and session level.</ListItem>
			<ListItem>At module level. This is an exception to the company and package level, and exceptions can be maintained at session level.</ListItem>
			<ListItem>At session level. This is an exception to the company, package, and module level.</ListItem>
		</List>
		<Paragraph class="Default">The authorization that is stated at the most specific level has the highest priority. This is the session authorization per session for a specific company. The lowest priority is the authorization that is stated at the most global level. This is the session authorization per company for all companies.</Paragraph>
		<Paragraph class="Default">Besides the already mentioned levels, session authorizations for a user can also be specified in several roles. For example, a user has two roles. If one role states that the user has permission for a session, and the other role states that the user has no permission, the user ultimately has permission for that session.</Paragraph>
		<Paragraph class="Default">The authorizations are time related. You must define the time period in which the users, linked to the role, are authorized to start sessions in <GUIRef href="/baanerp/tt" role="package">Tools</GUIRef>.</Paragraph>
	</GeneralSection>
	<RelatedTopics><SectionTitle>
                              Related topics
                           </SectionTitle>
		<RelTopic><Link href="/baanerp/tt/onlinemanual/000052" role="manual">To define authorizations</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tt/onlinemanual/000055" role="manual">To define database authorizations</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tt/onlinemanual/000053" role="manual">To define templates for AMS</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
