Groups and permissions configuration in small team

[gluzm]

Hi all,
we finally convinced many other project stakeholders to use EA. The positive thing is that some of them will actively work with it, which on one side is amazing,  however on the other side we should not allow them to chnage everything.

This whole switch to more formal process requires some access management and restrictions. What I am looking for is some document or advice how to configure groups and permissions, to minimize the risk to lose something.
Our team including all the users together is about 15 people.

Is there any white-paper related to this or what type of groups and permission combinations are you guys using?

Thank you
Jan

[thomaskilian]

Although I'm only working by myself, I think that the best way would be to go through a versioning system. Not only that this has many advantages like tracking of changes and the ability to reconstruct former models in case you went the wrong way. It also allows you to use the build-in access rights. In that way you can read and write permissions as you wish.

I don't know whether the discussion board is already open for EA lite, but your full members could make use of that anyway.

A finer granularity than package level is probably only possible via EA's security mechanism, but I have not much experience with that.

[gluzm]

I’m thinking more about how to cover the whole project cycle. Different people will work on the analysis part, other people on design, and some other on the testing.

Readers will definitely use lite version. The current configuration I was thinking about is using DBMS. To allow distribute changes more effectively thru the team, and we are as well using Perforce for the versioning.

As I am looking at the list of available permission from help file, and trying to understand with what permission combinations to start.
My idea is to start with some small set when almost everybody is able to do everything, but still as I know some people who will be working with the tool, there is a risk, that something could get lost.

Any thoughts, how could the basic set of groups and permissions look like?