DataPipe - The Complete EH&S Data Management Software Solution

Knorr Associates Inc. - Providing EHS Software Solutions Since 1979 (34 Years!)

EHS Software, Environment and Waste Management, Occupational Health and Medical, Industrial Hygiene and Safety

Welcome DataPipe Overview Our Approach DataPipe In Depth FAQs Online Demo Customer Support Contact Us

New Page 1

10 Topics for Assessing EH&S Software:

16 of 23

Security:
How does the system deal with security and permissions? How do you control who sees and who has access to forms, reports and even specific data? Can you set up role based security? What type of user authentication will DataPipe use (i.e. Windows Authentication, LDAP, Active Directory)

In addition to any security mechanisms your organization has implemented, DataPipe has its own built in security. Users, or groups of users, are given permission to forms, reports, data and other sensitive areas of DataPipe. Whomever you assign to administer DataPipe has control over what users see and what they can do. In addition, you may also control what they can do within the database. Some user may be allowed to see only certain sets of data. So while two users could in fact be looking at the same form/database, they each may have unique views. There are many levels of security and protection within DataPipe. How strongly you want to enforce them is up to you. Restrictions are controlled via roll-based security. You can set up as many rolls or groups as you want. DataPipe will use windows authentication, LDAP, Active Directory or other authentication security protocols to access the system, if you choose.

If you choose to have DataPipe accept authentication of a user from your network (this may be set on a user-by-user basis), DataPipe will take the information from your network authentication mechanism (e.g., Active Directory). If you have some specialized form of authentication, if there is an API available to get the information from that system we can provide you with an alternate user authentication routine that uses that system. For example, some single login systems create a “cookie;” in this case the DataPipe authentication routine would read the cookie for the user information.