search

rosedu / wouso

World of USO - the Official Repository
http://wouso.rosedu.org
Other
122 stars 103 forks source link

Document what goes in the Control Panel and what goes into the Django Admin interface #460

Open razvand opened 10 years ago

razvand commented 10 years ago

It's not clear to me what should be done in the Django Admin interface and what should be done in the Control Panel interface.

It would help to have a wiki page documenting all possible actions that are doable in the Control Panel interface (depending on the role) and what action need to be done in the Django Admin interface.

alexef commented 10 years ago

From my pov, everything should be available in the Control Panel. Django Admin is being kept just to cover use cases not implemented yet in the control panel. Django Admin is dangerous since it allows low level access to models and data.

razvand commented 10 years ago

I agree to have everything available in Control Panel. Provided we do that, could Django Admin be disabled, just to prevent anyone from tempering with low-level data? Or should we keep it "just in case", but with very few people able to access it?

alexef commented 10 years ago

Yup, that are the is_superuser and is_staff flags on the User model. Only a few users should be able to access Django Admin.

Notice that Staff member is not the same with is_staff.

razvand commented 10 years ago

There should be a consistent naming scheme for default roles, methods and flags. I'll come up with a proposal on the mailing list.