Q:

How do you set up N2 CMS in an "enterprise" environment?

I've been playing around with the N2 CMS and I've been impressed so far. But it seems like a big jump to move from the examples to an "enterprise" grade solution.
What I really need are robust permissions and roles integrated with Active Directory. So far I've played with the membership and role providers and got things sort of rolling. But I'd really like to compare what I've done with how people are actually using the thing.
How have you customized and deployed N2 CMS in your largish organization?
Update:
This question has sort of become a moot point for us. We decided to use Umbraco instead since a lot of the features that we needed were included out of the box. N2 still seems like a nice system for certain things though.

A:

The N2 role & membership functionality is built to use the Membership & Role Providers from ASP.NET.  So you should just be able to drop in the active directory membership providers & start using them.  See this post for a bit more information & some sample code that may help you out.
Permissions for pages & areas of the site are managed by N2 through the Security screen in the Admin section, and for ContentItems on the AvailableRoles attribute on the Page/PartDefinition attributes.  Permissions for the admin section itself are controlled in the web.config for that folder in your website.
If there's anything more specific that you need to know, you might be better off posting to the N2 discussion list

