1

Managing Permission

Settings and Overall System

Security # A L L I A N C E 2 0 1 7

2

YOUR PRESENTERRhett WilliamsMaster ConsultantJOINED SPARKROCK IN 2009

3

In t roduct ion

4

Basic Principles

Four Main Elements • Permission sets• User set-up• Workflows• Change Log Security and segregation of duties is dependent on the size of the team

Avoid operational users having super user permissions (even for small teams)

5

NAV Permiss ion

6

Initial Set-up of Permissions

Make ongoing maintenance as easy as possibleDefine rolesDefined functions that make up the roleSplit up functions such as create and postBuild permission sets to these functionsSeparate read permissions from insert, modify and deleteAltus Base permission sets and recorder

7

Some Permission Features

Security filters

Company specific permissions

User groups

8

User Set -Up

9

User Set-Up

Application side – under operational management control

Used to manage field level security and security over specific functions Useful for customized field level securityOverrides of posting windows (best practice to use only as an override)

10

Workflows

11

NAV Workflows

Workflows contribute to overall system security

Transactions require approvals before printing or posting (record restriction)

In theory, workflows can be applied to master data changes

12

Change Log

13

Change log

Neglected aspect of security

Switch on for sensitive master data tables.

‘All fields’ and ‘some fields’

Report on changes to certain tables, sign off and keep

14

EVALUATIONSP L E A S E TA K E 5 M I N S T O C O M P L E T E A S E S S I O N E VA L U AT I O N .

WIN ME!One lucky survey will take home a

Ecobee Smart Wi-Fi Thermostat

15

THANK YOU FOR LISTENING

@ S PA R K R O C K I N CW W W. S PA R K R O C K . C O

M