Download presentation
Presentation is loading. Please wait.
1
Shawn Dorward – InterDyn Artis
GP Related Security Presented by Shawn Dorward – InterDyn Artis Tweet During today’s #GPUGCharleston
2
SHAWN DORWARD Implementation Consultant
GPUG Member for 6 Years! Favorite Benefit: Endless Resources (GPUG is the GP Manual!) Long Time Dynamics GP User and GPUG FAN! 17+ Years using Dynamics GP GPUG All-Star GPUG Summit Planning Committee (2014, 2015, 2016) & 2017!! GPUG Board of Advisors (2015) Carolinas Regional Chapter Leader (2012-Present)
3
Security for GP Related Products
Learning Objective: Comprehensive review of security-related practices with Dynamics GP related applications
4
Session Overview Security Introduction Field Level Security
Directory Accounts with GP MR Security Excel Reports SSRS Reports Account Security
5
Dynamics GP Application
Security Overview Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS DYNGRP Dynamics GP Security SQL Server
6
Dynamics GP Application
Security Overview Does not look at GP Security Does not Use DYNGRP Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS DYNGRP Dynamics GP Security SQL Server
7
Dynamics GP Application
Security Overview Does not look at GP Security Accesses SQL via DYNGRP GP User Name does not allow SQL Access outside of GP GP Password is encrypted and not usable without the application and DYNGRP Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS DYNGRP Dynamics GP Security SQL Server
8
Dynamics GP Application
Security Overview Uses GP Security Accesses SQL via DYNGRP GP User Name does not allow SQL Access outside of GP GP Password is encrypted and not usable without the application and DYNGRP Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS DYNGRP Dynamics GP Security SQL Server
9
Dynamics GP Application
Security Overview Grants Access to Reports, Windows, and Forms Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS DYNGRP Dynamics GP Security SQL Server
10
Dynamics GP Application
Security Overview Access to SQL Via Application Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS DYNGRP Dynamics GP Security SQL Server
11
Dynamics GP Application
Security Overview Notice Power Users and other named users in GP can only access SQL via DYNGRP and the application Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS DYNGRP Dynamics GP Security SQL Server
12
Field Level Security What is it? How do I use it?
When shouldn’t I use it? How to Manage Security
13
Field Level Security Common Questions answered by FLS:
Can I password a field? Can I remove or hide a field?
14
Field Level Security Use the Field Level Security window to restrict access to any field, window, or form. You can apply a password or make a window or form unavailable. It also allows you to hide, lock, or apply passwords to fields.
15
Field Level Security Field Level Security Not available?
Check Registration
16
Dynamics GP Application
How does it Fit? Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS Field Level Security is separate from GP Security DYNGRP Dynamics GP Security SQL Server
17
Dynamics GP Application
How does it Fit? Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS Field Level Security is separate from GP Security
18
Dynamics GP Application
How does it Fit? Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS Field Level Security is separate from GP Security
19
Dynamics GP Application
How does it Fit? Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS Field Level Security Field Level Security Field Level Security Field Level Security is separate from GP Security
20
Dynamics GP Application
How does it Fit? Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS Field Level Security Field Level Security Field Level Security Field Level Security is separate from GP Security DYNGRP Dynamics GP Security SQL Server
21
Field Level Security – Let’s Put it to work!
Company List Users Security ID List
22
Field Level Security Lets Remove “DELETE” button from Payables Batch
23
Field Level Security First – Add a new Field Security ID
24
Field Level Security Next Choose the Product, Form and Window
25
Field Level Security Choose the Security ‘Mode’
26
Field Level Security Setup Password ID if using Password (Why are we not able to password the delete button?)
27
Field Level Security Passwords can be changed or reset by a user with access to field level security Once the Field Security ID is setup, it must be assigned to user(s) and company(s).
28
Field Level Security
29
Field Level Security Click the user(s) Click the company(s)
Select the ID(s) Notice Pending # Hit Apply
30
Field Level Security Password Before You must enter a password before getting access to a field. Password After You must enter a password after modifying a field for the changes to be saved. Warning Before A warning will be displayed and access to that field will be denied. Lock Field You can’t use or modify the field. Disable Field The field will be displayed but it will not be available. Hide Field The field won’t be displayed. Password Window You must to enter a password before access to the window is permitted. Disable Window Enter the system administrator’s password to have access to the window. Password Form Users/classes must enter a password before access to the form is permitted. Disable Form You must enter the system administrator’s password to modify the form.
31
Field Level Security Tips User must log out and back in
Use in Test first Use modifier to find field ID Use ‘Print’ to generate ‘audit’ report
32
Dynamics GP Application
Field Level Security Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS Field Level Security Field Level Security Field Level Security Questions? DYNGRP Dynamics GP Security SQL Server
33
Directory Accounts with GP
What is it? How do I use it? When shouldn’t I use it? How to Manage Security
34
Directory Accounts with GP
Windows Account Select the Windows account to assign to the user ID. The Window account cannot be assigned to more than one Microsoft Dynamics GP user. This field is not available for sa and DYNSA users.
35
Directory Accounts with GP
Web Client Only Option If this is marked, the Directory account is required! No SQL User Account created
36
Dynamics GP Application
How does it Fit? Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS Field Level Security Field Level Security Field Level Security DYNGRP Dynamics GP Security SQL Server
37
Dynamics GP Application
How does it Fit? Dynamics GP Application
38
How does this fit? Dynamics GP Web Client SA DYNSA POWERUSER
ALL OTHER USERS Field Level Security Field Level Security Field Level Security Directory Accounts Not Available Shared SQL User that is assigned DYNGRP Dynamics GP Security SQL Server
39
How does it Compare? Dynamics GP Web Client Only Dynamics GP Security
SQL Server DYNGRP Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS Field Level Security SA DYNSA POWERUSER ALL OTHER USERS Field Level Security Field Level Security Field Level Security Directory Account Not Available Shared SQL User that is assigned DYNGRP Dynamics GP Security SQL Server
40
How does it Compare? Dynamics GP Web Client Only Dynamics GP Security
SQL Server DYNGRP Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS Field Level Security SA DYNSA POWERUSER ALL OTHER USERS Field Level Security Field Level Security Field Level Security Shared SQL User that is assigned DYNGRP Dynamics GP Security SQL Server
41
Directory Accounts with GP
If user accesses GP from thick client, GP User name is used If user accesses GP from web client, AD account is used.
42
Directory Accounts with GP
Dynamics GP Web Client Questions? SA DYNSA POWERUSER ALL OTHER USERS Field Level Security Field Level Security Field Level Security Directory Accounts Not Available Shared SQL User that is assigned DYNGRP Dynamics GP Security SQL Server
43
MR Security What is it? How do I use it? When shouldn’t I use it?
How to Manage Security
44
MR Security Connection to DB
Windows Authentication? SQL User? For companies that use the data mart, security is based on the user’s Windows authentication. A separate user name and password are not required for company connection access.
45
MR Security Users AD Based
46
MR Security Groups (Not AD!)
Groups are a great way to manage permissions to companies, reporting tree units and folders.
47
MR Security Assign new users to groups to make administering MR security much easier!
48
MR Security Use groups or users in Tree Security!
49
MR Security MR Roles
50
MR Security
51
MR Security Report Library
52
MR Security
53
How does this look? MR Application MR Application Legacy DataMart
SQL Server MR Group MR Role MR Application Legacy Company Connection User Access Active Directory User Stored “Service” Account SQL Server MR Group MR Role MR Application DataMart Company Connection User Access Active Directory User Windows Authentication
54
Excel Reports Security
What is it? How do I use it? When shouldn’t I use it? How to Manage Security Want to Deploy? Tools/Setup/System/Reporting Tools Setup Click Excel Reports Tab Pick Location to Deploy/Publish Pick Company Name to Deploy Select Publish
55
Excel Reports Security
Authenticated Via AD AD Part of SQL Role Create New AD Group Assign Group access to SQL Role Copy/Paste with Connection File Share File Folder
56
Excel Reports Security
SQL Server SQL Reporting Role Excel Reports User Access Active Directory User
57
SSRS Reports What is it? How do I use it? When shouldn’t I use it?
How to Manage Security
58
SSRS Reports Remember those RPT_Roles? Use them here too!
Folder Security Report Security Active Directory Groups Datasource Settings
59
SSRS Reports System Roles (From Reporting Services)
60
SSRS Reports Role Assignments (From Reporting Services)
By User or Group (Both from Active Directory)
61
SSRS Reports Role Assignments Customize?
62
Reporting Service Role
SSRS Reports SQL Reporting Role Reporting Service Role SSRS Reports User Access Active Directory User SQL Server
63
Let’s Put it all together!
Dynamics GP Security SQL Server DYNGRP Dynamics GP Application SA DYNSA POWERUSER ALL OTHER USERS Field Level Security ??? Dynamics GP Security SQL Server Shared SQL User that is assigned DYNGRP Dynamics GP Web Client Only SA DYNSA POWERUSER ALL OTHER USERS Field Level Security Directory Account Not Available SQL Server SQL Reporting Role Excel Reports User Access Active Directory User SQL Reporting Role Reporting Service Role SSRS Reports User Access Active Directory User SQL Server SQL Server MR Group MR Role MR Application DataMart Company Connection User Access Active Directory User Windows Authentication SQL Server MR Group MR Role MR Application Legacy Company Connection User Access Active Directory User Stored “Service” Account
64
Let’s Put it all Together
GP WebClient SQL Excel Reports MR SSRS Reports User Name sdorward domain\sdorward Windows Account Access to SQL DYNGRP N/A SQL rpt_ Role Service Account
65
Account Security Activate Account Security (Do this with a plan in place and a test company first) Tools >> Setup >> Company >> Company
66
Account Security Define Org Structure Categories:
Tools >> Setup >> System >> Org Structures
67
Account Security Define Org Structure Categories:
Tools >> Setup >> System >> Org Structures
68
Account Security Assign Accounts to Category
69
Account Security Assign Org Structure to User Tools/Setup/System/User
70
Account Security Reference:
71
Shawn Dorward @ShawnMDorward Shawn.Dorward@InterDynArtis.com
9/23/2019 3:39 AM Shawn Dorward @ShawnMDorward © 2016 Dynamic Communities. All rights reserved. DYNAMIC COMMUNITIES MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.