|
Wednesday 22 September 2010 1:31:10 pm
You could create a user_profile class, and give each user permissions to create content objects of type cv / project /etc only in a user_profile of which they are the owners. Then you need to either let the users create their own user_profile when they log on, or set up a workflow that creates it for them as soon as they register. You might also want to set up a workflow to check that a user does not create two user profiles. Technically, you could use the user object as profile page, but by default users are stored in a separate content tree, and this imposes some restrictions - but you can set up site.ini so that new users are in fact created in the main content tree. Take care about that: having user object world readable might have security implications...
Principal Consultant International Business
Member of the Community Project Board
|