User security on fields

(0) Share

Report

Posted on by Community Member

Hi,

I have a question although I have a feeling that what I am trying to achieve cannot be done with standard out of the box functionality.

I have an opportunity and the revenue field has restrictions so basically only named users can see this particular field. That said the named users are not static and can change depending on the opportunity. I'm aware I can use field security profiles and add the users who do have read permissions to see this field but field security profiles are static so I don't think this will work long term as I mentioned the named users do change quite often. Therefore is there another way to achieve what I am after?

Thanks

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

Verified answer

ashlega 34,477 on at

Like (0)

Report

Hi JazB,

I don't think there is a way to do it with the field (maybe, if you add plugins/javascripts.. not sure it's going to be simple though)

As a workaround, you might move that field to a new entity and set up a lookup from the opportunity to that entity. Then use access teams to share those additional records with the appropriate users. It won't be as convenient as having that field on the opportunity, but, at least, you could use out-of-the-box security features.

Was this reply helpful? Yes No
Gopalan Bhuvanesh 11,401 on at

Like (0)

Report

Did you consider Field Security Profiles with Team. The team membership can be modified dynamically.

Was this reply helpful? Yes No
Suggested answer

axelortiz_allegient 185 on at

Like (0)

Report

Hi JazB,

I agree with Alex's response in that it may not be possible to achieve what you're asking with out-of-box functionality. However, you could use the field security profiles/field security feature of CRM if there was a mechanism or process that would assign those named users to a specific team (or teams) and manage the access/visibility to this field via teams associated to a field security profile.

I have used this approach for a similar request at a client and it worked well for them. The caveat is that whenever a user changes roles, they also need to have their team membership revoked or added depending on the case.

Hope this helps.

-Axel-

Was this reply helpful? Yes No
ashlega 34,477 on at

Like (1)

Report

Hi Axel,

the main reason I mentioned that other entity is that (it seems) what JazB is looking for is field access "per record". If there are two opportunities, then the same user might have access to the field on one opportunity and might have no access to the same field on another opportunity. If that's the case, field security profile (either with teams or without) will give access to the field on both opportunities instead of just one.. unless I'm missing something..

Was this reply helpful? Yes No
axelortiz_allegient 185 on at

Like (0)

Report

Hi Alex,

I see what you're saying. I had a different interpretation of the question in that the users may vary (eg. move on to different roles, etc.) instead of the opportunity having an attribute or type that would restrict visibility.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks everyone, I think the approach that Alex suggested sounds like the most plausible as it's not the user roles that change frequently rather the the individual users who can see the field, so access teams sound like the best option.

JazB

Was this reply helpful? Yes No