Data Protection

Table of Contents

1.0 Personal Data 3

1.1 Personal Data - removal 3
1.2 Objections to Processing 3

2.0 Securing your company data 4

2.1 Data Security 4
2.2 Product Access 4

Data Protection Page 2 of 7

1.0 Personal Data

1.1 Personal Data - removal

Personal data can be edited on all master file records. As example, on the customer
record, select to edit the record, find the field value that you want to edit, insert a new
value, then save the record.

1.2 Objections to Processing

Entities can elect to not receive any marketing material. In Sage 200 Evolution, we have
added a flag on the Customer, Supplier and Contact Person master file to indicate this
option.

Data Protection Page 3 of 7

2.0 Securing your company data

2.1 Data Security

Sage 200 Evolution stores your data in a Microsoft SQL Database. Each workstation with
an installation of Sage 200 Evolution connects to a database.

A dedicated server with advanced security is recommended to host the Microsoft SQL
Database. Install firewalls and ensure anti-virus software is active.

Manage the backups and ensure access is only given to security managers.

Ensure that the connection set up for this database is secure by using strong passwords.

No access should be given to users directly on the Microsoft SQL Database, this right
should be reserved for System Administrators only.

It is good practice to get expert advice to manage your data and its location.

2.2 Product Access

The system’s powerful access control features allow you to work on an exception basis. In
other words, you set the initial rules for what is supposed to happen most of the time.
Then, if necessary, you modify these rules for one or more agent groups or agents.

You set the initial default rules for agent access in the broadest possible terms. Once you
do so, you can then modify the access rules at two levels:

You can set access rules per agent group. Any agent you link to the agent group then
inherits the access settings for that group. If an agent belongs to more than one group, the
system will merge the settings for these groups to determine the access.

You can set access rules per agent. These are the strongest settings, and they override
any other settings that may apply to the agent.

You can mix and match settings at the global level, agent group level, and agent level.
The system will apply the most specific rules when they are present, and move up a level
when they are not.

Data Protection Page 4 of 7

Add Access

 If you wish to allow most agents to create new master records in the modules in which
they work, check this check box.
 If you prevent most agents from creating new master records, uncheck this check box.
 In either case, you can modify this access rule per agent group or per agent.

Edit Access

 If you wish to allow most agents to edit existing master records in the modules in
which they work, check this check box.
 If you prevent most agents from editing existing master records, uncheck this check
box.
 In either case, you can modify this access rule per agent group or per agent.

Data Protection Page 5 of 7

Delete Access

 If you wish to allow most agents to delete master records in the modules in which they
work, check this check box.
 If you prevent most agents from deleting master records, uncheck this check box.
 In either case, you can modify this access rule per agent group or per agent

Rule Access

 In each module, you set rules. For example, you set whether an agent can sell an
inventory item below cost. You set rules in the Access Permission tab of the agent or
agent group.
 If you wish to turn on all rules by default, and then disable them where necessary,
check this check box.
 If you wish to turn off all rules by default, and then enable them where necessary,
uncheck this check box.

System Tree Customisation

 You customise the system tree to simplify the display of program options for agents.
This also lets you prevent unauthorised access to transaction, report, and enquiry
options by these agents.

Login Security

 Enable Login Security to enforce the use of strong passwords.

Data Protection Page 6 of 7

Data Protection Page 7 of 7