/314120050310174840 {
    .title "/OBJECT/SYSTEM/USER"
	.id 314120050310174840
	.tags {database field}
    .body {
    	[p {
    		There is only one user when a database is created, the [qw_field_value ADMINISTRATOR].
            This user can access the entire database.
            To log into a database you need to be a user.
            The administrator can never be deleted, disabled, or removed from users,
            ensuring that you never lock yourself out of the database.
            This feature sets the administrator apart from other users that may be
            created in the database.
	    }]
    }
}
/314120050310174601 {
    .title "/OBJECT/SYSTEM/USER.password"
	.id 314120050310174601
	.tags {database field}
    .body {
    	[p {
			A password is a security measure used to restrict access to a database.
            A password is a string of characters that must be provided before the
            user name is authorized.
            A password can be made up of any typable character and is case sensitive.
        }]
        ::append ::Html [ul {
            [li {[link .chm $::qw_manual_file .id 314120050228112651 {Workstation Passwords}]}]
            [li {[link .chm $::qw_manual_file .id 314120050228125631 {User Passwords}]}]
        }]
    }
}
/314120050310174619 {
    .title "/OBJECT/SYSTEM/USER.sessions"
	.id 314120050310174619
	.tags {database field}
    .body {
    	[p {
            A table of sessions belonging to the user.
        }]
    }
}
/314120050310174627 {
    .title "/OBJECT/SYSTEM/USER.access_view"
	.id 314120050310174627
	.tags {database field}
    .body {
    	[p {
			If the user's [qw_field_name .access_view] field is set to [qw_field_value Yes]
            then security information will be displayed with windows the user creates
            on most accounting documents.

            The user will be able to switch to a view that displays who has been
            granted access to a particular object under the NV2 security system.
        }]
		[p {
			For example, when the user is displaying a table of accounts such as
            on a report, the bottom pane can display who has access to the account
            that the user is positioned on.
        }]
    }
}
/314120050310174637 {
    .title "/OBJECT/SYSTEM/USER.audit_view"
	.id 314120050310174637
	.tags {database field}
    .body {
    	[p {
			If the user's [qw_field_name .audit_view] field is set to [qw_field_value Yes]
            then audit information will be displayed with windows the user creates
            on most accounting documents.

            The user will be able to switch to a view that displays the audit
            information for a particular object under the NV2 audit system.
        }]
		[p {
			For example, when the user is displaying a table of transactions such as on a
            journal, the bottom pane can display who created or changed that transaction.
        }]
    }
}
/314120050310174641 {
    .title "/OBJECT/SYSTEM/USER.script_autoexec"
	.id 314120050310174641
	.tags {database field}
    .body {
    	[p {
            A script that executes every time the user log's in.
        }]
    }
}
/314120050310174645 {
    .title "/OBJECT/SYSTEM/USER.autoshut"
	.id 314120050310174645
	.tags {database field}
    .body {
    	[p {
			A script that executes every time the user log's out.
        }]
    }
}
/314120050310174650 {
    .title "/OBJECT/SYSTEM/USER.access_tos"
	.id 314120050310174650
	.tags {database field}
    .body {
    	[p {
			The user's [qw_field_name .access_tos] table is where access to objects
            in the database are granted.
            Each row in the table represents an object that the user has access to.

            The database structure is a hierarchy similar to a file system.

            When a user is granted access to the root object, the user has access to the entire
            database.

			For example, to give a user access to the entire database, insert a row on
            the access tos table. In the [qw_field_name .Name] field press F3 and click
            on the root of the database hierarchy.
        }]
		[p {
			Example, setting up an accounts payable clerk.
        }]
		[p {
            To only give a user access to Accounts Payable, the Purchase Invoice Journal
            and the Purchase Order Journal do the following;

            Insert a new row on the users access tos table, in the object name field press F3.
            On the Select Access to Object menu, select [qw_menu_command NewViews Account Accounts Payable] folder.

            Insert another row on the users Access Tos table, in the object name field press F3.
            On the Select Access to Object menu, select [qw_menu_command NewViews Journal Purchase]

			A users access to the database is through the users own desktop.
            The last item to be added is the user's own desktop.

            Insert another row on the users Access Tos table, in the object name field press F3.
            On the Select Access to Object menu, select [qw_menu_command System User (the user's name)],
            set the folder field to file.
        }]
		[p {
			Example, setting up an payroll clerk.
        }]
		[p {
            To only give a user access to Employees, Payroll, Payroll Journal, Payroll Accounts, and Payruns
            do the following;

            Insert a new row on the users access tos table, in the object name field press F3.

            Payroll is a special case.

            To access the hidden nodes in the database, right click on the Select Access to Object
            menu, click on File Sort, change the index from folder to description.
            On the Select Access to Object menu, select NewViews Payroll.

            Insert another row on the users Access Tos table, in the object name field press F3.
            On the Select Access to Object menu, select [qw_menu_command NewViews Journal Payroll],
            set the folder field to file.

            Insert another row on the users Access Tos table, in the object name field press F3.
            On the Select Access to Object menu, select [qw_menu_command NewViews System Employee],
            set the folder field to file.

            Insert another row on the users Access Tos table, in the object name field press F3.
            On the Select Access to Object menu, select [qw_menu_command NewViews Account Payroll],
            set the folder field to file.

            Insert another row on the users Access Tos table, in the object name field press F3.
            On the Select Access to Object menu, select [qw_menu_command NewViews System Transaction Payroll],
            set the folder field to file.

            Insert another row on the users Access Tos table, in the object name field press F3.
            On the Select Access to Object menu, select [qw_menu_command NewViews system Payrun],
            set the folder field to file.

			A users access to the database is through the users own desktop. The last item to be added
            is the user's own desktop.

            Insert another row on the users Access Tos table, in the object name field press F3.
            On the Select Access to Object menu, select [qw_menu_command System User (the user's name)],
            set the folder field to file.
        }]
		[p {
			The Payroll clerk's desktop should look like:
        }]
		[p {
            [table .border.cellspacing 1 .border.cellpadding 7 {
                [tr {
                    [td {
                        [bold "Object Name"]
                    }]
                    [td {
                        [bold "Object Description"]
                    }]
                    [td {
                        [bold "Access To=[gt]"]
                    }]
                    [td {
                        [bold Folder]
                    }]
                }]
                [tr {
                    [td {
                        PAYROLL
                    }]
                    [td {
                        Payroll
                    }]
                    [td {
                        /OBJECT/NEWVIEWS/PAYROLL
                    }]
                    [td {
                        folder
                    }]
                }]
                [tr {
                    [td {
                        PAYROLL
                    }]
                    [td {
                        Payroll
                    }]
                    [td {
                        /OBJECT/NEWVIEWS/JOURNAL/PAYROLL
                    }]
                    [td {
                        file
                    }]
                }]
                [tr {
                    [td {
                        EMPLOYEE
                    }]
                    [td {
                        Employee
                    }]
                    [td {
                        /OBJECT/NEWVIEWS/SYSTEM/EMPLOYEE
                    }]
                    [td {
                        file
                    }]
                }]
                [tr {
                    [td {
                        PAYROLL
                    }]
                    [td {
                        payroll
                    }]
                    [td {
                        /OBJECT/NEWVIEWS/ACCOUNT/PAYROLL
                    }]
                    [td {
                        file
                    }]
                }]
                [tr {
                    [td {
                        PAYROLL
                    }]
                    [td {
                        payroll
                    }]
                    [td {
                        /OBJECT/NEWVIEWS/SYSTEM/TRANSACTION/PAYROLL
                    }]
                    [td {
                        file
                    }]
                }]
                [tr {
                    [td {
                        PAYRUN
                    }]
                    [td {
                        payrun
                    }]
                    [td {
                        /OBJECT/NEWVIEWS/SYSTEM/PAYRUN
                    }]
                    [td {
                        file
                    }]
                }]
                [tr {
                    [td {
                        USER's name
                    }]
                    [td {
                        USER's name
                    }]
                    [td {
                        /OBJECT/SYSTEM/User's name
                    }]
                    [td {
                        file
                    }]
                }]
			}]
        }]
    }
}
/314120050310174654 {
    .title "/OBJECT/SYSTEM/USER.audit_trail"
	.id 314120050310174654
	.tags {database field}
    .body {
    	[p {
			This displays a table of the user's audits. Here you will find all the changes
            made to a database by the user. Whatever the user has created, changed or deleted
            will be listed here.
        }]
    }
}
/314120050310174658 {
    .title "/OBJECT/SYSTEM/USER.options"
	.id 314120050310174658
	.tags {database field}
    .body {
    	[p {
        }]
    }
}
/314120050310174704 {
    .title "/OBJECT/SYSTEM/USER.options.date"
	.id 314120050310174704
	.tags {database field}
    .body {
    	[p {
        }]
    }
}
/314120050310174711 {
    .title "/OBJECT/SYSTEM/USER.options.date.format"
	.id 314120050310174711
	.tags {database field}
    .body {
    	[p {
			This option is used to set the date display format for the user.

			NV2 has extended the date display formats over previous versions.

			Use F3 to get a list displaying the 22 various display formats available.
        }]
    }
}
/314120050310174715 {
    .title "/OBJECT/SYSTEM/USER.options.date.entry"
	.id 314120050310174715
	.tags {database field}
    .body {
    	[p {
			This option is used to set the date entry format for the user.

            In NV1, only one date entry format was provided, NV2 has numerous date entry formats.

            For example you may enter; 15 May 2005, May 15 2005 or 15052005 all as correct dates.

            To edit an existing date, you only need to replace the portion of the date that is incorrect.

            For example if you wish to change 15Jul2005 to 15Aug2005, simply replace the letters
            Jul with Aug and press Enter.

            Use F3 to get a list displaying the various entry formats available.
        }]
    }
}
/314120050310174719 {
    .title "/OBJECT/SYSTEM/USER.options.currency"
	.id 314120050310174719
	.tags {database field}
    .body {
    	[p {
        }]
    }
}
/314120050310174724 {
    .title "/OBJECT/SYSTEM/USER.currency.format"
	.id 314120050310174724
	.tags {database field}
    .body {
    	[p {
			This option is used to set the currency display format for the user.
            Use F3 to get a list displaying the currency display formats available.
            Changing this format will set the currency display for this user only.
        }]
    }
}
/314120050310174731 {
    .title "/OBJECT/SYSTEM/USER.currency.entry"
	.id 314120050310174731
	.tags {database field}
    .body {
    	[p {
        }]
    }
}
/314120050310174737 {
    .title "/OBJECT/SYSTEM/USER.transaction"
	.id 314120050310174737
	.tags {database field}
    .body {
    	[p {
        }]
    }
}
/314120050310174741 {
    .title "/OBJECT/SYSTEM/USER.transaction.begin"
	.id 314120050310174741
	.tags {database field}
    .body {
    	[p {
			This option is used to set a transaction edit range begin date for the user.
            Only transactions after this date may be created, changed or deleted by the user.
        }]
    }
}
/314120050310174747 {
    .title "/OBJECT/SYSTEM/USER.transaction.end"
	.id 314120050310174747
	.tags {database field}
    .body {
    	[p {
			This option is used to set a transaction edit range end date for the user.
			Only transactions before this date may be created, changed or deleted by the user.
        }]
    }
}
/271820181001111932 {
    .title "/OBJECT/SYSTEM/USER.transaction.date_range_check_is_enabled"
	.id 271820181001111932
	.tags {database field}
    .body {
    	[p {
			Transaction date range checking can be turned off for individual journals,
            only by users that have been granted rights to do so.
        }]
    	[p {
			Many applications that employ transactions to track non-financial or quasi-financial data
            require the ability to disable transaction date range checking on a journal by journal basis.
            For example, transactions with [qw_field_name tag] [qw_field_value schedule] might never need to be checked.
            Note that transactions with [qw_field_name tag] [qw_field_value financial] should probably always be checked.
        }]
    	[p {
			This option is used to set the rights for the user.
			If this field is set to [qw_field_value yes] then the user will have the ability to edit a journal's
            setting that enables/disables date range checking.
        }]
    }
}
/314120050310174752 {
    .title "/OBJECT/SYSTEM/USER.transaction.reconcile"
	.id 314120050310174752
	.tags {database field}
    .body {
    	[p {
        }]
    }
}
/314120050310174803 {
    .title "/OBJECT/SYSTEM/USER.transaction.reconcile.safety"
	.id 314120050310174803
	.tags {database field}
    .body {
    	[p {
			This option is used to turn Edit Reconcile ON. with Edit Reconcile
            set to OFF no transactons that are reconciled or have reconciled
            cross-items can be edited or deleted.
        }]
    }
}
/314120050310174809 {
    .title "/OBJECT/SYSTEM/USER.history"
	.id 314120050310174809
	.tags {database field}
    .body {
    	[p {
        }]
    }
}
/314120050310174818 {
    .title "/OBJECT/SYSTEM/USER.history.begin"
	.id 314120050310174818
	.tags {database field}
    .body {
    	[p {
			This option is used to set a history display range begin date for the user.

			Only history data after this date will be displayed.

            With this option the history date range can be limited. For example, when set to display current
            information such as one year, the weekly view will only display 52 weeks of information.
        }]
    }
}
/314120050310174822 {
    .title "/OBJECT/SYSTEM/USER.history.end"
	.id 314120050310174822
	.tags {database field}
    .body {
    	[p {
			This option is used to set a history display range end date for the user.

			Only history data before this date will be displayed.

            With this option the history date range can be limited. For example, when set to display current
            information such as one year, the weekly view will only display 52 weeks of information.
        }]
    }
}
/314120050310174826 {
    .title "/OBJECT/SYSTEM/USER.edit"
	.id 314120050310174826
	.tags {database field}
    .body {
    	[p {
        }]
    }
}
/314120050310174831 {
    .title "/OBJECT/SYSTEM/USER.edit.safety"
	.id 314120050310174831
	.tags {database field}
    .body {
    	[p {
			This option can be used to turn Edit Safety OFF. Edit Safety
            prevents accintdental changes to NewViews data. With Edit Safety set to ON,
            you can not change or delete any transactons.
        }]
    }
}
/314120050310174835 {
    .title "/OBJECT/SYSTEM/USER.edit.as_of_date"
	.id 314120050310174835
	.tags {database field}
    .body {
    	[p {
			This option can be used to set report aging dates. i.e. Account Payable
            and Account Receivable invoice and order aging reports will display aged
            columns according to the date set. When this date option is left blank,
            the report dates will be set according to the computer's system date.
        }]
    }
}