Objects: The HR database is simple. The difference from the diagram "HR_DB" is that the person table has more columns. The original person object of Metaverse is in use. For the workgroups we've created a custom object in MV as shown in the diagram "MV". The original Person object of FIM Portal is in use. For the workgroups we've created a custom object as shown in the diagram "FIM". Sequence: The lifecycle of a workgroup starts in HR. Than it flows to MV and after that to the FIM Portal. In the portal the administrator should add some pointers to the Security Groups associated with this particular WG. The members of the WG are controled by the HR DB. However, to effectively be a member of the WG, and therefore be member of the Security Groups associateds, there must be an appro vation of the WG's manager. If he not approves, then the member must be removed from WG only in FIM, to force another approval workflow until the member is removed from HR DB (PERSON_WG table). "The road so far": The synchronization works perfectly from HR to MV to FIM (with the non reference values). We are creating the workflow for the approval process. Problems: 1 - We are using the attributes ManagerStr and MemberStr in MV because the referenceDN cannot be modified in a C# MA Extension (at least the VS2010 throws a excetpion telling us this). How to use references instead of mere strings? Knowing that the objects to be referenced are not of the same type of the object containing the references. 2 - The membership needs to be approved in a per user basis. So if more than one member is added to the WG's HR in the same operation there must be a distinct approval process to each member. In this case, there is a way to create multiple workflows (one for each member) and control them?