nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Restricting 'people find'

kvaes

Is it possible to restrict "regular" users from finding other people?

Practical Example/Scenario
-> One Share Instance
—> Site A for Customer A
——-> Contact 1 from Customer A
——-> Contact 2 from Customer A
——-> …
—> Site B for Customer B
——-> Contact 1 from Customer B
——-> Contact 2 from Customer B
——-> …

Yet we wouldn't like that Customer A is aware of Customer B. So is it possible to restrict the people find that customers don't see eachother. I already found out how I can restrict the site search for this (by settings the folder rights in /alfresco), yet I'm puzzled how I can restrict the people find.

Thanks in advance for your help!

Find more posts tagged with

Comments

kvaes

Any ideas on this? I thought of hacking the jsp code, but I'm not eager to do this as it breaks my upgrade path…

petrush

Hi, did you find any solution to this?

I think this is quite important in a commercial multi-project environment running on a single server.

Regards

petrush

This is a serious issue if alfresco is used for several project, sometimes it is not ok to let a customer be able to search the others that is in the system.

Is there a way to completely disable the "people finder" in share?

Thankful for help

mabayona

Multi Tenant?

Multiple instalations in a single server?

petrush

Multiple instalations in a single server?

Yes that is an option to consider, which probably is the easiest in terms of installation, but becomes more administration - some central user handling is needed, and it would loose the ability to have your personal dashboard with an overview of what is going on in the different projects.

In my view, it should in best worlds be settable on user/group-level as: 1) no possibility to search for users, 2) project-wide possibility and 3) site-wide possibility. If this is difficult, the best would be to be able to remove the people search completely.

yasosaran

we had similar situation, and we did it through organization name. As in our case, all site A users will belong to Org A and site B users will belong to Org B.So now Org A people won't see Org B people.

In the people-finder.get.html file , we got the current users's organization name and checked that against in the people-finder.js file (included another if loop in function PeopleFinder_onReady() after Remove the current user from the list comment). You have to avoid this check for admin.

Thanks,
Yaso

gronfelt

I'm also interested in this.

yasosaran, would you care to post the changes you've made in the code?

movaxbx

Hi Yaso,

I know it's old but i've been searching everywhere for this. There are similar questions everywhere but noone has documented or explained it well. how did you pull the organization name? Did you pull this from the people-finder.sj file? if user.isAdmin exists, then maybe i can find the property method in a documentation where i can check it the way you did..

nwali

yasosaran _ Could you elaborate the changes you made to achieve this?

thanks.