Every business portal needs the same plumbing: logins, passwords, permissions, menus, a design, an administration area. It is dull, it is essential, and building it from scratch eats a large share of any software budget. DNN arrives with all of it finished. That is why it makes such a good foundation for portals, and why your budget goes into what your business does instead of into another login screen.
What a portal is
A portal is a website that knows who you are. A customer logs in and sees their own orders. An employee logs in and sees the company handbook and their own schedule. A member logs in and sees what their membership level allows. The public sees the marketing pages and nothing else. See how a web portal can improve your business.
What DNN gives you before any code is written
| Included in DNN | What it saves you building |
|---|---|
| User accounts, registration and password reset | The whole login system |
| Roles and permissions on every page and module | Who-can-see-what rules |
| Pages and menus | Site navigation |
| Themes | A consistent, phone-friendly design |
| A content editor | A way for staff to change wording without a developer |
| File management | Document and image storage with permissions |
| A scheduler | Jobs that run on their own, such as nightly imports or reminder emails |
| Logging | A record of logins, errors and changes |
| Languages | Translation of the site into other languages |
| Several sites from one installation | Separate portals for different brands or divisions |
It is not uncommon for 80% of a planned custom web application to disappear when it is looked at again in the context of DNN. What remains is the 20% that is particular to your business, and that is where the money should go.
How DNN is put together
In plain terms, DNN has three layers. At the bottom is a SQL Server database that holds the content, the users and your business data. In the middle is the DNN framework, written in Microsoft ASP.NET, which handles security, pages and everything in the table above. On top are the modules, which are the parts people see and use.
A custom module plugs into the middle layer. It does not have to check who is logged in or what they are allowed to do, because DNN has already done that. It only has to do its own job. Modules can also offer and use web services, which is how a portal exchanges data with accounting, a CRM or a mobile app.
Signing in
DNN has its own user accounts, which suits customers and members. For staff, it can be set up to accept the Windows accounts they already use through Active Directory, so there is no second password to forget. One portal can do both: employees sign in with their work accounts and customers with the accounts they registered.
Portals we have built on DNN
- A product portal for National Geographic School Publishing, managing more than 16,000 education products through more than 70 custom modules, integrated with accounting and sales support systems.
- A patient program system for Dartmouth-Hitchcock Medical Center, tracking bariatric patients, treatments, appointments and doctors.
- An online permitting system for P. Wolfe Consultants, where clients enter project details and the system completes New York City’s building permit forms.
- An operations system for R.O.D.S. Trucking, covering trucks, drivers, materials, deliveries and projects.
- Websites for the SLR group of finance companies, with custom modules for their reporting to shareholders.
- A content approval process for Trailmark Bank, so that page changes are reviewed before they are published.
When DNN is the right foundation, and when it is not
A good fit when the system is part website and part application, when different groups of users need different access, when staff need to edit content themselves, and when your company runs on Microsoft technology.
Not the best fit when there is no content to manage and the system is pure application, when it has to serve very heavy transaction volumes, or when it must run on something other than Windows. In those cases a custom ASP.NET Core web application is the better tool, and we build those too.
How we approach a portal project
- We listen. You describe who needs to log in and what they need to do.
- We analyze. Our no-risk business analysis produces a written requirements document before you commit to anything.
- We sort the requirements into three piles: what DNN already does, what a purchased module does, and what needs custom code.
- We build the custom part and configure the rest. See custom DNN module development.
- We train your staff and stay available.
Keene Systems has built custom business software since 1987, worked in ASP.NET since 2002 and in DNN since 2004. See our DotNetNuke development services, or book a 20-minute call to talk through your portal.
Frequently asked questions
What is a DNN portal?
In DNN, a portal is a website with its own pages, users and design. One DNN installation can run several. The word is also used for any site where people log in to see their own information.
Can DNN use Active Directory logins?
Yes. DNN can be set up so staff sign in with their Windows accounts, alongside ordinary registered users.
Can a DNN portal connect to our other systems?
Yes. Custom modules can exchange data with accounting, CRM and other systems through web services or directly with their databases.
Is DNN only a content management system?
No. It is also a foundation for custom business applications, which is how many of our DNN projects use it.

