Permissions for profile fields and categories
complete
Angela Gaida
complete
As of version 5.2 of Linchpin Suite and 2.2 of Linchpin Essentials this feature is now available.
D
Dominika
Hi,
Do you already know what the new functionalities will be? I'm interested in limiting visibility on specific groups. Do you know when the updates can be expected?
Angela Gaida
Dominika: For a field, you will be able to restrict visibility to certain confluence groups (for example: field "phone number" is only visible to members of the group "employees".)
I can't give an estimate on the time frame yet; but I can say it doesn't seem likely that it will be available for the September update. It's a feature that requires more work than is visible at first glance.
Angela Gaida
In the context of this feature, we were also looking at the existing option for "hidden" fields. That option ensures that a given profile field is existent, but doesn't show in the profile and various other places.
We probably will have to make slight changes to this option, so I would be very interested to learn about how it's used to ensure we don't break anything for you. So my question is: do you use the "hidden" option for fields? If so, what exactly is your use case? What kind of information is in that field, what do you do with it, why do you not want it to show in the profile?
If you can give us some insight there, that would be highly appreciated. In case you don't want to share publicly, feel free to email me at agaida@seibert-media.net. :)
Angela Gaida
You wouldn't believe the complexity of this beast. But I hope we will prove more stubborn than the issue and end up with a good result. At the moment it's looking good, we have a plan and are now in the process of verifying that it doesn't cause problems further down the road. Keep your fingers crossed!
Angela Gaida
in progress
Currently we are working on the concept of this, which is more complex than it appears at first glance. But we are confident that we can make it work and will keep you updated here on the progress.
Angela Gaida
under review
I really would love to give you all an update that tells you an ETA for this, but I can't at this point in time.
Nevertheless, I'm putting this issue on "under review" status. As a first step we need to look at what consequences a setting "only these people can see this field" will have, because it affects of course every single place in Linchpin that shows or uses profile data - and that's a lot. The whole architecture wasn't originally set up in a way that reflects a setting like this, so we'll have to dive deep into the code to decide how to best tackle this and make it future proof.
D
David
Please implement the function that Linchpin Profiles uses restrictions for profile fields.
We really need that for our extranet scenarios!
Right now every extranet user can see what profile fields we use.
P
Peter Scheidt
Hi there,
is there any news on a possible ETA for this? This is a must-have requirement for any extranet setting if you want to use profiles for more than your phone number ;-)
Regards
Peter
Angela Gaida
Peter Scheidt: Not yet, Peter Scheidt. While we certainly can see the importance (not only) for extranet settings, it's nothing that's done by just adding a checkbox. On the contrary, it's a rather complex thing with a lot of dependencies and risks for unwanted side effects, which is why we haven't tackled it yet.
It's on the shortlist for "soon to do", but I cannot promise anything more specific at this point in time.
Angela Gaida
Merged in a post:
User profile field-level permissions for viewing/editing
P
Paul Stahlke
We use the Linchpin API to update some user profile data. It would be nice to prevent users from updating these fields. Plus there are other more sensitive fields that should only be displayed to certain users/groups that we would like to control view and edit access on.
Nastja Kozlova
Another case: emergency contact (person to call if something happens to an employee), which is visible only to a person and hr team. It would be great to have an opportunity to add these fields as required in onboarding assistant.
We found a workaround: you can add such fields as hidden and give a permission to edit the profile to certain category of users (hr team in our case). You can't add them to onboarding assistant (fields become uneditable when hidden), but if they are marked as required, they are shown in profile assistant pop-up. But it would be nice to have a straight solution :)
Load More
→