Each user may reset his/her password by clicking the Password button on the Top Button bar, entering and confirming the password, and clicking OK.Maintains user record, password and security information. If filled in, the security table in the lower section of the screen enables the user to switch their branch security levels (and, optionally their user group) without logging in under a different id. This feature is useful for administrators logging on to maintain branch data.
This release changes the way in which ‘Active’ users of specific type are counted. Previously, when counting active users for licensing purposes, the system only looked at users whose ‘Disabled’ field was clear (set to No). In this release, active users are those whose Disabled field is clear AND whose Password Expiration Date is either blank (1900-01-01) or set to a future date. This brings the licensing calcuations in line with the users that are displayed as active in the list.
In general a User Id should NOT be changed if, for example, one sampro user was being replaced by another. The preferred method of handling the user record if one user will be replacing another is to first disable one user record (for the old user) and then create a new record for the new user.
Required to log onto SAMPro, DBAnalytics and TimeAnywhere.
Referenced in Journals: A user, date and time stamp is maintained by the system for manual journal entries.
See Global Setting Security Override to set the security of work orders and other records according the security of the Job, not the user.
See Block Users from Seeing Records with Specific Security for a registry to limit user's access to specific companies by Security (Intercompany installations).
Create a new user on the system, change a password expiration date.
Main Tab
User Id:
A unique id for this user. This field is required.
User Name:
The name of the user; this field is optional but recommended.
Disabled?
If this field is flagged, the user will be unable to log onto the Data-Basics' software. Double-click on this field (or press the Spacebar) to flag/clear it.
If a user flags this field and the AND the User Account being disabled has active sessions a warning that 'Active Sessions for this User will be terminated' will be displayed. The system will terminate all active sessions when a User Account is disabled and the record is saved.
Note: If the user being disabled has unsaved changes it may be difficult for them to exit SAMPro; we recommend that you contact the user and instruct them to exit SAMPro. The UserLogonSummary tab should be used to determine if the selected User is active.
New Password: Confirm Password: (10 character)
Use these fields to enter and confirm a new/changed password for this user. The password does not display in either of these fields for security purposes. After a user record has been created, the user should log on as soon as possible and change his or her password to maintain system security.
Report Password: Confirm Report Password: (10 character)
Use these fields to enter and confirm a new/changed Access report password for this user. This field must be completed even if the user will not be running Access reports. The password does not display in either of these fields for security purposes.
Each user may reset his/her password by clicking the Password button on the Top Button bar, entering and confirming the password, and clicking OK.
Access Type: Full Read Only Remote Special
This field defines this user record for licensing purposes. The system compares the number of active users of this type with the number of users that you have licenses for when you create or change a user record. The Access type of Remote is used for Remote Time Entry (users must have an Access Type of Full or Remote).
The type of Special is designed for support and agent log on’s so that the count of user’s purchased licenses can be maintained more accurately. A master log in is required to create or edit this type of user.
Credit Manager?
If this user is a credit manager that is allowed to implement credit overrides the Work Order or COP Order, flag this field by double-clicking on it (or pressing the Spacebar). To implement credit overrides for only COP or only Work Orders, see User Registry Entries.
Purchasing Agent
A User must be flagged as a Purchasing Agent to save a released, changed, or printed PO. Users without this authority can only save Unreleased PO's.
Drop Ship Agent:
Check this box (by pressing the spacebar or double-click it) if this user is authorized to flag Client Orders for drop shipment.
Executive P/R?
This field has been added to both the User and Employee records. By definition:
An Executive P/R Employee is only accessible by an Executive P/R User.
The Executive Payroll check box in an Employee record may only be set or cleared by a user with the Executive Payroll box checked in their user record
An Executive P/R User has full access to ALL employees.
Executive Payroll enter/edit restrictions have been applied so that users without the Executive Payroll flag will not be able to access entries for Executive Payroll Employees in the Labor Journal, PR Journal and Job Journal as well as many reports. See Executive Payroll for details.
Notes Administrator?
Checking this field designates the user as a notes administrator that will override the ownership security on record notes. Any user designated as a Notes Administrator will be able to change or delete ANY public or private note record note even if it is marked private and the user is not the owner.
Notes Administrators are also allowed to delete Global Ranges created by other users. Previously, named global ranges (prefixed by a *) for viewers and reports could only be deleted by the user that created them. If that user left the firm, the range could not be deleted. In this release, users flagged as a Notes Administrator may delete global ranges defined by other users. Note that ranges are deleted by double-clicking and answering Yes to Remove Selected Range prompt.
Time Entry Admin?
This field is not currently supported.
Scroll down to see the following buttons:
If several users will be employing the same or similar DB Analytics, the Clone Profile button on the User record (scroll down the parent to access this button) may be used to clone the settings from a selected user who already has them set up.
The Reset Profile button should only be used to clear a user’s DB Analytic configuration if there is a problem accessing it.
’Scroll down the parent screen to access this button; it is designed to be used with DBAnalytics. This button enables you to export the User Profile (KPIs, Tab Groups and Tabs), for this user as an object (.obj) file. This object file may then be imported to provide a preset profile for other users. For example, a support person could use this file to expedite user setups for a new installation.
The Export Function no longer exports any KPis that are set to Active: False, or Shared. Only active:true KPI's are exported. Clicking this button exports the User's Profile to the DashboardProfiles folder in the main SAMPro directory. This folder will be created if it does not exist.
The file will use the naming convention exported_DBAnalyticsFrom_databasename_For_userid.obj.
Scroll down the parent screen to access this button; it is designed to be used with DBAnylytics. This button enables you to import a Profile (KPI’s, Tab Groups and Tabs) from an object (.obj) file. For example, a support person could use this file to expedite user setups for a new installation. The Import Function only imports Active:True KPI's.
When you click this button, a selection box will appear allowing you to choose from the appropriate objects located in the main SAM Pro directory. Click on a file to select it, and then click Select to import the DBAnalytics profile, or Cancel to cancel the operation. When the user next logs into DBAnalytics, the imported profile will be installed.
Password Expiration: (date format mmddyyyy)
The date on which this password expires. If a user attempts to login after this date, a message that this user/password are invalid will be displayed. record. Note: if you are not implementing this security feature, be sure to leave this field blank (set to the default value of 01/01/1900).
Password Renewal: (date format mmddyyyy)
This field specifies the date by which this user must enter a new password. It should be initialized (e.g., to today's date, or a week from today) if the Password Days field is set in the User Group/User Group Functions record. When the user enters a new password, this field will automatically be updated to the current date plus the number of Password Days specified in the User Group record. Note: if you are not implementing this security feature, be sure to leave this field blank (set to the default value of 01/01/1900).
Failed Login Attempts:
This field is a counter that registers the number of times this user has entered his password incorrectly at the login. If this number exceeds the Max Failed Login Attempts field in the User Group record, the user will be unable to login until this counter is reset to zero (or a number less than Max Failed Login Attempts).
Group Id:
A valid User Group Id. Double-click on this field to select from a list of Group Id's. The User Group controls the User's access to records, reports and functions.
Security Id:
This field should only be filled in if your firm implements multiple regions or branches on a single database and this is a non-global user. Double-click on this field to select from a list of Id's.
See Global Setting Security Override to set the security of work orders and other records according the security of the Job, not the user.
See Block Users from Seeing Records with Specific Security for a registry to limit user's access to specific Companies by Security (Intercompany installations).
Employee Id:
This field is required if TimeAnywhere will be used for employees to enter their own time or that of their crews.
Location Id:
If this user runs the Stock Status Report, this field should be completed to provide the default location for this report. Also, if this user runs Fill COP and SHOP Backorders function, this field should be completed to provide the default location for this report.
Contact Id:
This field specifies the record that supplies the e-mail, phone and address contact information for this User.
Notes:
Email Address: Email Fax: Email Address 2: (formerly Email Pager)
These display-only fields default from the Contact record. To update them, right-click on the Contact Id and edit the Contact record directly.
Branch Id:
The home Branch for this user.
Branch Filter:
If several Branches will be sharing information, this filter should specify which Branch information this user should see (within his security parameters) by default. If the user wishes to see additional information, the Branch Range in the Record field may be cleared to allow access to other Branch information.
Hard Blocking: Note that if Hard Blocking is turn on via registry (in Registry Entry Global Setting ) the user will only be able to view the information defined by this filter. To enable the user to also see global records (not associated with any branch), the text in the Branch Filter MUST begin with a comma.
Examples: Branch Filter Settings when Hard Blocking is Enabled
See Global and Branch A Records ,A
See Global, Branch A and Branch B Records ,A,B
PM Reporting Filter:
If this user is a project manager, this field may be used to limit reporting information to only those project manager id(s) listed in this field. Note that a report must include the Project Manager key for this feature to be implemented. If completed, this range also limits a user’s access to only those project manager-related records (e.g., jobs) included in this filter. If this field is blank and this user has access to the Project Manager viewer, he or she will be able access any project manager viewer in the system.
Version 9.0 and above also applies the User's PM filtering to the Work Order viewer. The Project Manager is connected to the Work Order via the Work Order's parent Job. A list option, Work Orders By Project Manager Id supports this enhancement.
Sql= Support: This range provides full support of the various options available on a typical range screen, include sql= specifications.
Example:
Suppose this user is a project principal, with project managers BSMITH,JCONNER and KFEIN working under him. In this case, the Project Manager Reporting Filter would be filled in as follows:
BSMITH,JCONNER,KFEIN
If this user is a project manager, filling in just his Project Manager Id would automatically filter reports to the projects he manages.
Discipline Filter:
This field may be used to limit job reporting information to only those Disciplines listed in this field. Note that a report must include the Discipline key for this feature to be implemented. Data-Basics’ standard job cost reports include this key.
Location Filter:
In the Back Orders Fill functions for COP and Shop Orders, the back orders are initially listed only for the Location Id’s listed in this field. If the user's Location Filter is blank, the system will take the initial location from the user's Location Id field as before.
Other Tab
User Security 1-3:
These fields are designed for use with certain custom analytics (KPI's). They are not currently referenced by the SAMPro code.
Additional Profiles Tab
If filled in, this table enables the user to switch their security levels (and, optionally their user group) without logging in under a different id. This feature is useful for administrators logging on to maintain branch data. Switching Security Identities builds a new function list that is determined by the User Group from the selected Security Identity plus each of the Additional User Groups.
When the user logs on, their security level will be as defined in the main (upper) section of the User record. If their security table is empty, the user will not be able to switch security. If their security table contains one or more lines, they will be able to switch to one of the alternate securities listed in their table. The Switch Security Identity function may be accessed from the Special tab of the Folders viewer.
Alternately, you may do so from the menu by selecting:
Functions > Special > Switch Security Identity
Next, the system will display a box listing the alternative securities available for this user; simply click on the desired security to log on. The user's current security id will appear in the title bar of the Data-Basics windows.
Security Id:
Enter an alternate Security Id for this user or double-click on this field to select from a list.
In Version 9.0 and above, multiple lines may be entered per Security Id to support access to multiple User Groups (in addition to the Additional Groups tab) when the user switches to the specified Security.
Example:
User Header:
Security: A User Group: Service
User Additional Groups: Inventory
User Additional Profiles:
Security: B - User Group: Service
Security: B - User Group: Purchasing
Security C: - User Group: Purchasing
When the user is logged on as:
Security A they can access: Service, Inventory
Security B they can access: Service, Inventory, Purchasing
Security C they can access: Purchasing, Inventory
Group Id:
Switching Security Identities builds a new function list that is determined by the User Group from the selected Security Identity plus each of the Additional User Groups. If this field is left blank, the Group Id from the Main tab will be used when switching security.
Branch Id:
If this field is completed, the user’s branch membership will also be changed when the user switches his/her security.
Note: Registry Entry to Specify Security Exceptions by Record
A registry entry (sys-securityexceptionsbytable) can be used to force the security of newly created records to global security, regardless of the security of the user.
The following fields may be accessed by clicking the Magnify button.
Branch Id: Location Id:
Branch Filter: Location Filter: PM Reporting Filter:
If completed, the system will now also switch these fields and filters when security is switched.
Additional Groups Tab
This tab enables users to belong to other Users Groups in addition to the primary one specified in the upper portion of this viewer. The Group Id in the parent determines the password settings used during the login process. After the initial login, the available functions are determined by the parent User Group plus each of the Additional User Groups.
Example:
A user that handles both Service Management and Purchasing functions could be assigned to the Service Group in the User Parent record, and the Purchasing Group in the Additional Groups tab.
Important Note: for report scheduling purposes where a User Group is specified, the system only considers the primary (header) User Group Id referenced in the User record. The User record’s Additional Groups tab is NOT evaluated when compiling the recipient Email Addresses.
Registry Tab
Key: Value:
These fields may be used to add to / override sys-ffv-global-settings for this User. Since these settings are loaded when the user logs on, he or she must log on after User Registry changes are made to see them in effect. Other options are only intended to be used on this tab.
See User Registry Entries for options designed to be used on this tab only, including maxpoamount (limits the dollar value of a released PO created for this use. This may also be used to filter which employees a Foreman can manage in TimeAnywhere 2.0.
See Registry Global Settings (sys-ffv-global-settings) for additional options that may be used on this tab.
DB Analytics: also see User Registry Entries for individual overrides for the DB Analytics Dashboard.
CRMAnywhere: see CRM Gmail Calendar for the settings needed to interface with Google Calendar.
UserLogonSummary Tab
This tab summarizes the SAMPro versions this User logged onto and if they are actively using the software.
VersionNo:
The SAMPro Version Number which was/is being used.
Important Note: A User must log off and back on SAMPro to be running the currently installed version. If this user has not done so, they may be running a session using an older version of the software which can lead to inconsistent results.
First Used - Last Used:
The first and last date a session for the SAMPro version was active.
Active Sessions:
The number of currently active sessions for this version.
Successful Logins - Failed Logins:
This tab lists when number of successful and failed logins by SAMPro version.
Apps Tab
This tab is reserved for future use.
App Name: Last Session Id:
Reserved for Future Use.