Hi Rob,

I can understand where you might feel that the licensing links should not be visible to end users so let me explain our position, too.

The Enterprise License is a license for as many DNN installations that you directly own and operate.  For example, a business entity that might have multiple DNN installations will use the Enterprise License.

If you want to install the modules for clients that you're implementing solutions for, then the Developer License would be the right option for you. Please see the license comparison chart to see the difference.

Even with the Developer License, we need to obtain specific information from the installation itself.  This ultimately protects the end user because down the line, if the developer, for any reason, is no longer involved with them, we can trace the license back and know that they have a legitimate install.  If they need direct support (and not through the developer), they may have to obtain their own license at that point. We see this all the time where the developer sets up the site but the client ends up managing/upgrading on their own as they develop their own expertise.  On the other hand, if you're the one installing at their site, you'll be the one filling out the licensing form anyway.

I realize that this may not be the ideal for every situation.  We will continue to consider licensing options in the constant balancing act, juggling client protection, ease of use, and controlling abuse.  Thanks for sharing your opinion and your understanding.

Candace

Hi... Yes in the future I can see that licensing might be setup at the host level, however other links are used by many of our customers that use the product so not sure about those (examples of help in setting things up, the user guide, links to the forums, etc...). I realize these might not be appropriate for your specific situation and we might review later adding some host options which allow you to turn on/off certain features but this would mostly be for security... Dynamic Forms/Reg are very powerful and there are many areas where there is direct SQL access so there are other risks involved with having that many sites on a host if they have direct access to the administration interfaces. So maybe if we add some host options to disable SQL Options, SQL Binding, SQL Events and so forth which are a security risk for these types of setups then we can also add some options for 'Do not display user guide links' etc...

Thanks,

Chad

Thanks for the reply Chad,
 

Yes I agree, the SQL bits are also undesirable at anything below host level and I already hide these from Admins and below via additional code in the ASCX.
 

I don't mind if unsuitable links and content are present in a module so long as there is a way I can drop them from the interface, even if its through the ASCX files. The troublesome area is anything placed in the action menu where it's difficult, or even impossible to alter.

 
Ultiimately, I am the customer of Datasprings, and my customers are not. As such, I feel that my needs are relevant here and hence why I'm providing the feedback here. Thanks for anything you can do to improve this later on down the road.
 
 

@Candace
Thanks for the explanation of the licensing as well. I read the differences carefully before upgrading and my business is covered by an Enterprise license because I own and manage all websites on my server. They have different domains, but I offer websites only as SAAS (Software as a service). 

This is much like having your email on Gmail.. you use it to send email, but you don't own or have rights to any part of Gmail.
 
I am the sole purchaser and owner of all components and licenses and I am the only person who installs modules and only I should be supported by my suppliers (i.e. Datasprings). No one else has any rights to any part of the installation. My customers only have the ability to use the websites - not build them, not add modules, nor take anything away. They are buying my service, not buying products. I have 3 DNN instances on one web server and I have two contracted employees at Admin-level. The other two instances are not yet activated, but will be eventually.  My two admins are unaware of the underlying systems they use and that is a strict requirement for building and maintaining the service.
 
I understand that I would need a developer license if either my staff or my customers were directly installing or using the modules outside of my business, but this is not the case. The modules are installed, operated and managed solely by me and my admins.
   
I may have several dozen websites on my system, but seriously, all of this drama and cost is for a mere half dozen forms in actual live use. I am also testing one instance of Dynamic Registration with Dynamic User Directory today and obtaining the latest version of User Directory was also part of the motivation for upgrading the license.
 
Sorry for the lengthy reply, but I need to clarify my business so that we're not working at odds here. 
 
Thanks again
Rob