> The  problem is then that I want some users to be able to create new accounts,
> but only see or edit accounts that they themselves have created.

If you're trying to do it through the admin app, you'll probably not
be able to pull if off since the admin doesn't have row-level
permissions.

Are you looking at using the Users model from the auth app? If so, I'd
suggest looking at the Groups app with it. I'd probably create a
special page (login_required) that would allow that parent user to add/
edit/delete users in their own group. This would keep "bar"'s accounts
from modify "foo"'s. This would also let you get an even finger-
grained control and only let users edit accounts they have created.

The execution might be a little tricky; you'll probably need to use a
user profile model to attach the extra metadata to a user w/o
modifying Django's contrib auth app. (Editing core is the path to
darkness for me) This way you could assign the necessary extra data to
a user - what user created them, if it is a "parent" account, etc. It
won't be hard, but the devil is in the details of setting up the user
profile models. James Bennett has done some great work in this area
that you might want to check out. (look at b-list.org)

This may not be the best approach, but it's the first to come to mind.
I hope this helps.

Scott


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to