Hi

I generally put site administration settings in a new section so the access rights can be controlled by the user settings page.

I would put things only developers have access to in the settings or developers section.

Settings section: I would class these as things that need to be configured

Developers section: These are things that are not configured but created and worked with online.

A good example may be in settings i would put email addresses but within developer i would hold the template for the email.

Hope that helps. Anything else ask away

It might be easier to offer advice if you gave some idea of what your package is going to do.

Rich

Thanks for the input guys. I'm not developing any specific package at the moment but will be making a few so just need to know what the best practices are.

I also found this series of videos on umbraco.tv 

http://umbraco.tv/help-and-support/video-tutorials/developing-with-umbraco/custom-sections,trees-and-pages

that are really useful.

Creating a new section specifically for administration tasks does seem like the most sensible thing to do so I can manage the access rights. I'm interested to know whether this is an approach everyone is taking or whether a large proportion of implementations assume that site administrators and developers are one and the same?

We work with many clients and therefore developer and content admin are never the same so we would always put content admin in a new section.

Hope that helps

Remember to mark the correct answer as the answer.

is working on a reply...