SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What should be the provisioning model for supporting only 2010 and above, if:

  • it needs to include custom SharePoint security groups
  • it would be deployed to multiple unrelated SharePoint installations

I have a feeling only site definition would support these, but could more experienced please comment?

share|improve this question

I might be misunderstanding the question but if you only need to provision security groups why not just use a feature which makes the appropriate modifications?

You may need to think how you decide what the custom security groups would be called. Unless they are always the same. One option could be defining feature properties.

share|improve this answer
Are there custom master pages withbdesign being implemented as well? – Simon Doy Feb 6 '13 at 19:56
My bad, I did not include the details. These groups are needed along with other custom artifacts that would be bundled as a site-template/site-definition/something... – Floyd Pink Feb 6 '13 at 19:59
thanks - ok some more questions. will you have multiple sites created in site collection? do you expect people will use your solution in its own site collection? or mix with other types of sites. just thinking if you will have control at site collection level. – Simon Doy Feb 6 '13 at 20:05
Most probably it would be only one instance in a particular site collection, but need not necessarily have to be at the site collection scope. – Floyd Pink Feb 6 '13 at 20:08

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.