From mails here it seems that it is more efficient to limit "Repository Access" than "Folder Access".
But limiting "Repository Access" is a very bad feature to administrate compared to "Folder Access", because it does not use the user groups.
Adding people to groups and then setting permissions for groups is much simpler than clicking of individual users on many repositories. Also it is very difficult to see what repositories a certain user has access to, whereas it is very simple to see which groups the user is member of.
Furthermore, it would be natural to be able to give "read-only" access to a repository.
If it wasn't for the performance issue then it would seem most natural to drop the "Repository Access" feature completely. Since "Repository Access" corresponds to setting access on "$" in that repository.
So I would suggest that you drop the "Repository Access" feature, and make sure that setting access only on "$" works efficient.
I would guess that in more than 99% cases access is only set on "$" and then next level.
User administration
Moderator: SourceGear
-
- Posts: 153
- Joined: Tue Jan 20, 2004 2:28 am
- Location: PDC, Copenhagen Denmark
- Contact:
User administration
Thomas Linder Puls
Visual Prolog www.visual-prolog.com
Visual Prolog www.visual-prolog.com
The ability to limit repository access was implemented because we had many requests from users who wanted to hide repositories from certain Vault users.
We've also had requests to be able to limit repository access by group. I'll add your comments to those feature requests.
We've also had requests to be able to limit repository access by group. I'll add your comments to those feature requests.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 153
- Joined: Tue Jan 20, 2004 2:28 am
- Location: PDC, Copenhagen Denmark
- Contact: