Products

Solutions

Resources

Partners

Community

Blog

About

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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Making module invisibleMaking module invisible
Previous
 
Next
New Post
12/26/2006 11:46 AM
 
Excerpt from my post above:

If you have not placed users in these groups it is not too late.  Create the employee group and make it public and auto.  This will place every user into the group.  Optionally you can skip this step and just use the Registered Users group for this purpose.  Next create the Manager security role and do not make it public or auto.  You then will manually assign users into this group.


After creating these groups they will be available for assigning security permissions.
 
New Post
12/27/2006 3:06 AM
 

I don't think I understand your solution.
The security-part is clear. How to link a security role to a module is not clear.

For now I make 2 seperate pages.

Thanks for your replies.

 
New Post
12/27/2006 5:19 AM
 

Elwin,

You can make each module visible or invisible on a page.  Just go to the Module-->Settings.  Then uncheck the "Inherit view settings from page" check box.  You can then make the module viewable or not for any group.  For example, I show a log-in module on the home page for unauthenticated users but once they log-in, it disappears.   It works like a charm.

Bill

Elwin wrote

I don't think I understand your solution.
The security-part is clear. How to link a security role to a module is not clear.

For now I make 2 seperate pages.

Thanks for your replies.

 
New Post
12/27/2006 9:06 AM
 
If you understand how to assign security roles to a page, you should have no problem doing it with a module - it is the same thing.  For example, if you are using the Text/HTML module, in the menu for the module itself there will be many options...the first one is "Edit Text"....further down the list is "Settings" right after "Print".

You should now see the Module Settings.  Near the top is "Permissions".  By default the module will have the same permissions as the page. De-select the option to "Inherit View permissions from Page".  You should now be able to apply your custom security at the module level.
 
New Post
12/28/2006 3:05 AM
 

Thanks for your answers.

It is not what I am searching for. Assigning security roles to pages and modules are clear to me.
I will try to explain my needs.

I have a homepage with general information about the company. Registering is disabled.
All persons have a loginname and a password to login. In a relation table a field is used to mark the person as employee or manager. Managers and employees are registered users when they log in.

When a manager logs in, a link-module must appear with extended possibilities for manager.
When an employee logs in, an other link-module must appear with the extended possibilities for employees.
The link-module for managers is invisible now.

I hope the above makes everything clear.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Making module invisibleMaking module invisible


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