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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositoryRepository for user groupsRepository for user groups
Previous
 
Next
New Post
5/6/2006 3:05 PM
 
I'm trying to decide how best to setup a "company page" for different clients that would have their own unique downloadable content based upon who is logged in.  I'd like to tie groups of users to a company.  These users would have access to their company repository and no other.  I know I can create a role and call it a "company", and then assign users to that role.  I know I can then create a page or pages with a repository that is viewable to only users in that role.  Is there a better way?  That's a lot of work.  Ideally, I'd like to set a repository module (or something like it) on a given page such that the module "knows" who is logged in and what role (or company) they belong to and dynamically presents that companies repository information and no other.

Another problem I see in going down this road using "roles" as a company identifier is perhaps creating too many roles within the system -- I've heard of performance issues in doing this.  Also, seems like the management of these roles would be painful.

Any ideas or suggestions?  Thanks.

http://www.idsconsulting.com Ideas, Design, Success.
 
New Post
5/19/2006 12:34 PM
 
I'm surprised, 2 weeks and not a single response.  Bummer...

http://www.idsconsulting.com Ideas, Design, Success.
 
New Post
5/19/2006 2:27 PM
 

The problem is that the current version of the Repository allows you to define roles at the overall repository level. What you need is the ability to assign roles to categories.

I have a similar requirement on my own site. What I did was create a separate page for each client and set the page permissions so each client could only see their own page. I then placed a repository module on each page. So each client has their own repository. I set each repository to allow uploads for that particular client and set the moderator to Administrator only so I would get an email whenever a client uploaded a file.

Not a perfect solution and possibly unworkable if you have a large number of clients.

In a future release you will be able to assign roles to categories which would allow you to do what you want within a single repository module. Sorry there's no better solution for you right now.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositoryRepository for user groupsRepository for user groups


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