DataPipe Security
DataPipe provides a layer of security
and data access permissions in addition to what you set up
in your operating system, network and database. It won’t
override any restrictions that you’ve set up at these
primary levels. DataPipe requires a username and password
for any user logging on to the system, and may be
customized on a per-user and per-form basis as to what
data access is allowed. The system administrator (SA) or
database administrator (DBA) can fine-tune very
specifically who can see and do what in their DataPipe
system.
Defining Database “Views”
Unlimited numbers of “views” for single
users or user-groups can be defined in your database.
These user-specific views are basically sub-sets of the
“master” database tables. For example, one may want to
limit a user or user-group to seeing data from a single
plant, even though information from all plants is in the
master database. You can control and limit data access for
every user on every form in the system, if desired.
Database views provide an added level of security without
a lot of complicated database partitioning.
HIPAA Compliance
Learn more about DataPipe and
HIPAA compliance.
The Sarbanes-Oxley (SOX) Act of 2002
Learn more about DataPipe and
Sox.
Multi-User Security
- Built-in security features safeguard
data files, while controlling and monitoring employee
access.
- Integrated system security includes
record-level locking, date stamping and database
validation tools.
- User level security permissions
restrict access, limit add, edit and delete functions
and vary the available menus.
|
