Could you explain how you suggest your product would be used in terms of permissions for the sites that are created? We're looking for a solution that allows us to create multiple project sites, where the people requesting the site creation would not have the ability to create sub-sites in any way. We would however want them to retain full control of all other aspects of the site, such as permissioning, creating of Lists, Libraries etc.
How would the permission structure of MOSS work in conjunction with your product to achieve this?
Here is the most common approach for this type of configuration.
When this provisioning profile is used to create sub-sites users will have a modified permission level that does not contain the 'Create Subsites' permission.
Thanks for that, this is what I thought would be the intended approach.
However, if the user then has permission to change permissions, can they not assign themselves Full Control at a later stage and therefore give themselves the ability to create Sub-Sites again?
In this case, would the only solution to also be to remove their permission to change Site Permissions?
Also, am I correct in assuming that it would be possible to create some sort of workflow to make the requester the Site Owner?