KTS-2685

"Update Onscreen Help" Updated. Added new content from manuals (provided by Carolyn) Committed By: Philip Arkcoll Reviewed By: git-svn-id: https://kt-dms.svn.sourceforge.net/svnroot/kt-dms/trunk@8736 c91229c3-7414-0410-bfa2-8a42b809f60b

KTS-2685
"Update Onscreen Help" Updated. Added new content from manuals (provided by Carolyn) Committed By: Philip Arkcoll Reviewed By: git-svn-id: https://kt-dms.svn.sourceforge.net/svnroot/kt-dms/trunk@8736 c91229c3-7414-0410-bfa2-8a42b809f60b
Philip Arkcoll
1 parent ce3cad44
Showing 18 changed files with 582 additions and 168 deletions
kthelp/ktcore/EN/admin/admin-mode.html
kthelp/ktcore/EN/admin/archived documents.html
kthelp/ktcore/EN/admin/authentication sources.html
kthelp/ktcore/EN/admin/automatic workflows.html
kthelp/ktcore/EN/admin/control units.html
kthelp/ktcore/EN/admin/deleted documents.html
kthelp/ktcore/EN/admin/document checkout.html
kthelp/ktcore/EN/admin/document fieldsets.html
kthelp/ktcore/EN/admin/document types.html
kthelp/ktcore/EN/admin/dynamic conditions.html
kthelp/ktcore/EN/admin/help administration.html
kthelp/ktcore/EN/admin/link type management.html
kthelp/ktcore/EN/admin/manage groups.html
kthelp/ktcore/EN/admin/manage permissions.html
kthelp/ktcore/EN/admin/manage plugins.html
kthelp/ktcore/EN/admin/manage users.html
kthelp/ktcore/EN/admin/role administration.html
kthelp/ktcore/EN/admin/system information.html
@@ -6,14 +6,28 @@
  
 <body>
  
-<h2>Administrator Mode</h2>
 <p>
-There are instances where systems administrators may be denied access to certain documents in the repository - management level documents containing classified information, for example.
+Administrator mode is a system state that allows KnowledgeTree administrative users to override the permissions system, in an audited fashion, in order to access all documents in the system. With administrator mode enabled, Unit administrators will only be provided access to all documents in their Unit. 
 </p>
+<br />
 <p>
-However, because problems with these documents in the repository will also need to be fixed, administrators must be granted a way of overriding the controls in an audited manner that protects this information. 
-</p><p>
-Enabling Administrator mode allows system and unit administrators to view and manage all documents in the system, including those documents where they are normally denied access. 
+Administrator mode provides an audited method of fixing errors on documents or in folders where even administrative users are usually denied access, such as content containing classified information. 
+</p>
+<br />
+<p>
+Note: Administrators are not able to delete immutable documents using the 'Delete' button in Browse Documents, even if they're working in Administrator mode. To delete an immutable document, use the 'Delete' action from the immutable document's Document Detail page. This ensures that immutable documents are only deleted one at a time, and avoids the mistaken deletion of an immutable document in a mass action delete.
+</p>
+<br />
+<h2>How to Enable and Disable Administrator Mode</h2>
+<p>
+<ul>
+<li>1. Open Browse Documents.</li>
+<li>2. Locate the Administrator mode menu; then, click the maximize icon to expand the Administrator mode menu.</li>
+ <ul>
+ <li>To ENABLE administrator mode, click 'Enable Admin Mode'. </li>
+ <li>To DISABLE administrator mode, click 'Disable Admin Mode'. </li>
+ </ul>
+ </ul>
 </p>
 </body>
 </html>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
-"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
 <html>
 <head>
    <title>Archived Documents</title>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
-"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
 <html>
 <head>
-   <title>Authentication Sources</title>
+   <title>AUTHENTICATION SOURCES</title>
 </head>
  
  
 <body>
-<h2>Authentication Sources</h2>
-KnowledgeTree allows you to control access to the DMS for the users and groups in its database, using KnowledgeTree's own default authentication method - Database Authentication.
-<br></br><br></br>
-However, KnowledgeTree also allows you to add external authentication sources where your organization maintains its own list of users and groups that require controlled access to the DMS.
-<br></br><br></br>
-You can also modify or delete the details of external authentication sources and authentication provider information.
-<br></br><br></br>
-Note: You need to add the credentials of each user to KnowledgeTree (see Managing Users and Managing Groups) to allow the system to retrieve their details, even if you're using an external authentication source. 
+<h2>ABOUT AUTHENTICATION SOURCES</h2>
+<br />
+<h3>KnowledgeTree Default - Database Authentication</h3>
+<p>
+By default, KnowledgeTree's inbuilt authentication method stores information about users and groups in the KnowledgeTree database, and retrieves this information to control access to the KnowledgeTree document management system (DMS). 
+</p>
+<br />
+<h3>External Authentication Sources</h3>
+<p>
+If you want to maintain your own predefined user and group information to control access to KnowledgeTree, you can add users from a preconfigured external authentication source.  
+</p>
+<br />
+<p>
+When using external authentication sources, you need to add the authentication source, then, when adding your users to KnowledgeTree, select your preferred authentication source. When a user from your preferred authentication source first logs in to KnowledgeTree, their user credentials are automatically imported into KnowledgeTree. 
+</p>
+<br />
+<h2>HOW TO VIEW / ADD / EDIT / DELETE AN EXTERNAL AUTHENTICATION SOURCE</h2>
  
-For more detail, please refer to the Administrator Manual.
+<p>
+<ul>
+<li>1. In DMS Administration, click 'Users and Groups'.</li>
+<li>2. To open the Authentication configuration page, click 'Authentication'.</li>
+<li>3. What do you want to do?</li>
+</ul>
+</p>
+<br />
+<p>
+<h3>VIEW EXISTING EXTERNAL AUTHENTICATION SOURCES</h3>
+<li>a. External authentication source that have been added to your system are listed on the page.</li>
+</p>
+<br />
+<p>
+<h3>ADD A NEW EXTERNAL AUTHENTICATION SOURCE </h3>
+<ul>
+<li>a. To open the 'Add an authentication source' page, click 'Add a new authentication source'.</li>
+<li>b. Define a name for the authentication source. </li>
+<li>c. Select an authentication provider - by default, the pick list contains the standard options (LDAP, and Active Directory). To add more authentication providers, check the KnowledgeTree community forums at www.knowledgetree.com for developer information.</li>
+<li>d. Click 'Add a new source'. </li>
+<li>e. The authentication provider settings page opens, where you can edit the authentication provider settings.</li>
+</ul>
+</p>
+<br />
+<p>
+<h3>EDIT THE STANDARD CONFIGURATION FOR AN EXISTING AUTHENTICATION SOURCE (NAME AND PROVIDER)</h3>
+<ul>
+<li>a. On the Authentication page, view the list of existing authentication sources. </li>
+<li>b. In the Edit column for the relevant listed authentication source, click the 'Edit' icon to open the 'Edit an authentication source' page. </li>
+<li>c. Edit the authentication source name and/or the authentication provider.</li>
+<li>d. Click 'Save'. </li>
+</ul>
+</p>
+<br />
+<p>
+<h3>EDIT AUTHENTICATION PROVIDER SETTINGS FOR AN EXISTING AUTHENTICATION SOURCE</h3>
+<ul>
+<li>a. On the Authentication page, view the list of existing authentication sources.</li>
+<li>b. In the 'Edit Provider Information' column for the relevant listed authentication source, click the 'Edit' icon to open the 'Edit an authentication source' page. </li>
+<li>c. Add or edit the following settings: server name, port, whether to use Transaction Layer Security, base DN, search user, search password, search attributes, object classes. </li>
+<li>d. Click 'Save'. </li>
+</ul>
+</p>
+<br />
+<p>
+<h3>DELETE AN AUTHENTICATION SOURCE</h3>
+<ul>
+<li>a. On the Authentication page, view the list of existing authentication sources. </li>
+<li>b. Click the Delete icon for the authentication source you want to remove.</li>
+</ul>
+</p>
  
 </body>
 </html>
@@ -11,7 +11,7 @@
 Automatic workflows allow you to define the conditions for automatically assigning a
 specific workflow to a document.</p><p>
 Workflow assignment may occur on a per folder basis or on a per document type
-basis. Only one mode may be selected for a particular system.</p>
+basis. Only one mode may be selected for a particular system. </p>
  
 </body>
 -</html>
+</html>
 \ No newline at end of file
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
-"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
 <html>
 <head>
    <title>Unit Administration</title>
 </head>
 <body>
 <h2>Unit Administration</h2>
-<p>KnowledgeTree provides Units as a means of organizing groups. Units may be used to model your organization's business units.</p>
 <p>
-<strong>Note:</strong> By default, each time a new Unit is created on the system, a Unit folder is created in the Organization (root) directory.</p> 
+KnowledgeTree's <b>Unit</b> concept allows you to arrange the content of your document management system into standalone, separately managed sections.
+</p>
+<br />
+<p>
+For example, you may want to create Units that match the business model of your organization, such as a Unit folder for each department or regional office.
+</p>
+<br />
+<p>
+Units are also useful where you want to restrict access to certain parts of the DMS for specific users. User-level control is thus set up for specific Units - when these users log on, they will see only the Unit folder/s where they have been granted at least the 'read' permission. All other system folders and files are hidden.
+</p>
+<br />
+<p> 
+As with other system folders, Unit level access is controlled through KnowledgeTree's permissions system, by user group, and on specific folders.
+</p>
+<br />
+<p> 
+<b>Note:</b> By default, new Unit folders are added to the root directory, but you can specify a different location in the DMS.
+</p>
+<br />
+<p> 
+The KnowledgeTree system administrator adds Units, and assigns Unit administrator privileges to one or more users who are responsible for managing content and users in their Unit. The system administrator retains administrator privileges over the entire DMS, including all Units. 
+</p>
 </body>
 </html>
@@ -4,16 +4,14 @@
 <head>
    <title>Deleted Documents</title>
 </head>
-
-
 <body>
 <h2>Deleted Documents</h2>
 <p>
-This page allows you to restore or expunge documents that have been deleted in the KnowledgeTree repository.
-</p><p>
-<strong>Note:</strong> Expunging saves disk space by permanently deleting documents that are no longer useful or required.
-</p><p>
-<strong>Note:</strong> By default, documents are restored to the folder location where they were originally deleted. If that folder no longer exists on the system, the document is restored to the root directory in the repository. 
+Documents that are deleted from Browse Documents in the DMS are not permanently deleted - they are 'soft deleted' and hidden from view until the system administrator restores those documents or permanently removes them from the system (expunge).
+</p>
+<br />
+<p> 
+Expunging deleted documents frees up disk space in your system. Restored documents are returned to their original folder location or to the root directory if the original folder no longer exists. 
 </p>
 </body>
 </html>
@@ -8,13 +8,13 @@
  
  
 <body>
-<h2>Document Checkout</h2>
+<h2>Override Document Check out</h2>
 <p>
-This page lets you override the currently checked out status of a document and forces the document to be checked back in to the repository.
-</p><p>
-Forced check ins are used where a checked out document is urgently required back in the repository so that another user can check it out.
-</p><p>
-<strong>Note:</strong> The document is checked back in to the repository without saving any changes that may have been made to it while it was checked out.
+The KnowledgeTree administrator may override the checked-out status of a document to force a document back in to the repository. This action restores the content version of the document as it was before it was checked out.
+</p>
+<br />
 <p>
+Forced check-in is used when a checked out document is urgently required back in the repository so that another user can check out the document to update it, and the original document is no longer available and/or the user who checked that document out is not available to check-in the document. 
+</p>
 </body>
 </html>
@@ -5,57 +5,74 @@
    <title>Document Fieldsets</title>
 </head>
 <body>
-<h2>Document Fieldsets</h2>
 <p>
-Document Fieldsets allow you to associate custom metadata with documents in the
-repository.
+A <b>Fieldset</b> is a collection of Fields that may be associated with a specific Document Type, or with all Document Types in the system.
 </p>
+<br />
 <p>
-There are two types of document fieldsets:
+<h3>Types of Fields</h3>
+There are three types of fields:
 <ul>
-<li><strong>Normal</strong> - users are allowed to edit normal fieldsets only if they have been
-   associated with the document type that is being edited.</li>
-<li><strong>Generic</strong> - users may add and edit generic fieldsets to any document type in
-   KnowledgeTree.</li>
+<li><b>Normal</b> - stores text metadata, such as invoice code</li>
+<li><b>Lookup</b> - contains a list of selectable options that display in a pick list</li>
+<li><b>Tree</b> - allows you to select metadata values by browsing a tree structure</li>
 </ul>
 </p>
-<p>   
-<strong>Note:</strong> KnowledgeTree auto-generates an editable system name (namespace) for every
-fieldset. Plug-ins use this namespace to call the fieldset, and to control how the fieldset works.
-For more information on developing Plug-ins for KnowledgeTree, see the KnowledgeTree Wiki
-at <a href ="http://support.knowledgetree.com/confluence/">http://support.knowledgetree.com/confluence/</a>
-</p>
-
-<h2>Document Fields</h2>
+<br />
+<p>
+<h3>Types of Fieldsets</h3>
 <p>
-KnowledgeTree uses fields to group sets of related information into predefined
-fieldsets. The custom fieldsets are then associated with specific document types, to
-define the information (metadata) that should be included on documents of that
-type.</p>
+The following two fieldset types are KnowledgeTree defaults:
+</p>
 <p>
-There are three classes of custom fields in KnowledgeTree:
+<b>Note:</b> You can add plugins to KnowledgeTree that add different types of fieldsets, if required.
+</p>
+<p> 
 <ul>
-<li><strong>Normal</strong> - stores text metadata, such as invoice code</li>
-<li><strong>Lookup</strong> - used to allow users to select from a predefined set of options</li>
-<li><strong>Tree</strong> - used to allow users to select a metadata value by browsing a tree structure</li>
-</ul>
+<li><b>Normal</b> - may contain a variety of field types, i.e. one or more, or a combination, of Lookup field's, Tree field's, and Normal field's.</li>
+<li><b>Conditional</b> - contains two or more Lookup fields. This fieldset must be configured in the Fieldset editing pages after you add the fieldset, in order to set one field as the 'master' field, and to define how user-selected values in the master field determine the display of subsequent fields and values that are presented when the user adds document metadata. Since conditional fieldsets comprise a collection of interdependent fields and values, you need to plan the fieldset structure before creating the fieldset in the DMS. To use this feature, enable the 'Conditional Metadata' plugin in <b>DMS Administration >> Miscellaneous</b></li>
+</ul>.
 </p>
-<h3>Managing Tree Fields</h3>
-
+<h3>Generic Fieldsets</h3>
 <p>
-Trees can have multiple sub-categories and levels. You need to add sub-categories at
-each level in order to organize the options into a 'tree'.</p>
+A fieldset that is defined as 'generic' is automatically associated with each document type you add to the repository. Define a fielset as 'generic' when adding or editing the fieldset.
+</p>
+<br />
+<p>
+<h3>Working with Fieldsets</h3>
+How to View Existing Fieldsets
+<p>
+<li>1.	To open the Fieldset management page, click Document Fieldsets in Document Metadata and Workflow Configuration.</li>
+<li>2.	On the Document Fieldsets page, view existing fieldsets listed in the table.</li>
+</p>
+<br />
+<p> 
+<h3>How to Add a New Fieldset</h3>
 <p>
-The top level of the tree is called the root. The root, which holds all the top level
-items, is not shown to the user, but it provides a single 'parent' to the top level items.</p>
+<li>1.	On the Fieldset management page in DMS Administration, click Create New Fieldset.</li>
+<li>2.	Define a name for the fieldset in the Fieldset Name field; then, add a description in the Description field.</li>
+<li>3.	In the Fieldset Type section, define whether the fieldset is 'Normal' or Conditional'; then, define whether this is a 'generic' fieldset.</li>
+<li>4.	Click Create Fieldset.</li>
+</p>
+<br />
+<p>
+<h3>How to Add a New Conditional Fieldset</h3>
+<p>
+Before you begin, plan the fieldset, and its lookup fields and lookup values.
+</p>
+<br />
+<p>
+<ul>
+<li>1.	Add a new fieldset, and define the fieldset as 'Conditional'.</li>
+<li>2.	On the Edit Fieldset page, click Add New Field to add two or more lookup fields to this fieldset, and add lookup values for each field.</li>
+<li>3.	Once you have added all the fields and their lookup fields, set one field as the 'master' field - click Manage Field Ordering on the Edit Fieldset page.</li>
+<li>4.	Define the control field / dependent field relationship between all fields in the fieldset, starting with the master field - click Manage Field Ordering on the Edit Fieldset page. Repeat this step until all fields have been ordered into the control / dependent structure.</li>
+<li>5.	Edit fieldset rules to define conditional behaviour. To do this, click Manage Conditional Behaviour on the Edit Fieldset page.</li>
+<li>6.	For each control field, select a lookup value; then, select two or more lookup values in the dependent field - the dependent field values will display when the user selects the control field lookup value in the conditional fieldset. Click save this dependency to save each behaviour; then, when you're ready to configure the next field, click edit field.</li>
+<li>7.	When fieldset rules (conditional behaviour) have been set up on all control/dependent fields, click View Overview on the Edit Fieldset page to walk through a test of the fieldset you created.</li>
+</ul>
+</p>
+<br />
 <p>
-For example, let's say you create a tree of the countries in the world. In this case, the
-actual countries would be keywords - e.g. South Africa, England, Singapore, etc. And
-the highest group of categories (the top level or 'root') would be continents - e.g.
-Africa, Europe, Asia etc. The sub-categories, which fall below the top level 'continents'
-could be 'regions' - e.g. Sub-Saharan Africa, Western Europe, South East Asia.</p><p>
-KnowledgeTree allows you to create more sophisticated tree fields on the Edit
-Lookup Tree page.</p>
-
 </body>
 -</html>
+</html>
 \ No newline at end of file
@@ -2,44 +2,90 @@
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
 <html>
 <head>
-   <title>Archived Documents</title>
+<title>Document Types</title>
 </head>
 <body>
-<h2>Archived Documents</h2>
+<h2>Document Types</h2>
 <p>
-Document Types are used to group together documents that have a similar function.
-They also allow you to associate custom fieldsets for specific information that must be
-included with a particular document type.
+KnowledgeTree uses Document Types to group documents in the repository. This allows you to search for and manage your documents by 'Document Type', e.g. Invoice, Report, Template, Order, etc.
 </p>
-Let's say you create a document type called 'Invoice', and you want to ensure that
-all documents of the type 'Invoice' contain the following fields: invoice number,
-customer name, delivery address. You can group these fields in a fieldset called
-Invoice Details, for example. And then you may want to create another fieldset for
-the monetary values in the invoice, which you could call 'Amount'. The fieldset
-Amount may include the following fields: Nett Item Value, Tax, Discount, and
-Total Due.
+<br />
 <p>
-There are two ways you can configure the document type - Invoice - and the
-fieldsets you want to associate with this document type.
+For each Document Type, you can create a collection of fields, called 'fieldsets', and then associate the fieldsets (one or more) with selected Document Types. For example, for an 'Invoice' document type, you could create a fieldset called 'Invoice Details', for which you can create a collection of fields, such as: Invoice Number, Customer Name, Date, etc. When a user adds a document of the type 'Invoice', the fields display, and the user is required to enter field values, such as the invoice number, the name of the customer, and the date. When adding fieldsets and fields, you can specify whether they are 'required' - i.e. whether the user is must enter values for those fields.
 </p>
-
+<br />
 <p>
-1. You can first create the document type in the Document Types section, and then
-create one or more custom fieldsets in the Document Fieldsets section. The
-collection of fieldsets you define are automatically listed in the Document Type
-editing page. Having created the fieldset(s), you need to edit the document type you
-created in order to to add (associate) the fieldset(s) you want to use in this document
-type.
+<b>Note:</b> Fields, Fieldsets, and Document Type are Metadata - they are descriptive references for documents in the repository.
 </p>
+<br />
 <p>
-2. Alternatively, you can first create a set of custom fieldsets in the Document
-Fieldsets section, and then create the document type. Having added the document
-type, KnowledgeTree automatically opens the Document Type editing page, where
-you can select the fieldsets out of the collection of fieldsets you have pre-defined in
-Document Fieldsets, and which now display on the Document Type editing page.
+<h2>Working with Document Types</h2>
 </p>
+<br />
 <p>
-<b>Note:</b> Document types cannot be deleted in KnowledgeTree; they can only be disabled. Since a document type may be associated with a large amount of documents, deleting a document type may cause the loss of required metadata.
+<h3>How to Add a New Document Type</h3>
+<ul>
+<li>1.	On the Document Types page, enter a name for the new document type in the Name field.</li>
+<li>2.	Click Create.</li>
+<li>3.	On the document type configuration screen that displays, you can:</li>
+<ul>
+<li>change the document type name (click Change to save the new document type name)</li>
+<li>associate one or more fieldsets with this document type (available fieldsets are listed in the Available Fieldsets menu; or you can add more fieldsets in the Fieldset configuration section of DMS Administration, and then return to this page to associate additional fieldsets). When you're done, click Associate Fieldsets.</li>
+</ul>
+</ul>
+</p>
+<br />
+<p>
+<h3>How to View Existing Document Types</h3>
+<ul>
+<li>1.	Existing document types are listed in a table on the Document Types page. The table provides access to the following configuration options:</li>
+<ul>
+<li>Edit document type (edit document type name and associated fieldsets)</li>
+<li>Enable / disable the document type</li>
+<li>Delete document type (if the document type may be deleted)</li>
+</ul>
+</ul>
+</p>
+<br />
+<p>
+<h3>How to Edit a Document Type</h3>
+<ul>
+<li>1.	View existing document types in the table on the Document Types page.</li>
+</p>
+<br />
+<p>
+<li>2.	Do you want to ...</li>
+<ul>
+<li>change the document type name? Click the Edit icon in the Edit column for the relevant document type. On the editing screen, change the name of the document type. Click Change.</li>
+<li>associate or disassociate fieldsets on a document type? Click the Edit icon in the Edit column for the relevant document type. To associate fieldsets, on the editing screen, select fieldsets in the menu; then, click Associate Fieldsets; Or, to disassociate fieldsets, on the editing screen, select fieldsets you want to remove from this document type; then, click Disassociate Fieldsets.</li>
+</ul>
+</ul>
+</p>
+<br />
+<p>
+<h3>ENABLE OR DISABLE A DOCUMENT TYPE</h3>
+<ul>
+<li>1.	View existing document types in the table on the Document Types page.</li>
+<li>2.	Click on the icon in the Enable/Disable column for the relevant document type. If the document type is currently disabled, clicking the icon enables the document type; if the document type is currently enabled, clicking the icon disables the document type.</li>
+</ul>
+</p>
+<br />
+<p>
+<h3>EDIT A FIELDSET ASSOCIATED WITH A DOCUMENT TYPE</h3>
+<ul>
+<li>1.	View existing document types in the table on the Document Types page.</li>
+<li>2.	Click on the fieldset you want to edit (listed in the Associated Fieldsets column for the relevant document type).</li>
+<li>3.	On the Edit Fieldset page, to edit the fieldset name, description, and to define whether the fieldset is generic, click Edit these details); you can also manage (add, edit, or remove) fields in the fieldset.</li>
+</ul>
+ </p>
+<br />
+<p>
+<h3>DELETE A DOCUMENT TYPE</h3>
+<ul>
+<li>1.	View existing document types in the table on the Document Types page.</li>
+<li>2.	Click the delete icon in the Delete column for the relevant document type.</li>
+<b>Note:</b> You may only delete document types that have no associated documents in the repository - i.e. you cannot delete the 'Invoice' document type if you have documents in the repository of the type 'Invoice'. This prevents the removal of required metadata. You may however 'disable' a document type if you have no further use for it.
+</ul>
 </p>
 </body>
 -</html>
+</html>
 \ No newline at end of file
@@ -7,13 +7,31 @@
 <body>
 <h2>Dynamic Conditions</h2>
 <p>
-You use KnowledgeTree's Dynamic Conditions feature to set up the rules that will determine the permissions that may be applied to documents within a folder.These rules may be applied to a document's metadata, to its contents, or to its transactional information. Dynamic Conditions are applied on a per folder basis, and may be set up in the folder's Folder permissions page.
-</p><p>
-Having created a new dynamic condition, you need to assign it to a folder. You can also unassign dynamic conditions when they're no longer useful for the folder. </p><p>
-
-<strong>Note:</strong> Dynamic Conditions are configured in the same way as Saved Searches.
-</p><p>
-<strong>Note:</strong> Having defined a dynamic condition, you cannot delete it because that may change permission  assignments.
+A dynamic condition filters content in the system to selectively apply permissions to documents that meet the criteria of the condition.
+</p>
+<br />
 <p>
+After creating the dynamic condition you need to associate permissions with it on the Folder Permissions management page in Browse Documents.
+</p>
+<br />
+<p>
+<h3>Dynamic Conditions and Workflows</h3>
+</p>
+<p>
+Dynamic Conditions are also used to create Guard permissions, which are required to perform transitions on Workflows.
+</p>
+<br />
+<p>
+<h3>Viewing / Adding / Editing / Running Dynamic Conditions</h3>
+</p>
+<p>
+On the Dynamic Conditions page you can perform the following actions:
+<ul>
+<li>View existing dynamic conditions</li>
+<li>Add a new dynamic condition</li>
+<li>Edit an existing dynamic condition - add/remove/or edit criteria</li>
+<li>Run a dynamic condition to test results</li>
+</ul>
+</p>
 </body>
 </html>
@@ -6,18 +6,43 @@
 </head>
 <body>
 <h2>Help Administration</h2>
-
+KnowledgeTree Document Management System contains several built-in Help files.
+</p>
+<br />
+<p>
+You can access Help for the page you're on, wherever you see this icon <b><font color='blue'>(?)</font></b> in the bar at the top right of the page. The Help file that displays provides information on using the system function relevant to your current location in the DMS.
+</p>
+<br />
+<p>
+You can customize any Help file and restore the default text if necessary.
+</p>
+<br />
 <p>
-The KnowledgeTree Document Management System contains several built in system
-help files.
+<h3>Customize a Help File</h3>
+<ul>
+<li>1.	Open the relevant Help file in KnowledgeTree's Web interface.</li>
+<li>2.	Click the Help icon in the top bar to open the file.</li>
+<li>3.	Click Edit this help page to open the file editing screen.</li>
+<li>4.	Make the required changes; then, click Update.</li>
+</ul>
 </p>
+<br />
 <p>
-You can open a help file anywhere in the system by clicking this help page icon:(?)
+<h3>View Your Customized Help Files</h3>
+<ul>
+<li>1.	In DMS Administration - Miscellaneous - Edit Help Files, click Edit Help Files to open the Current Help Assignments page.</li>
+<li>2.	View the list of files (if any) in the Existing Customized Help Pages section.</li>
+</ul>
 </p>
+<br />
 <p>
-The help file that displays is relevant to the location of the icon. For example, in the
-image below, you click the help page icon on the right of the page to view help for
-Browse Documents.
+<ul>
+<h3>Delete a Custom Help File</h3>
+<li>1.	View the list of custom help files.</li>
+<li>2.	Click Delete for the relevant file.</li>
+<li>3.	The default file replaces the custom file.</li>
+</ul>
 </p>
+<br />
 </body>
 -</html>
+</html>
 \ No newline at end of file
@@ -6,10 +6,42 @@
 </head>
 <body>
 <h2>Link Type Management</h2>
-
-Document links allow users to establish associations between documents in the
-repository. When creating a document link, you should specify the type of relationship that the
-link implies between the linked documents - i.e. 'associated with', or 'duplicated by'.
-
+You can create various types of links between documents in the system that informs the user about the relationship between the linked documents.
+<p>
+When creating a link, you specify the type of link, such as 'associated with' or 'duplicated by'. When a document is linked to one or more other documents, the link to associated documents display on the document's Document Details page.
+</p>
+<br />
+<p>
+<h3>Viewing Existing Link Types</h3>
+<ul>
+<li>1.	Scroll down to the bottom of the page, to the 'Manage Existing Link Types' section, where you can view existing link types.</li>
+</ul>
+</p>
+<br />
+<p>
+<h3>Editing Link Types</h3>
+<ul>
+<li>1.	Click the Edit icon for the relevant link type to open the the link type editing screen.</li>
+<li>2.	Make the required changes (change the name or description).</li>
+<li>3.	Click Change Link Type.</li>
+</ul>
+</p>
+<br />
+<p>
+<h3>Adding New Link Types</h3>
+<ul>
+<li>1.	Define a name for the link type in the Name field.</li>
+<li>2.	Provide a brief description of the link in the Description field.</li>
+<li>3.	Click Add Link Type.</li>
+</ul>
+</p>
+<br />
+<p>
+<h3>Deleting Link Type</h3>
+<ul>
+<li>1.	Locate the link type in the Manage Existing Link Types section at the bottom of the page.</li>
+<li>2.	Click the Delete icon for the relevant link.</li>
+</ul>
+</p>
 </body>
 -</html>
+</html>
 \ No newline at end of file
@@ -7,17 +7,36 @@
 <body>
 <h2>Manage Groups</h2>
 <p>
-Only a <b>User</b> that has been assigned to a <b>Group</b> is allowed to access the KnowledgeTree Document Management System.
+Any system User may belong to more than one Group, and any Group may be added as a member of another Group, as a Sub Group.
 </p>
-<strong>Note:</strong> Groups can be members of other groups, and can have other groups as members.  These memberships pass the permissions set on to the parent group to user members of the member groups, possibly along a few chains.
-
-<h3>Example:</h3>
-
-<p>Let's say you create a new Group called Testers. Having created the Testers Group, you must assign the it to a Unit. You can name the Unit 'Quality Assurance'. So, the group named Testers is part of the unit Quality Assurance.
+<br />
+<p>
+Permissions and Group Membership
+</p>
+<br />
+<p>
+KnowledgeTree permissions are assigned at the Group level (and also at the Role level), but not to individual users. Each user requiring access to the system must be added to KnowledgeTree as an individual user, and then that user is added to one or more Groups, or is assigned to a Role, in order to obtain the permissions allocated to the Group (or the Role).
+</p>
+<br />
+<p>
+Permissions are passed on to users through their membership of a Group (or a Role), and any sub group that is a member of another Group (the parent) obtains the permissions that are allocated to the parent group.
 </p>
-<p> 
-Group: Testers<br>
-Unit: Quality Assurance
+<br />
+<p>
+Add users to groups in DMS Administration - Manage Users.
+</p>
+<br />
+<p>
+<h3>Tasks in Manage Groups</h3>
+</p>
+<p>
+In Manage Groups you can perform the following tasks:
+<ul>
+<li>View existing groups - search for a group by entering all or part of the group name, or click View All Groups to display a list of all groups</li>
+<li>Add new groups</li>
+<li>Edit groups - change the name of a group, allocate Unit Administrator rights and/or System Administrator rights to group members, remove a Group from a Unit</li>
+<li>Add or remove sub groups from a Group</li>
+</ul>
 </p>
 </body>
 </html>
@@ -6,8 +6,36 @@
 </head>
 <body>
 <h2>Manage Permissions</h2>
-KnowledgeTree 3 provides several default (core) permissions - <b>Read</b>, Write</b>, <b>Add Folder</b>, <b>Manage Permissions</b>, <b>Delete</b> - but it also allows you to create your own permissions.
-<br></br><br></br>
-You can create permissions for controlling user and group access for plug-ins, or create permissions to use as Guard Permissions for workflow transitions.
+<p>
+KnowledgeTree provides several default (core) permissions:
+<ul>
+<li>Read</li>
+<li>Write</li>
+<li>Add Folder</li>
+<li>Manage Security</li>
+<li>Delete</li>
+<li>Manage Workflow</li>
+<li>Folder Details</li>
+<li>Rename Folder</li>
+</ul>
+</p>
+<br />
+<p>
+You may create additional (custom) Permissions, which are useful where you want to control access for Plug-ins, or to create Permissions as Guard permissions on Workflows.
+</p>
+<br />
+<p>
+<b>Note:</b> Only custom permissions may be deleted.
+</p>
+<br />
+<h3>Tasks in Manage Permissions</h3>
+<p>
+In this section you can perform the following tasks:
+<ul>
+<li>View existing permissions</li>
+<li>Remove custom permissions</li>
+<li>Add new custom permissions</li>
+</ul>
+</p>
 </body>
 </html>
@@ -7,19 +7,32 @@
 <body>
 <h2>Manage plugins</h2>
 <p>
-Plug-ins allow you to add new features to your implementation of the KnowledgeTree Document Management System.
+KnowledgeTree allows the use of Plugins that extend the functionality of the document management system.
 </p>
- 
+<br />
 <p>
-<strong>Note:</strong> Go to <a href="http://support.knowledgetree.com/confluence/x/xg">our Wiki </a> to view a list of the plug-ins that have been developed by the KnowledgeTree community. 
+View descriptions of the plugins on the Plugins Index at the <a href="http://forge.knowledgetree.com">KnowledgeTree Forge</a>.
 </p>
+<br />
+<h3>Updating Plugins</h3>
 <p>
-You use <strong>Manage Plugins</strong> to:
-</p>
-<ul> 
-<li>re-read the plug-ins list for new plug-ins that you copy to the plug-in directory</li>
-<li>enable plug-ins</li>
-<li>disable plug-ins</li>
+The plugins list must be re-read from the filesystem in the following instances:
+<ul>
+<li>if you have moved the location of your KnowledgeTree installation to another server</li>
+<li>after installing or upgrading KnowledgeTree</li>
+<li>if you have installed new plugins or removed unwanted plugins from the filesystem</li>
 </ul>
+ </p>
+<br />
+<p>
+Rereading the plugins from the filesystem refreshes the plugins list that displays on the Manage Plugins page in the DMS.
+</p>
+<br />
+<h3>Enabling and Disabling Plugins</h3>
+<p>
+Most plugins are enabled by default. To enable a plugin so that you can use this functionality in the system, select the check box adjacent to the plugin name. To disable a plugin, deselect the check box. When you're done, save your changes. 
+</p>
+<br />
+<p>
 </body>
 </html>
@@ -8,11 +8,108 @@
 <body>
 <h2>Manage Users</h2>
 <p>
-You use the <b>Manage Users</b> section of <b>Users</b> and <b>Groups</b> to add or remove users from the KnowledgeTree Document Management System. You can also search for user details, or view a list of all the users that exist in the system.
+<h3>In DMS Administration >> User and Groups >> Manage Users you can:</h3>
+<ul>
+<li>add new users (add users manually, or import user details from an external authentication source)</li>
+<li>search for users</li>
+<li>view a list of all users that exist in the system</li>
+<li>enable, disable, or delete users</li>
+<li>edit users (add and edit login name, username, email address, mobile number, enable/disable email notification, password, maximum login sessions)</li>
+<li>view, add, and edit a user's group membership</li>
+</ul>
 </p>
+<br />
 <p>
-The system uses the information you specified when you added the user or group, to retrieve their details from the authentication source. This allows verification of the user or group's login rights, and of the permissions they have for accessing information in the repository. 
+<h2>Adding Users</h2>
+<h3>Adding New Users (manually)</h3>
+<ul>
+<li>1.	Click Add a new user.</li>
+<li>2.	Add details for the user:</li>
+</ul>
+<ul>
+<li>login name</li>
+<li>full name</li>
+<li>email address</li>
+<li>define whether to enable email enable notifications</li>
+<li>password</li>
+<li>mobile number</li>
+<li>maximum login sessions (prevents multiple users logging in on the same account)</li>
+</ul>
+<li>3.	Click create user.</li>
+</ul>
 </p>
-
+<br />
+<h3>Adding New Users (From External Authentication Source)</h3>
+<p>
+KnowledgeTree uses the information you specified when adding the user or group to retrieve their details from the specified authentication source. The user or group's login details and permissions are verified when they first log in to the DMS.
+</p>
+<br />
+<p>
+<b>Note:</b> You can't change the authentication source for a user after adding the user from a selected authentication source.
+</p>
+<br />
+<p>
+Prerequisites:
+<ul>
+<li>Add the authentication source to KnowledgeTree</li>
+<li>Ensure the authentication provider plugin is registered and enabled</li>
+</ul>
+</p>
+<br />
+<p>
+<ul> 
+<li>1.	In the Add User From Authentication Source section, select an authentication source from the pick list.</li>
+<li>2.	Click Add from Source to open the Search for user page for the authentication source you selected; then, do one of the following:</li>
+<ul>
+<li>search for the user</li>
+<li>select Mass Import (adds all users from the authentication source); then, click search for users.</li>
+</ul>
+</ul>
+</p>
+<br />
+<p>
+<b>Note:</b> You won't be able to verify the details of individual users added through Mass Import. When bulk adding users, users that already exist in the system are duplicated in KnowledgeTree with 'duplicate' appended to the username.
+</p>
+<br />
+<p>
+<h3>Display All Users</h3>
+<ul>
+<li>1. In Search for Users, click View All Users. A list of all users displays at the bottom of the page.</li>
+</ul>
+</p>
+<br />
+<p>
+<h3>Search for Users</h3>
+<ul>
+<li>1.	In Search for Users, enter all or part of the username in the Username field.</li>
+<li>2.	Click Search for Users to display the user's details.</li>
+</ul>
+</p>
+<br />
+<p>
+<h3>Enable / Disable User</h3>
+<ul>
+<li>1.	Search for the user.</li>
+<li>2.	Select the user; then, click Enable or Disable as required.</li>
+</ul>
+</p>
+<br />
+<p>
+<h3>Edit User Details</h3>
+<ul>
+<li>1.	Search for the user to display the user's details.</li>
+<li>2.	Click the Edit icon for the user to open the Edit User Details page.</li>
+<li>3.	Make the required changes; then, save your changes.</li>
+</ul>
+</p>
+<br />
+<p>
+<h3>Edit User's Group Membership</h3>
+<ul>
+<li>1.	Search for the user.</li>
+<li>2.	Click Manage Groups for the relevant user to open the Change [username] Groups page.</li>
+<li>3.	Make the required changes (add user to groups, remove user from groups).</li>
+<li>4.	Save your changes. </li>
+</ul>
 </body>
 -</html>
+</html>
 \ No newline at end of file
@@ -6,10 +6,42 @@
 </head>
 <body>
 <h2>Role Administration</h2>
-Roles include, for example, a document creator, a document reviewer, a document publisher, or writer, editor, developer, secretary, and so on.
-<br></br><br></br>
-Workflow actions - e.g. review, or publish - are typically assigned to a specific role. The role is granted permissions for working with the document, based on the type of tasks their role performs - e.g. reviewers need read and write permissions.
-<br></br><br></br>
-User Groups are allocated to Roles on a per-directory basis, and are inherited from the root folder of the DMS. 
+<h3>In DMS Administration >> Security Management >> Role Management page, you can:</h3>
+<p>
+<ul>
+<li>add new roles</li>
+<li>edit roles (change the name of the role)</li>
+<li>delete a role</li>
+</ul>
+</p>
+<br />
+<p>
+
+<h3>What are Roles?</h3>
+</p>
+
+<p>
+To access the DMS, users must be assigned to Groups, or to Roles. Permissions are assigned to Groups and Roles on the Folder level. Roles are used to assign permissions to specific users for specific tasks. Example Roles may be: Reviewer, Publisher, Writer, Editor, Developer, Secretary, Anonymous.  In smaller organizations there are likely to be groups with only one user, e.g. the 'manager', and in this case the Group concept can be replaced entirely by the 'Role'.
+</p>
+<br />
+<p>
+ 
+
+<h3>Roles and Workflows</h3>
+</p>
+
+<p>
+Workflow actions, e.g. 'review', or 'publish', are typically assigned to a specific Role. The Role is granted permissions for working with the document, based on the type of tasks their role performs - e.g. reviewers need read and write permissions.
+</p>
+<br />
+<p>
+ 
+
+<h3>Groups and Roles</h3>
+</p>
+
+<p>
+User Groups are allocated to Roles on a per-directory basis (by location), and are inherited from the root folder of the DMS. When assigning permissions or actions to Roles in a Workflow, you can use that Workflow anywhere in the site by assigning the appropriate Groups to it in that location.
+</p>
 </body>
 </html>
@@ -6,24 +6,26 @@
 </head>
 <body>
 <h2>System information</h2>
-
 <p>
-KnowledgeTree provides a Support and System Information page in the Miscellaneous section of DMS Administration, which helps you identify and fix problems with your system.The Support and System Information page displays the output of a php_info command in a scrollable window. You may be asked to copy and send this information to the KnowledgeTree support staff if you require assistance with your problem.
+In DMS <b>Administration >> Miscellaneous >> Support and System Information</b> you can download support information that helps you to identify and fix problems.
 </p>
+<br />
+<h3>View System Support Information</h3>
 <p>
-Clicking the Download PHP Information link on this page automatically runs <strong>phpinfo</strong> and prints the results to the KnowledgeTree Document Management System.
+1. Click Download Support Information.
 </p>
+<br />
 <p>
-<strong>Note:</strong> If you believe that distributing this information represents a security risk for your organization, we recommend that you sanitize the output before copying and sending it. Alternatively, please enquire about sending the information directly to the developer dealing with your issue. 
+This action downloads a collection of information on your KnowledgeTree installation.
+</p>
+<br />
 <p>
- 
+<b>Note:</b> You may required to send this information to KnowledgeTree support staff to assist with your issue. Sanitize the information before sending it to us if you believe that distribution represents a security risk for your organization, or enquire about sending the information directly to the KnowledgeTree developer dealing with your issue.
+</p>
+<br />
+<h3>KnowledgeTree Issue Tracker</h3>
 <p>
-You can also click the direct link to the KnowledgeTree Issue Tracker, where you can:
+To report bugs, view known issues, or to find out whether fixes have already applied for your problem in a newer version of KnowledgeTree, click on the link to the KnowledgeTree Issue Tracker.
 </p>
-<ul> 
-<li>report bugs</li> 
-<li>view known issues</li> 
-<li>find out whether fixes have already been applied for your problem in a new version of KnowledgeTree</li>
-</ul>
 </body>
 </html>