Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN Experts - Kindly advise - Feature Questions...DNN Experts - Kindly advise - Feature Questions...
Previous
 
Next
New Post
5/18/2006 5:37 PM
 
Murali Rajendran

Joined: 5/17/2006
Posts: 2

Hello,
Since I am a n00b here, I request the respected experts to kindly guide me and clarify my questions... 

I am building an online (hosted) application that will be used by many companies, hopefully .  I am looking towards DNN to jumpstart my online web app, although my app is NOT a 'Portal' where many people can register, and post news, etc.. etc.. 

Some of the features that I am looking for are:

1) I need to support many Companies with one installation of DotNetNuke.  I am hoping to create ONE Portal for EVERY company who signs up for my service. Is this approach the correct one?

2) Every Company will have an 'admin' who can then 'create' and 'maintain' many 'users' for his Company. Can I (the Super User, or host) create 'admins' for every Company in my app... and allow these 'admins' to maintain their own RESPECTIVE Company users?

3) Can I RESTRICT the Admin for a particular Company (portal) to ONLY create/maintain users (for that Company alone)? I dont want to give access to the Admin to modify 'Page Functions', 'Add/Remove Module', 'Common Tasks', etc.

4) A particular Company's data should not be visible to any other Company.  In fact, I dont want Company A to know that even Company B subscribes to my online application.

5) Can I develop a module and share it among different Companies, who are on different Portals?  The data contained in this Module needs to be shared as well.  For e.g. If I maintain a list of 'preferred' service providers, ALL Companies (portals) in my app should be able to view these providers and be able to 'rate' them and write comments about these providers.

6) Can I disable/remove certain core Portal modules, like News Feeds, Discussions, etc?

7) Can I have a COMMON login page for ALL my Companies (portals)? For example, I will have a login applet in http://www.CoolWebApp.com.  Now, when users of Company A login, they will be automatically redirected to Company A's Portal.  When users of CompanyB login, they will be automatically redirected to Company B's Portal.  
That way, Company A users DONT have to remember that thir subscription is at http://CompanyA.CoolWebApp.com, and Company B users DONT have to remember the URL http://CompanyB.CoolWebApp.com

This post is kinda long, but I pray that some kind soul shed some light...

Thanks in advance
-GFI
 
New Post
5/18/2006 7:19 PM
 
Erik van Ballegoij


Erik van Ballegoij's Avatar

erikvanballegoij.com
Joined: 4/7/2004
Posts: 4445
gfi wrote

1) I need to support many Companies with one installation of DotNetNuke.  I am hoping to create ONE Portal for EVERY company who signs up for my service. Is this approach the correct one?

Yes.

gfi wrote

2) Every Company will have an 'admin' who can then 'create' and 'maintain' many 'users' for his Company. Can I (the Super User, or host) create 'admins' for every Company in my app... and allow these 'admins' to maintain their own RESPECTIVE Company users?

Yes

gfi wrote

3) Can I RESTRICT the Admin for a particular Company (portal) to ONLY create/maintain users (for that Company alone)? I dont want to give access to the Admin to modify 'Page Functions', 'Add/Remove Module', 'Common Tasks', etc.

No. Admins always have admin rights in a portal. If you want to restrict access, you have to create a non admin user, and give that user access rights to the user accounts module. For that you will have to create a new module that is a verbose copy of the user accounts module, and put that module on a different page. Then you give edit rights to that page/module for your "admin" role

gfi wrote

4) A particular Company's data should not be visible to any other Company.  In fact, I dont want Company A to know that even Company B subscribes to my online application.

yes: all data is partitioned on portal level, no portal can access data from another portal (this is at least true for core modules, third party modules might have (in a very rare occasion) other behaviour

gfi wrote

5) Can I develop a module and share it among different Companies, who are on different Portals?  The data contained in this Module needs to be shared as well.  For e.g. If I maintain a list of 'preferred' service providers, ALL Companies (portals) in my app should be able to view these providers and be able to 'rate' them and write comments about these providers.

Yes. Not withstanding my previous answer, you could create a module that does not use the portal id to partition the data. That way you can use the data accross multiple portals

gfi wrote

6) Can I disable/remove certain core Portal modules, like News Feeds, Discussions, etc?

Yes, you can make modules premium (from the module definitions page), and then select which portals should be able to use whch module

gfi wrote

7) Can I have a COMMON login page for ALL my Companies (portals)? For example, I will have a login applet in http://www.CoolWebApp.com.  Now, when users of Company A login, they will be automatically redirected to Company A's Portal.  When users of CompanyB login, they will be automatically redirected to Company B's Portal.  
That way, Company A users DONT have to remember that thir subscription is at http://CompanyA.CoolWebApp.com, and Company B users DONT have to remember the URL http://CompanyB.CoolWebApp.com

No, at least not with the dnn core application. You might want to look into the UCanUse portal mapper though, which allows you to share users across multiple portals. I don't know if that module can take care of the redirection, but that's something you can ask the developers

Cheers,

Erik

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn
 
New Post
5/18/2006 10:51 PM
 
Murali Rajendran

Joined: 5/17/2006
Posts: 2

Thank you very much Erik,

I really appreciate the answers and it bolsters my decision to choose DNN over anything else...

Of course, I will have some other doubts, but I will post those to the forum, if I dont see a clarification of it by searching..

Thankx

-GFI
 
New Post
12/12/2008 5:34 PM
 
LarrySM

Joined: 11/16/2008
Posts: 3

Hi, I am reviving this thread because I have similar questions, and since this answer was from a few years ago, I was wondering if any answers have changed.

Regarding Previous Question

3) Is copying the user account module and restricting access to the page it sits on, still the best way to restrict admin access?

7) Is a common login page possible now? what non-core modules help in directing users to different portals.

I also have New related questions:

New 1) Is there a maximum limit of portals? similar to the original posted question, I wish to make a website where 1000's of companies will have a portal. When there are that many portals - does anything break/slow down? is this a bad idea? should i have a different structure? (or different CMS?)

New 2) Is there a module that allows a user who has access to several portals , to create a "Dashboard" page that pulls in data from all the different portals? It would be very important that this data is only permissioned to that one user, thus it shouldn't "break" the partition between portals for any other users. Example of data to be displayed on the Dashboard would be a) all events from all portal event calendars that a user has access to, b) recent changes on the portals...etc. From the Dashboard the user would then be able to click the event link and be taken "inside" the individual portal.

New 3) Generally speaking, I'd like to emulate the functionality of huddle.net using DNN. Huddle has a "workspace" concept, which in my case would just be "Company". Thus any user can access several "workspaces"( companies) if given permission, but the workspaces are kept private from one another. Is DNN up to this task? any red flags that I should be aware of? Should I investigate other CMSs?

 

thanks to all who respond,

Larry

 

Note: I will probably be looking to hire a DNN guru to help me buy the best modules, and develop the site. Feel free to contact me.

 

 
 
New Post
12/13/2008 3:47 AM
 
Sebastian Leupold


Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

www.dnnwerk.de
Joined: 3/8/2004
Posts: 46212

Larry,

3) still applies to current DNN version, upcoming DNN 5.0 will overcome this limitation: admin modules are like ordinary modules now and admins/hosts may individually grant permission to other roles.

7) this will require a custom login or authentication provider, 3rd party modules like from UCanUse may also contain this option.

New 1) Users reported, that they did run 1000's of portals in a single DNN installation, but you might need to create your own portal management tool, since a simple list with 1000's of entries becomes unhandy

New 2) There are generic modules from 3rd parties to access SQL data sources, which might provide you with this option, otherwise you will need to create a custom one.

New 3) DNN will be able to suit your situation, but require some customization, since this is not the default use case. I am not aware of a different Web Application Plattform, which already provides this option out of the box.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN Experts - Kindly advise - Feature Questions...DNN Experts - Kindly advise - Feature Questions...


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out