Limited Access for Opportunities, Activities and History

[#1]

We need to make Opportunities, Activities and History have Limited Access?  I can make them Private or Public but not Limited.  We are a trade association with competing members.  The association shares a common Database of customers in India with a shared Sales Force.  When a Opportunity is marked Private it excludes the Users in India (our sales force).  If I mark the Contact as Limited Access and separate the competing members into Teams one or the other member is prevented from having access to that Contact.

What I really need to do is mark an Opportunity as Limited and have all Activities and History related to that Opportunity be limited to a particular team.  Any thoughts?

Thanks,

Ken A.

[#2]

Ken

I fully support this idea. This is a problem in many companies I have worked with, especially where sales people are competing with each other and need to keep their activities and opportunities hidden, but they need to be accessible to managers and administrators.

Jeff

[#3]

In ACT! 2010, Opportunities can have limited access.  With this feature available, do you still need Activies and Histories to have Limited Access since they will inherit the access of the object (Contact or Opportunity) with which they are associated?

[#4]

Histories can (and most likely will) include e-mail attachments that need to have limited access.  Therefore the answer would be yes, activities and histories also need limited access. 

This is a major problem for us.  The only solution is to have different databases which is very combursome.  For us it is the opposite problem to what Jeff Granger stated.  Our association members need to keep information confidential  from certain other association members but accessable by all of our salesmen in India.