<?xml version="1.0" encoding="iso-8859-1"?>
<!-- >e-novative> DocBook Environment (eDE)                                  -->
<!-- (c) 2002 e-novative GmbH, Munich, Germany                               -->
<!-- http://www.e-novative.de                                                -->
<!-- DocBook article template                                                -->
<!-- This file is part of eDE                                                -->
<!-- eDE is free software; you can redistribute it and/or modify             -->
<!-- it under the terms of the GNU General Public License as published by    -->
<!-- the Free Software Foundation; either version 2 of the License, or       -->
<!-- (at your option) any later version.                                     -->
<!-- eDE is distributed in the hope that it will be useful,                  -->
<!-- but WITHOUT ANY WARRANTY; without even the implied warranty of          -->
<!-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the           -->
<!-- GNU General Public License for more details.                            -->
<!-- You should have received a copy of the GNU General Public License       -->
<!-- along with eDe; if not, write to the Free Software                      -->
<!-- Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA -->
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "file:/c:/docbook/dtd/docbookx.dtd">
  <article lang="en">
    <articleinfo>
      <title>NvWebAdmin</title>
      <pubdate>2007</pubdate>
      <copyright>
        <year>2007</year>
        <holder>New Voice International AG</holder>
      </copyright>
    </articleinfo>
    <sect1 id="introduction">
      <title>Introduction</title>
      <para>
        With this application the web environment will be configured
      </para>
    </sect1>
    <sect1 id="user">
      <title>Users</title>
      <para>
        This section describes how to configure and administrate web users
      </para>
      <sect2 id="user_overview">
        <title>Overview of all web users</title>
        <para role="intro">
        </para>
        <para role="inline">
          Overview of all web users. Each entry is clickable and redirects
          to the detail page of the profile.
        </para>
        <para role="info">
        </para>
      </sect2>
      <sect2 id="user_create">
        <title>Creating a new web user</title>
        <para role="intro">
        </para>
        <para role="inline">
          Create a new web user by givin his real name (Real User Name)
          along with its Login name, that he will use to login to the web
          applications.
        </para>
        <para role="info">
        </para>
      </sect2>
      <sect2 id="user_detail">
        <title>View and modify user details</title>
        <para role="intro">
        </para>
        <para>View and modify user details ...</para>
        <sect3 id="user_detail_account">
          <title>User name and login</title>
          <para role="inline">By pressing "Delete" the shown web account can be deleted.</para>
          <para role="inline">It's also possible to change the login and user name before pressing "Change".</para>
          <para role="inline">Description of the input fields:</para>
          <para role="inline">- "Name" is (usually) the real and full name of the web user</para>
          <para role="inline">- "Login" is the name that the user will enter to get access to the web</para>
        </sect3>
        <sect3 id="user_detail_passwd">
          <title>Re-setting a password</title>
          <para role="inline">Change or set a new password of the user here. In order to be sure the entered password is correct, it has to be retyped before pressing "Set".</para>
          <para role="inline">Whenever a new password is assigned (and a possible old one overridden), the user will be forced to change it again during the next login.</para>
          <para role="inline">Description of the input fields:</para>
          <para role="inline">- "New Password" has to be filled with the new password</para>
          <para role="inline">- "Repetition" has to be filled with the same new password to check correct input</para>
        </sect3>
        <sect3 id="user_detail_profile">
          <title>Assigning a profile</title>
          <para role="inline">Assign a profile to the current user here. The user will implicitely have the rights that are assigned to the selected profile.</para>
          <para role="inline">Description of the shown profile values:</para>
          <para role="inline">- "Max. Idle Time" defines the maximum time of inactivity after which any further action will require to pass through the login page again.</para>
          <para role="inline">- "Max. Session Time" defines the maximum duration after which the user needs to login again.</para>
          <para role="inline">- "Password Life Time" defines the number of days after which the user needs to change his password again.</para>
        </sect3>
        <para role="info">
        </para>
      </sect2>
    </sect1>
    <sect1 id="profile">
      <title>Profiles</title>
      <para>
        This section describes the use of profiles and how to configure
        them
      </para>
      <sect2 id="profile_tree">
        <title>Profile tree</title>
        <para role="intro">
        </para>
        <para role="inline">
          The profile on top of the tree is your own profile from where
          all others will inherit the settings and rights. All profiles,
          except your own, can be changed and adapted as needed. Please be
          aware that modifying one profile will directly impact others too
          and especially access rights of profile childern may be
          completely different afterwards
        </para>
        <para role="info">
        </para>
      </sect2>
      <sect2 id="profile_creation">
        <title>Profile creation</title>
        <para role="intro">
        </para>
        <para role="inline">
          Create a new web profile by giving it a name (doesn't need to be
          unique). The new profile will be attached to the given parent
          profile.
        </para>
        <para role="info">
        </para>
      </sect2>
      <sect2 id="profile_setting">
        <title>Profile settings</title>
        <para role="intro">
        </para>
        <para role="inline">
          The profile settings will be used to contol all the assigned web
          users. Some of the settings just act as default values as long
          as the web user is not overriding it.
        </para>
        <para role="info">
        </para>
      </sect2>
      <sect2 id="profile_deletion">
        <title>Profile deletion</title>
        <para role="intro">
        </para>
        <para role="inline">
          By confirming the deletion of the profile, it will be
          permanently removed. Here is also the last chance to avoid it.
        </para>
        <para role="info">
        </para>
      </sect2>
    </sect1>
    <sect1 id="application">
      <title>Applications</title>
      <para>
        This section describes how to configure and use the access control
        rights
      </para>
      <sect2 id="application_list">
        <title>Application settings</title>
        <para role="intro">
        </para>
        <para role="inline">
          Define here the Execution and Administration rights for each web
          application of the selected profile. When giving the "YES" right
          it will be automatically inherited by the sub-profiles. In order
          to stop this inheritance, give the right "YES stop inherit". The
          right "NO" is automatically inherited by the sub-profiles. The
          rights "Inherited YES" and "Inherited NO" mean that the right
          has been inherited from it's parent profile.
        </para>
        <para role="info">
        </para>
      </sect2>
    </sect1>
    <sect1 id="mobilisation">
      <title>Mobilisation</title>
      <para>
        This section describes how to configure the mobilisation access
        control rights
      </para>
      <sect2 id="mobilisation_alarm">
        <title>Alarm access rights</title>
        <para role="intro">
        </para>
        <para>Alarm access rights ...</para>
        <sect3 id="mobilisation_alarm_acl">
          <title>Pattern assignment of the different alarm rights</title>
          <para role="inline">
            Pattern assignment of the different alarm rights. For each
            section below (Allow Viewing, Allow Modification, Allow
            Creation, Allow Deletion and Allow Execution), the left list
            contain the patterns of alarms the current profile has the
            right to view, modify, create, delete or execute. The right
            lists contain the existing patterns left.
          </para>
        </sect3>
        <sect3 id="mobilisation_alarm_pat">
          <title>Pattern definition for the alarm rights</title>
          <para role="inline">
            The left section (Allow Administration) defines the patterns
            that the current selected profile (except for the currently
            logged in profile) will be able to manage. For example a
            profile that has the right to manage the patterns "50*" will
            only be able to give to himself and his sub-profiles the right
            to manipulate alarms starting with "50" like 5002 or 5089. The
            right section allows to create new patterns or to delete
            existing ones.
          </para>
        </sect3>
        <para role="info">
        </para>
      </sect2>
      <sect2 id="mobilisation_group">
        <title>Group access rights</title>
        <para role="intro">
        </para>
        <para>Group access rights ...</para>
        <sect3 id="mobilisation_group_acl">
          <title>Pattern assignment of the different group rights</title>
          <para role="inline">
            Pattern assignment of the different group rights. For each
            section below (Allow Viewing, Allow Modification, Allow
            Creation, Allow Deletion and Allow Execution), the left list
            contain the patterns of groups the current profile has the
            right to view, modify, create, delete or execute. The right
            lists contain the existing patterns left.
          </para>
        </sect3>
        <sect3 id="mobilisation_group_pat">
          <title>Pattern definition for the group rights</title>
          <para role="inline">
            The left section (Allow Administration) defines the patterns
            that the current selected profile (except for the currently
            logged in profile) will be able to manage. For example a
            profile that is given the right to manage the patterns "2*"
            will only be able to give to himself and his sub-profiles the
            right to manipulate groups whose number starts with "2" like
            21 or 29. The right section allows to create new patterns or
            to delete existing ones.
          </para>
        </sect3>
        <para role="info">
        </para>
      </sect2>
      <sect2 id="mobilisation_department">
        <title>Department access rights</title>
        <para role="intro">
        </para>
        <para>Department access rights ...</para>
        <sect3 id="mobilisation_department_acl">
          <title>
            Pattern assignment of the different department rights
          </title>
          <para role="inline">
            Pattern assignment of the different department rights. For
            each section below (Allow Viewing, Allow Modification, Allow
            Creation, Allow Deletion and Allow Execution), the left list
            contain the patterns of departments the current profile has
            the right to view, modify, create, delete or execute. The
            right lists contain the existing patterns left.
          </para>
        </sect3>
        <sect3 id="mobilisation_department_pat">
          <title>Pattern definition for the department rights</title>
          <para role="inline">
            The left section (Allow Administration) defines the patterns
            that the current selected profile (except for the currently
            logged in profile) will be able to manage. For example a
            profile that is given the right to manage the patterns
            "Section1" will only be able to give to himself and his
            sub-profiles the right to manipulate persons working in the
            department "Section1". The right section allows to create new
            patterns or to delete existing ones.
          </para>
        </sect3>
        <para role="info">
        </para>
      </sect2>
      <sect2 id="mobilisation_schedule">
        <title>Schedule access rights</title>
        <para role="intro">
        </para>
        <para>Schedule access rights ...</para>
        <sect3 id="mobilisation_schedule_acl">
          <title>
            Pattern assignment of the different department rights
          </title>
          <para role="inline">Pattern assignment of the different schedule plan rights. For each section below (Allow Viewing, Allow Modification, Allow Creation and Allow Deletion), the left list contains the patterns of the schedule plans that are allowed to view, modify, create and delete by the current profile. The right lists contain the remaining and unassigned patterns.</para>
        </sect3>
        <sect3 id="mobilisation_schedule_pat">
          <title>Pattern definition for the department rights</title>
          <para role="inline">The left section (Allow Administration) defines the patterns that the current selected profile (except for the currently logged in profile) will be able to manage. For example a profile that is given the right to manage the patterns "Section1" will only be able to give to himself and his sub-profiles the right to manipulate persons working in the department "Section1".</para>
          <para role="inline">The right section allows to create new patterns or to delete existing ones.</para>
        </sect3>
        <para role="info">
        </para>
      </sect2>
    </sect1>
    <sect1 id="licence">
      <title>Licence information</title>
      <para>
        This section just explains licence information and its activation
        (e.g. used by the support)
      </para>
      <sect2 id="licence_overview">
        <title>Licence overview</title>
        <para role="intro">
        </para>
        <para role="inline">
        </para>
        <para role="info">
        </para>
        <sect3 id="licence_version">
          <para role="inline"/>
        </sect3>
        <sect3 id="licence_serialno">
          <para role="inline"></para>
          <para role="inline"/>
          </sect3>
          <sect3 id="licence_packages">
          <para role="inline"/>
          </sect3>
          <sect3 id="licence_aclrights">
          <para role="inline"/>
          </sect3>
      </sect2>
    </sect1>
  </article>
  