You need to set the ViewAllProjects setting in the web.config file to NO.

Then assign to users security scheme per project. By doing this you are giving your users the ability to view only the projects they are allowed to. You can make a user "read only" if you wish and you can hide private issue and comments.

I am also having issues with this.

I just downloaded and installed Gemini to evaluate it for use in our company but this is a bit of a blocking issue.

After install I have created a project in addition to the sample ACME project. I saw that everyone could see all projects at the login screen so reading the docs I find the ViewAllProjects setting and set it to NO.  This works fine and now at login screen no projects are visible. As admin I still see both when logged in.

Then the problems start :

1) I create a new user and give him No Access security scheme  on ACME and make him project manager on my new project. When he logs in he can still see both projects.

2) I set each projects default scheme to No Access  and  log in and still my user sees both.

3) I create another new user after doing 2, and log this user in and he can still see both.

So how exactly do I make projects visible only to  the correctly permissioned users?

?

Which version of Gemini are you using? This should be and is not the case.

Are you sure that you have saved the web.config file?

I am using Gemini 2.0.4 from your downloads page.

Yes I have saved the web.config file.

As I say , when I go to the gemini site after updating the web.config I no longer see any projects on the login page. That is perfect. 

Once I login though I can see all projects , even those that the user has No Access security role set on.

I would like to use Gemini for both internal and client use, so its important that clients only see the projects they have permissions on and not all projects in the system.

That should not be the case. You should not be able to see ANY project even if you are logged in as admin, unless you have been granted access to that project.

Did you change the actual security schemes?

Ok,

well while we were discussing , i completely removed it, and reinstalled from scratch including rebuilding the db, and went through the same steps again and now it works just fine. I have no idea whatsoever why it was behaving oddly previously. 

All i did before was update the web config, create projects , give them No Access as default , then create a user and he could still see them as could admin. 

I am even using the same web.config as before (as I was too lazy to recopy and paste the licence key and email details)

Thanks for the prompt replies though, I appreciate it and I am happy it all seems fine now. I guess I'll just chalk this up to one of those WTF incidents and forget all about it.

No worries. Glad that all is well now.