On Tue, Nov 18, 2008 at 08:42, Jain, Rajat <rajat.jain_at_fiserv.com> wrote:
> Hi Team,
>
>
>
> We have recently migrated our project repository from VSS to SVN. But we are
> facing some problem due to access rights.
>
> Actually we want that different combination of rights for different team
> members. Let me make it more clear-
>
>
>
> Suppose in my team we have four members namely A, B, C & D and we want that
> –
>
> · A to have read only access on repository and should not be able to
> update, add or delete any document
>
> · B should be able to read as well as update the existing documents
> but should not be able to add new document or delete any existing document.
>
> · C should be able to read & update existing documents and should
> also be able to add new documents but should not be able to delete existing
> documents.
>
> · D should be able to read, update and delete existing ones and add
> new ones to repository.
>
>
>
> We are trying to put this in place with our IT team working on it. But IT
> team says that this is not at all possible with SVN. They says that you can
> have either access as given to A above or access as given to D above.
> According to them B & C roles as defined above are not feasible. But I
> doubt?
You're both right. The IT group is right that SVN natively only has 3
access levels - non, read-only, and read/write.
You are correct to doubt their position that B&C are not feasible at
all. B & C can be achieved via the svnperms.py pre-commit hook script,
or possibly some creative Apache configuration if that's how you're
serving your repository.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-18 18:10:43 CET