The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
FLS profiles
Posted: 16 Nov 06 3:35 PM
|
fiogf49gjkf0d How are field level security profiles applied to the users? That is if a user has more then one Sec profile assigned to them how and in what order are they applied or is the least restrictive profile applied and the rest ignored?
Thanks for the help ML |
|
|
|
Re: FLS profiles
Posted: 16 Nov 06 3:40 PM
|
fiogf49gjkf0d The first one found is applied. There is no logic applied to determine least or most restrictive.
Timmus |
|
|
|
Re: FLS profiles
Posted: 16 Nov 06 4:00 PM
|
fiogf49gjkf0d Thanks for the answer Timmus How do you get a user down to a single profile? |
|
|
|
Re: FLS profiles
Posted: 16 Nov 06 4:21 PM
|
fiogf49gjkf0d You have to structure your security hierarchy differently to accommodate this. Keep in mind that SalesLogix teams are often used for multiple reasons. Here are the most common:
1. Company Org Chart - manager and subordinate hierarchy
2. Plugin Security (releasing plugins to teams/departments)
3. Record Ownership
It is the mixing of these concepts that usually leads folks down the wrong path. Record Ownership is the only case where FLS profiles come into play, so it is important to keep this as streamlined as possible. To avoid multiple FLS profiles per user per record owner you must ensure that a user is never a member of a team more than once - this can occur when a user is a member of multiple teams that are nested within one team.
For example, Ted belongs to the Arizona and California teams. Both AZ and CA belong to the South West team and each has a different FLS profile applied.
In this case I would argue that there is no benefit to the South West team owning data. It is a regional/organizational attribute and is not really an owner of records. AZ and CA should be the owners of the records and this will allow you to apply different FLS profiles for Ted (if needed).
Now, if AZ and CA do not require differing security, then I would say get rid of AZ and CA and just use South West. It really depends on what the business requirements are. Any time you must assign a FLS profile to a specific relationship such as "when Ted sees accounts in AZ he can not edit the Account Name but he can when they are in CA", that leads me to believe that you need two teams for RECORD OWNERSHIP. It does not matter that the sales team does not really have a CA or AZ team - this is SalesLogix security not an org chart.
I hope that helps - it is not a simple task to architect record ownership and FLS profiles.
Timmus
|
|
|
| |
|
Re: FLS profiles
Posted: 28 Apr 16 3:41 PM
|
I have a situation..
One user belongs to 2 different teams (Operations and Operation Super)
If I assign Operation only, then function A works.
If I assign Operation Super only, then function B works
If I assign both, then function B only works.
How do I make both function A and B work?
Thanks
Gopinath Srinivasan |
|
|
|