Location: PHPKode > projects > Netautor Professional > netautor/napro4/admin/docu/en/adm_user.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
	<title>Dokumentation | Netautor Professional  | user administration</title>
	<link rel="stylesheet" type="text/css" href="../../../include/docu.css">
</head>

<body>


<a name="page_top"> </a>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
	<td class="menu">
		<font class="menu"><b>application:</b></font>
		<font class="function"><b>user</b></font>
	</td>
	<td align="right" nowrap>
		<span class="link">
		&raquo;&nbsp;<a href="#screen" class="link">Screenshot</a><br>
		</span>
	</td>
</tr>
</table>

<br>

<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
	<td class="text">
		<font class="menu"><b>description:</b></a>
		<br>
		The Netautor user administration is based upon a user/group concept.
		Usind the user administration, all user and group authorizations are configured.
		After installing, the Admin user and System group are available.
		<br>
		The group System is always active and all users are automatically member of this group.
		The possible System settings are identical with possible user and group settings.
		<br>
		Each user gets at least user name and password. This data is saved to the database.
		The password is saved in encrypted form.
		<br>
		A user can be assigned to multiple groups and inerits all group settings (features)
		<br>
		There are several types of features:
		<ol>
			<li><b>Boolean</b> (typically access rights etc.)</li>
			<li><b>Value</b> (string, max. 250 characters)
			<li><b>Multiple Value</b> (multiple string values, each max. 250 characters)
		</ol>
		<br>
		A user first receives the system features, then the features of all groups he is assigned to,
		and then the personal features.
		Following has to be considered:
		<br>
		Boolean features are maintained, if the system or an assigned group hast set the feature to "true".
		<br>
		<br>
		Value features of assigned groups and/or the system are overwritten.
		<br>
		<br>
		When using multiple value features, group and/or system settings are added to the users settings.
		<br>
		<br>
		During installation, the following features are created, and, for a better overview, categorized into several areas:
		<br>
		<br>

			<table border="0" cellspacing="1" cellpadding="4">
				<tr>
					<td colspan="2" class="ft_head">
						<font class="menu"><b>Area Access:</b><br></font>
					</td>
				</tr>
				<tr >
					<td align="right" class="ft_name1">
						Admin
					</td>
					<td class="ft_besch1">
						The user has admin privileges and can access all netautor menus.
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name2"	>ac_schema</td>
					<td class="ft_besch2"				>The user is allowed to manage data schemas</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1"	>ac_layout	</td>
					<td class="ft_besch1"				> 	The user is allowed to create and manage templates</td>
				</tr>
				<tr>
					<td align="right" class="ft_name2"	>ac_import	</td>
					<td class="ft_besch2"				> 	Access to the "Import" application</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1"	>ac_export	</td>
					<td class="ft_besch1"				> 	Access to the "Export" application</td>
				</tr>
				<tr>
					<td align="right" class="ft_name2"	>ac_system	</td>
					<td class="ft_besch1"				> 	Access to the system settings</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1"	>ac_user		</td>
					<td class="ft_besch1"				> 	Access to the user administration</td>
				</tr>
				<tr>
					<td align="right" class="ft_name2"	>ac_db_idx	</td>
					<td class="ft_besch2"				> 	Access to the DB fulltext settings</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1"	>ac_file_idx	</td>
					<td class="ft_besch1"				> 	Access to the Swish-Index settings</td>
				</tr>
				<tr>
					<td align="right" class="ft_name2"	>ac_functions</td>
					<td class="ft_besch2"				> 	Access to the function administration</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1"	>ac_database	</td>
					<td class="ft_besch1"				> 	Access to the database application</td>
				</tr>
				<tr>
					<td align="right" class="ft_name2"	>ac_install	</td>
					<td class="ft_besch2"				> 	Access to the installer</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1"	>ac_workflow	</td>
					<td class="ft_besch1"				> 	Access to the workflow manager</td>
				</tr>
				<tr>
					<td align="right" class="ft_name2"	>ac_queu		</td>
					<td class="ft_besch2"				> 	Access to the Queu manager</td>
				</tr>
				<tr>
					<td colspan="2" class="ft_head">
						<font class="menu"><b>Area Layouts:</b><br></font>
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1"	>create_given_layout_id</td>
					<td class="ft_besch1"				>allows specifying layout ids for new layouts.</td>
				</tr>
				<tr>
					<td align="right" class="ft_name2"	>layout_source_path</td>
					<td class="ft_besch2"				>
						Path to the template sources which can then be edited in the file system.
						This allows usage of version control systems and also allows using any editor for accessing the layouts.
					</td>
				</tr>
				<tr>
					<td colspan="2" class="ft_head">
						<font class="menu"><b>Area Mediapool:</b></font>
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1">display_path</td>
					<td class="ft_besch1">
						Is used to define the media pool.
						A directory is specifiedm where data is located, which is used by multi media fields (see schema manager).
						<br>
						example : images=/var/daten/images/klaus/
						<br>
						Multiple pools can be defined.
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name2">upload_path</td>
					<td class="ft_besch2">
						Defines a directory where uploaded files are stored.
						<br>
						example: images=/var/daten/images/klaus/
						<br>
						In this example, files are uploaded into the directory which also is used for displaying them.
						<br>
						Separating these directories is usefull, if files should be converted to another format after upload,
						or using any other workflow functions.

					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1">filefilter</td>
					<td class="ft_besch1">
						Filefilter for displaying files in the gallery used for multimedia fields.
						<br>
						example: .gif
						<br>
						(shows only .gif files).
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name2">show_subtree</td>
					<td class="ft_besch2">
						Specifies, if sub directories of a media pool should be displayed.
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1">run_script</td>
					<td class="ft_besch1">
						Specifies a name für an URL which should be called after uploading a file.
						<br>
						example_: gallery=http://servername/netautor/napro4/scan/proc.php?configfile=upload
						<br>
						<br>
						This allows e.g. starting workflow scripts after uploading an image.
					</td>
				</tr>
				<tr>
					<td colspan="2" class="ft_head">
						<font class="menu"><b>Area Java:</b></font>
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1">use_plugin</td>
					<td class="ft_besch1">
						Specifies if the Java Plugin for the integrated Java text editor should be used.
					</td>
				</tr>
				<tr>
					<td colspan="2" class="ft_head">
						<font class="menu"><b>Area Third Party:</b></font>
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1">IMG-PATH</td>
					<td class="ft_besch1">
						Path to the program "convert" (part of ImageMagick) which is used for converting images.
						This settings is especially important for Windows systems, where the programm path normally ist
						not set in the PATH environment variable.
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1">SWEXE</td>
					<td class="ft_besch1">
						Path to the programm "Swish" which is used for creating indexes of text files.
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name2">index_path</td>
					<td class="ft_besch2">
						Directory where the index creted by "Swish" should be stored.
					</td>
				</tr>
				<tr>
					<td colspan="2" class="ft_head">
						<font class="menu"><b>Area System:</b></font>
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1">Timeformat</td>
					<td class="ft_besch1">
						Default time format.
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name2">Dateformat</td>
					<td class="ft_besch2">
						Default date format.
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1">Initialdoc</td>
					<td class="ft_besch1">
						Document which should be opened after successful login.
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name2">Debug-Level</td>
					<td class="ft_besch2">
						Specifies verbosity of debug information .
					</td>
				</tr>
				<tr>
					<td align="right" class="ft_name1">checkdate</td>
					<td class="ft_besch1">
						Specifies which date should be when checking using npf_results.
						Can be "auto" or a date in format "dd.mm.YYYY".
						For more details see "npf_results" documentation.
					</td>
				</tr>
			</table>
	</td>
</tr>
<tr>
	<td class="text" align="right">
		<a href="#page_top" class="menu"><img src="../../../grafik/button_top.gif" border="0"></a><br>
		<img src="../../../grafik/pixel.gif" width="1" height="4"><br>
	</td>
</tr>
<tr>
	<td class="line"><img src="../../../grafik/pixel.gif" width="1" height="1"></td>
</tr>
</table>

<br>

<a name="screen"> </a>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
	<td class="text">
		<font class="menu"><b>Screenshot:</b></font>
		<br>
		<img src="../../../grafik/pixel.gif" width="1" height="4"><br>
		<img src="../../../grafik/en/docu/adm_user.jpg" width="723" height="509"><br>
		<br>
		
		<table width="732" class="text">
		<tr>
			<td width="350" valign="top">
				<ol type="1">
					<li value="1" class="screenshot">
						<b>Name</b>
						<br>
						User/group name.<br>
						<br>
					</li>
					<li value="2" class="screenshot">
						<b>E-Mail</b>
						<br>
						User's e-mail address.<br>
						<br>
					</li>
					<li value="3" class="screenshot">
						<b>Password</b>
						<br>
						Input field for the password.
						Has to be entered a second time for control.
						Also groups need a password, although it is not used.<br>
						<br>
					</li>
					<li value="4" class="screenshot">
						<b>Remark</b>
						<br>
						More user information.<br>
						<br>
					</li>
					<li value="5" class="screenshot">
						<b>groups</b>
						<br>
						Selection field to assign a user to one or more groups.
						A user is assigned to alle selected groups.
						Select multiple groups by holding the CTRL key.<br>
						<br>
					</li>
					<li value="6" class="screenshot">
						<b>Active</b>
						<br>
						Specifies if a user is active.
						Only active users can login.<br>
						<br>
					</li>
					<li value="7" class="screenshot">
						<b>Group</b>
						<br>
						To select if a user is a group or a single user.<br>
						<br>
					</li>
				</ol>
			</td>
			<td width="27" valign="top">
				<img src="../../../grafik/pixel.gif" width="27" height="1"><br>
			</td>
			<td width="355" valign="top">
				<ol type="1">
					<li value="8" class="screenshot">
						<b>save</b>
						<br>
						Creates or updates a user or group.<br>
						<img src="../../../grafik/pixel.gif" width="1" height="6"><br>
						<b>Clear form</b>
						<br>
						Clears the form.<br>
						<img src="../../../grafik/pixel.gif" width="1" height="6"><br>
						<b>delete</b>
						<br>
						deletes the open user or group<br>
						<br>
					</li>
					<li value="9" class="screenshot">
						<b>Area</b>
						<br>
						name of the area to show its settings.<br>
						<br>
					</li>
					<li value="10" class="screenshot">
						<b>Presettings (Rights / Features)</b>
						<br>
						feature-list to manage user/group authorizations.<br>
						<br>
					</li>
					<li value="11" class="screenshot">
						<b>Groups</b>
						<br>
						Displays a list of all available groups.<br>
						<br>
					</li>
					<li value="12" class="screenshot">
						<b>User</b>
						<br>
						Displays a list of all available users.<br>
						<br>
					</li>
					<li value="13" class="screenshot">
						<b>Work on Group/User</b>
						<br>
						A seperate area to assign multiple users to one or more groups.<br>
						<br>
					</li>
				</ol>
			</td>
		</tr>
		</table>
	</td>
</tr>
<tr>
	<td class="text" align="right">
		<a href="#page_top" class="menu"><img src="../../../grafik/button_top.gif" border="0"></a><br>
		<img src="../../../grafik/pixel.gif" width="1" height="4"><br>
	</td>
</tr>
<tr>
	<td class="line"><img src="../../../grafik/pixel.gif" width="1" height="1"></td>
</tr>
</table>

<br>
<!--
<table border="0" cellpadding="0" cellspacing="5" width="100%">
<tr>
	<td class="text">
		<font class="menu"><b>Related:</b></font>
	</td>
	<td class="text" align="right">
		<a href="#page_top" class="menu"><img src="../../../grafik/button_top.gif" border="0"></a><br>
		<img src="../../../grafik/pixel.gif" width="1" height="4"><br>
	</td>
</tr>
<tr>
	<td class="line" colspan="2"><img src="../../../grafik/pixel.gif" width="1" height="1"></td>
</tr>
</table>
-->
<a name="ende"> </a>




</body>
</html>
Return current item: Netautor Professional