PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 08/25/2017 10:25 AM by  Russell Spreeman
Just wondering what everyone else does...
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages
CindyW
Private
Private
Veteran Member
(409 points)
Veteran Member
Posts:159


Send Message:

--
08/16/2017 2:10 PM
    When you create your security classes, do you generally have much overlap as far as the forms/tokens?  Do you try to minimize that?  Is it a headache to have much duplication?  We are still testing our security and hope to be using it in production soon, but I am still trying to wrap my head around the best methods.  It's such a beast!
    Roger French
    Private
    Private
    Veteran Member
    (1266 points)
    Veteran Member
    Posts:522


    Send Message:

    --
    08/17/2017 1:09 PM

    Every situation and set of requirements is different.

    Overlap may or may not be intentional in your situation.  In whatever situation you have, you should probably have some reporting mechanism after your security roles are built to confirm and review any kinds of overlap. I've seen both lots of overlap and also little or no overlap.

    Russell Spreeman
    Private
    Private
    Veteran Member
    (128 points)
    Veteran Member
    Posts:52


    Send Message:

    --
    08/25/2017 10:25 AM
    My attitude has always been to try to minimize the proliferation of security classes. When there is a new user or one who has changed duties I ask the supervisor if there is someone else who is already using Lawson in the same way, and assign the new person's security to match the existing user. This was even more important back in the LAUA days (where I am still living) but even with Lawson Security, having many more security classes to keep track than necessary only makes things more complicated.
    You are not authorized to post a reply.