How is security handled in Data Loaders?

Security within Data Loaders is controlled using standard QAD security logic. There are
three levels of security built in to each Data Loader to ensure that QAD data does not
get into unauthorized hands: QAD credentials, QAD groups (menu access), and QAD site/
entity access

QAD credential level security.
When a user clicks an action button within an Excel
file, to download from or upload to QAD, the first thing they will see is the prompt to
enter QAD credentials – user id, password and domain. Without proper credentials, a user
will not be able to use the Data Loaders tool.

QAD group or menu access security.
This security level authorizes a user based on
the types of tasks they have permission to perform and information they can access. For
example, a user has the credentials to use the Data Loaders tool to create Item Master
records and similar kinds of tasks, but is not authorized to make journal entries. That
user would not have access to Journal Entry Data Loader. If they try to access Journal
Entry Data Loader, the user will receive a message telling them don’t have access to
that menu.

QAD site/entity access security.
This level controls the user’s site level authorization.
For example, if a user only has access to entity 1000 records, and tries to upload or
download records from entity 2000, Data Loaders will deliver a message telling them they
do not have access to that entity.

A note about Field Security.
Field security is not implemented as is in Data Loaders,
but is handled with different tools for different groups. For example, credit terms are only
able to be determined and entered by Accounts Receivable, but a CSR may need to see that
information (but not be able to modify it). To accommodate this, Data Loaders would have
two separate tools within the same master file that would allow different levels of access
to different user groups.

Join our mailing list
to stay informed about our solutions