A Bad Assumption

I just felt a lot of shame due to a bad assumption.

If you're familiar with the Salesforce sharing model, when an object is set as private, you know that if you own an object, you can see it.  If not, you can't.  (Unless something else implicitly grants access like a hierarchy or sharing rule).  

That works great.  EXCEPT FOR ACTIVITIES!

Private activities don't really mean private.  It means "If I can see the object an activity is attached to, I can see the activities, no matter who made them".

I made an assumption that activities worked as they work with other object, and obviously, I was wrong.

So, a few lessons to learn (and share) from this:

1. If something is a pivitol part of a project, MAKE SURE it works the way you think it should.
2. You'll never know everything about Salesforce, it's too big.
3. Always have a plan B.  In my case, Plan B is more work but we'll still meet our client's needs.

And, if you're feeling generous, please vote up this idea to make it work the way it should:

https://sites.secure.force.com/success/ideaView?id=08730000000BrSoAAK

Have you made a bad assumption before? Would love to hear about it! - Garry

Comments

[Steve]

Another thing to look out for is the "Grant Access Using Hierarchies" checkbox. You can update this sharing setting for custom objects and it can mean the difference between private... and not so private.