Struggles
Bernard,
I've asked several questions that may seem odd. Hopefully this post will clear up any misconceptions and I'll be able to see whether YACS can work for me.
Let's say that I own BigCompany.com with offices in Toledo, Miami, Paris, London, and LA.
Let's say that I want to set up a public intranet of sorts for my employees that is read only - they can't edit the content. What I mean by public is that it will be out on the web but access will be controlled by passwords and logins.
Further let's say that on this employee only site we have news, articles, checklists, etc. However I only want employees from Miami to be able to see the Miami related information and the same for the others.
I can see setting this up in 2 ways - either one big site or multiple separate sites.
[b]One big site.[/b]
The problems with this setup are:
1. I can't have forums that are separate for each location. I would not want the Toledo employees using or seeing the Paris forum.
2. I can't have separate newsletters. Again employees from Miami should only get the news about Miami.
3. I can't control sections/categories by location. If I have checklists for the LA employees that don't apply to the London employees I would want it separate. However if an LA employee is logged in he would be able to see the London sections/categories too.
4. I know that we could approve every sign up. But if a bunch of non-employees came in and signed up it would create a hassle trying to determine and approve everyone. This could partially be resolved by being able to hide the register link but apparently that isn't possible.
5. Also problem #2 below applies.
[b]Multiple sites.[/b]
The main problems with this scenario are:
1. Because of the distributed authentication scheme YACS would automatically let employees from Paris login to the Miami separate installation.
2. Further if a regular non-employee -- let's say one of YOUR members wants to login to my private employee site they can. This is even worse than problem #1.
Any thoughts or ideas on how to accomplish this type of setup? Thanks!
I've asked several questions that may seem odd. Hopefully this post will clear up any misconceptions and I'll be able to see whether YACS can work for me.
Let's say that I own BigCompany.com with offices in Toledo, Miami, Paris, London, and LA.
Let's say that I want to set up a public intranet of sorts for my employees that is read only - they can't edit the content. What I mean by public is that it will be out on the web but access will be controlled by passwords and logins.
Further let's say that on this employee only site we have news, articles, checklists, etc. However I only want employees from Miami to be able to see the Miami related information and the same for the others.
I can see setting this up in 2 ways - either one big site or multiple separate sites.
[b]One big site.[/b]
The problems with this setup are:
1. I can't have forums that are separate for each location. I would not want the Toledo employees using or seeing the Paris forum.
2. I can't have separate newsletters. Again employees from Miami should only get the news about Miami.
3. I can't control sections/categories by location. If I have checklists for the LA employees that don't apply to the London employees I would want it separate. However if an LA employee is logged in he would be able to see the London sections/categories too.
4. I know that we could approve every sign up. But if a bunch of non-employees came in and signed up it would create a hassle trying to determine and approve everyone. This could partially be resolved by being able to hide the register link but apparently that isn't possible.
5. Also problem #2 below applies.
[b]Multiple sites.[/b]
The main problems with this scenario are:
1. Because of the distributed authentication scheme YACS would automatically let employees from Paris login to the Miami separate installation.
2. Further if a regular non-employee -- let's say one of YOUR members wants to login to my private employee site they can. This is even worse than problem #1.
Any thoughts or ideas on how to accomplish this type of setup? Thanks!