Company Level Security

 12 Replies
 0 Subscribed to this topic
 15 Subscribed to this forum
Sort:
Author
Messages
Jay Riddle
New Member Send Private Message
Posts: 0
New Member

Using the new Lawson security is there a quick way to setup company level security so only certain users can see a company? 

MattM
Veteran Member Send Private Message
Posts: 82
Veteran Member
Create an element rule on COMPANY that states if COMPANY=="company number" then no access else all access and apply it to whichever roles you dont want to have that company.
John Henley
Send Private Message
Posts: 3351
There is a new user attribute in RM called "CompanyControl" (I think that's the name) you can use to avoid hard-coding. =
Thanks for using the LawsonGuru.com forums!
John
Jay Riddle
New Member Send Private Message
Posts: 0
New Member
We are on 9.0.0.4 so I think we do not have the CompanyControl attribute. Also even with an element rule wouldn't we need to go through every form and add in isElementAccesible(....)??? Going through every form on every security class is what I would like to avoid if possible.
MattM
Veteran Member Send Private Message
Posts: 82
Veteran Member
The company and process level elements are different, they use the 700/900 security that LAUA used when defining data level security. If you create a rule on company and assign that security class to a users role, the effect is global. If you wrote an element rule on employee or such, you would have to write the isElement... rule on each token. If you use ESS, be careful of the impacts to a users access to the company they exist in. Hope this helps.
StacyR
Send Private Message
Posts: 5

MattM - 

Would you add this to an element or element group?

Jay Riddle
New Member Send Private Message
Posts: 0
New Member
We tried both a element and an element group rule and it didn't seem to deny access. Is the rule on a specific type of element group? On a related note: We do not have any employees in the company we are attempting to lock down so we I wouldn't think we will run into ESS/MSS issues.
Mark F. Hardy
Veteran Member Send Private Message
Posts: 45
Veteran Member
I did as you said in your post of 03/18/2010 7:44 PM. No luck. Anything else needs to be done? Thanks!
Mark F. Hardy
Veteran Member Send Private Message
Posts: 45
Veteran Member
This last post was for John Henley. Thanks.
Jimmy Chiu
Veteran Member Send Private Message
Posts: 641
Veteran Member
Add Files to a new secClass Add COMPANY element to the new secClass Add secClass to role Assign role to user if(user.attributeContains('CompanyControl',lztrim(COMPANY))) 'ALL_ACCESS,' else 'NO_ACCESS,' Add value of the company(s) in user RM "CompanyControl" that they should have access to. If they can still access everything, you have another rule overriding the company element.
Mark F. Hardy
Veteran Member Send Private Message
Posts: 45
Veteran Member
I just saw this post.  I think I understand what you are saying.  I'll give it a go.  Update to follow.
Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
Be careful setting this up for ESS access. I believe that there is the entry in AC00.1 under the 'Security' field. I've heard that you also need these set up in your company control attributes to have ESS work correctly... Not sure why.
LKEN2002
New Member Send Private Message
Posts: 3
New Member
I saw this post while trying to do the same thing. I have to secure a company and I tried the group and element and it hasn't secured it. Not sure what else I am missing. Any help would be appreciated.

 

Update:  tried it again with just element this time and it works!!