Just wondering what everyone else does...

Sort:
You are not authorized to post a reply.
Author
Messages
CindyW
Veteran Member
Posts: 169
Veteran Member
    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
    Veteran Member
    Posts: 545
    Veteran Member

      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
      Veteran Member
      Posts: 61
      Veteran Member
        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.