Prev
Next
Forums S3 Security

Revisiting Company Level Security

Sort:
You are not authorized to post a reply.
Author
Messages
Greg Moeller
Veteran Member
Posts: 1498
Veteran Member
5/18/2011 3:26 PM
    I see the previous thread posted on Company level security, but would like some more clarification/revisit.

    We have had no luck here trying to get company level security to work, and now we are going to be bringing on another company and trying to fold them into our existing LS security.

    Although setting up the new company shouldn't be difficult, they shouldn't see anything but themselves...  there will be existing users here that will also need access to the new company.  I'd like to know how others would address this.

    Anyone willing to share the rules/setup that they have with Genesis Health?

    Thanks,
    -Greg Moeller
    Unix Administrator
    Derek Czarny
    Veteran Member
    Posts: 63
    Veteran Member
    5/20/2011 5:17 PM
      We are actually in the beginning phases of our Lawson Security implementation. Our request to the Lawson consultant is to do company level security. What are some issues that you are having with company level security? Are you using the Company element to do your security?
      Greg Moeller
      Veteran Member
      Posts: 1498
      Veteran Member
      5/20/2011 5:26 PM
        We got through our security implementation and have been live for a while and now we decide we need to secure by company.

        We've tried to add this to our existing security classes/roles but we've found that whatever we did broke those roles/classes. We had to remove the security class that limited by company to get them working again.

        This was a while ago, so I'm just trying to remember everything off the top of my head... but the paragraph above was the biggest thing.
        Gary Padgett
        Veteran Member
        Posts: 90
        Veteran Member
        5/23/2011 3:39 PM
          We use the company control attribute in Lawson Security. One thing that was a "gotcha" for us originally is that, if you use activites, the "security code" in AC00 is checked against the company control attribute. All of our activity groups were mapped to a code (9999) for instance and we got security violations all over the place until we added 9999 to our company control for the users who needed to access activities.
          Greg Moeller
          Veteran Member
          Posts: 1498
          Veteran Member
          5/25/2011 1:13 PM
            Thanks, Gary, I see that we have our AC00.1 set to a security level of 999, so perhaps adding 999 to the company control attribute would be best for us.
            Greg Moeller
            Veteran Member
            Posts: 1498
            Veteran Member
            5/27/2011 6:12 PM
              Noticed the other post mentioned something about being careful about ESS, and doing more research here, I find that is what really broke about our first attempt at company level security.
              Can anyone clear up what in particular was meant by "Be careful about ESS"?
              You are not authorized to post a reply.