<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/archiving/tt/Attams2100m000" xml:lang="en">
   <Header>
      <Title>Role Data (ttams2100m000)</Title>
   </Header>
   <AimSection>
      <Paragraph>
         <GUIRef href="" role="manual">Path: // Tools / User Management / Authorization Management System</GUIRef>
      </Paragraph>
      <Paragraph>
         <GUIRef href="" role="manual">Instruction (in operational or 000 company)</GUIRef>
      </Paragraph>
      <ProcedureList>
         <ListItem>In the <GUIRef href="/baanerp/tt/ams/ttams2100m000" role="session">Role Data (ttams2100m000)</GUIRef> session, add a role Archive, as shown
		  below:</ListItem>
         <ListItem>To add table authorization rights to the newly created Archive
		  role, on the Specific menu, point to Table Authorizations, and click Table
		  Authorizations by Company.</ListItem>
         <ListItem>In the Table Authorizations by Company (ttams2100m100) session,
		  click the New button and set Authorization Indicator to Read, as shown below:</ListItem>
         <ListItem>In the <GUIRef href="/baanerp/tt/aad/ttaad2500m000" role="session">User Data (ttaad2500m000)</GUIRef> session, link the Archive role to the users with
		  access to the archive company. <Emphasis>Do not link the Archive role to users
		  responsible for the process of actually archiving data, because those users
		  must be allowed to update the data in the archive
		  company.</Emphasis>
         </ListItem>
         <ListItem>Convert to runtime.</ListItem>
         <ListItem>Assign the role to all users requiring access.</ListItem>
      </ProcedureList>
   </AimSection>
   <Note>
      <SectionTitle>Note</SectionTitle>
      <Paragraph>Because you cannot change the archived data in the archive
		company, you must define the relevant authorizations for the archive company.
		Generally, you are advised to make the archive company read-only for almost all
		users.</Paragraph>
      <Paragraph>Pay special attention when you use sub-roles. Authorizations on
		a sublevel are overruled by authorizations on a higher level. For example, if
		you enter read authorization for all archiving sessions in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef> on level B, but, in level A, you give the user full authorization
		for the WH package, the user can still run an archiving session in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>.</Paragraph>
   </Note>
</ManualTopic>