Contact Information

Chris Toohey

    Publishings
    Remove my name from the Domino Directory!! 02/05/2008
    Lotus Notes
    Quick and Dirty Mail Application Document Importing 01/24/2008
    Methods and Strategies
    Addressing Domino Web-based @DBLookup limitations with Rich-Text and Context Profiles 12/16/2007
    Domino Web Development
    Dynarch Calendar - Date Blockers 01/25/2007
    Integrated Solutions
    Domino Flex Fields 11/03/2006
    Methods and Strategies
    Site Resources

    RSS Site Content
    Syndicate This Site!
    DG Banner Logo
    Advertisements

    IBM Lotus Notes and Domino 7 now available

    Remove my name from the Domino Directory!!

    02/05/2008 04:55:17 PM | Chris Toohey | Saylorsburg, PA

    Quick little tip here - and I forget where I picked this up - but it's proven very useful. Let's say that you don't want, for whatever reason, your name to show up in the To/CC/BCC type-ahead save for a select few individuals. Say you have Directory Assistance-based secondary nab and you don't want people to hit a particular address - whichever the case. Here's a pretty slick way to do it with no design changes to the target address book!

    We'll start by adding a a User Role to the application ACL called isAdmin. Once this is added, I'd recommend giving this role to LocalDomainAdmins, LocalDomainServers, etc. immediately!

    Restricting Read-Access to a specific group

    Then simply highlight - from the People view - the document you wish to modify, and go to the Security (4th) tab on the Document Properties. Once there, simply modify the "Who can read this document" to explicitly define your isAdmin user role.

    Now, if I try to use type-ahead to lookup (for example) my wife:

    Directory Search for Shirley = No Results

    You can also search the directory and the document won't be returned... unless you have the isAdmin role, that is!


    Comments

    Tim Tripcony
    http://www.timtripcony.com
    02/05/2008 06:02:25 PM

    That's a popular request for groups as well... say, for example, end users can't send email to "All Employees" unless they're in a group that has the role that can see that mailing list.


    Paul Inglis
    3/19/2008 1:04:11 AM
    Good tip! I was asked to "unclutter" Groups in our NAB a few months ago, as we have several hundred groups, so I used a similar approach (with Roles) so the employees only could see (and send to) groups that they needed to use. However, I agree that it's also useful for restricting access to "All Employees" style groups. Nothing worse than some clueless person sending a timewasting mail to several thousand employees.

    David Killingsworth
    http://domino.symetrikdesign.com
    4/9/2008 2:44:55 AM
    We use this for restricting the use of our ALL-ALL-ALL group only to upper management and HR. However, now that we are piloting Sametime 8.0 connect client, I can add ALL-ALL-ALL group to my sametime buddy list and send an announcement if I want. How can we limit this group in Sametime??

    Paul Harrison
    www.dominkow.co.uk
    4/15/2008 3:44:12 PM
    Great tip, I didn't realise that you could apply this technique to Person Documents as well as groups!

    @David, re limiting hidden groups in Sametime, this may help => http://domiknow.co.uk/2007/11/22/sntt-preventing-sametime-users-from-accessing-hidden-groups/


    Add a New Comment


    (Not Published/Public)
    Remember my Information!

    (Enter the text from the image to proceed)

    (Full markup allowed in the comment field below; play nice!)

    Live Comments Preview