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!
|
|
User Field Security
Posted: 01 Jul 09 7:38 AM
|
I am attempting to create a user field security profile that will not allow users to change opportunity information. I thought that this could be accomplished by making the opportunity table read only, but the users continue to be able to alter fields such as the opportunity description. Am I going about this in the wrong manner, or is there a quirk to SLX?
SalesLogix 6.2.6 |
|
|
|
Re: User Field Security
Posted: 01 Jul 09 8:23 AM
|
Field Level security is tied into Ownership and Team Membership.
So, if a record is owned by a Team, I will have to change the Profile of each user within that team to have the profile apply to them. I have seen many people get confused with the "Default Security Profile" setting, but that is just the profile that that user is assigned to by default as you add him/her to Team (including User Security Teams), not his Security Profile.
With that in mind, you need to do the following:
- Select a set of records to test with.
- Select a Test user to test with
- Review the ownership of those records.
- If the records are owned by Teams, go into the Teams module and locate the Team(s) in question. Then locate your test user and change his Security Profile within the team.
- If the records are owned by Users, go into the Owner's Profile and on the "User Team" list, select your Test User and adjust his Security Profile
|
|
|
|
Re: User Field Security
Posted: 01 Jul 09 8:35 AM
|
| In our case, we have 'Everyone' as the default owner in SLX. How does that change the approach to field security? |
|
|
|
Re: User Field Security
Posted: 01 Jul 09 8:44 AM
|
You can't do it with Everyone as the Owner.
You will need to Create a Team and then assign all your users to it (with your Custom Security Profile if applicable), then Realign all your Records so that they are owned by this team.
Going forward, as new users are added/removed from the system you will need to add them to this profile (with the Custom Security Profile if applicable) |
|
|
|
Re: User Field Security
Posted: 01 Jul 09 9:06 AM
|
Are there any other options to limit the ability of users to alter specified fields without coding it into, in this case, the Opportunity Details form?
|
|
|
|
Re: User Field Security
Posted: 01 Jul 09 9:12 AM
|
Are there any other options to limit the ability of users to alter specified fields without coding it into, in this case, the Opportunity Details form?
|
|
|
|
Re: User Field Security
Posted: 01 Jul 09 9:18 AM
|
Not that I am aware of.
You either Code it into the view or you use Field Level Security. |
|
|
| |
|