From a systems management perspective I prefer the instance rights approach. Unless there is an insane amount of resoruce changes in an organization, then there is only a small amount of adminsitration. One thing a lot of organizations forget about Clarity is that it is an Enterprise Class tool. As with all Enterprise Class Applications, there is administration involved. Just like in SAP, People Soft, Oracle E-business Suite, and other enterprise class apps. A good operational procedure guide should provide the check list for what the Clarity Administrator needs to do when preforming any move/add/change to a resource. Also, the sucess of this is dependant upon the Clarity Administrator knowing about any move/add/changes. So it is very important that Clarity is tied into HR so that they are informed of the changes. Think about it this way. Any time a there is a Move/Add/Change, HR has to know about it and there generally is a formal mechanism for a manager to notify HR. This notification often also informs teh applications group, desktop support gorup, and other groups to make sure the resource has a phone, email, desktop, office and other requriements. Why not get onto the same form/request so that the Clarity administartor is also notified so that they can also perform the necessary actions to get someone on/off/moved in Clarity.