I'm not sure this is the way to go about....I would list all requirements first. How do you want the User to interact with the Events, versus how will others view the User's Events (if that is a requirement)...what I would imagine is a Use Case:

- Admin sets the Event Instance to a "User Instance" (means the Event Calendar will capture Events by User)

- User logs in and only see's (and can Edit/Delete) his events.

- Others can log on and select the User's Event Calendar (if it is designated public)

- User can delegate authority to update his Calendar to others (they can edit/delete events on his behalf)

- Other Event/Calendar Instances can incorporate a User's Instance (events) into a Master Calendar. This an Admin-selected option.  In this way, all users for a Department can be added to a Department Calendar.

Anyway you see what I'm getting at...define the functionality/requirements.  Then, the design becomes more obvious.

Tony I apologize for the late answer,I would like to know about your personalized events module, this could help me very much in my project.

Thanks.