InfoShare: How to turn on/off internal and external users? 1

[ukrex]

InfoShare is an instance that we use to collaborate with external partners.

We have turned off searching because externals had too much priv to see things they should not. We would like to turn on searching for internal users, but leave it off for externals. How to accomplish it?

Thank you all who will help in advance.

 

[appnair]

This is a very crude requirement.The beauty of livelink is its search engine and the way the taxonomy can be administered.This really should be attacked at the root.See a good white paper at greggriffiths on enterprise permissions.By default livelink search does not show things to people who are not the acl list
Otherwise if you load customizationRT from OpenText which is a module which maps weblingo files(the html stuff that you see on the enterprise) you can modify and map to your files.If you know the logic to segregate your internal vs external all it may take is a conditional to redirect it to atemplate containing the search box vs none not having it.

The requirement anyways really does not sink in to me.Looks like you have a loose permissions model.It could easily be tackled by Oscript or LAPI.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[ukrex]

Hi appnair,

I like your answer on this question. You pointed on three ways how it is possible to resolve the issue - to revise the permission model (global fix), to use the existed module for mapping the external user's search results (minimum effort, logic to distinguish users exists) or build own module which will restrict external users to use the search engine to defined document hierarchy (more effort, flexible result, logic to distinguish users exists).

Thank you.