EA Repository

[Stirl]

Is it possible to set up permissions in a repository so that different projects in the same repository have different permissions?  IE so a user maybe able to edit some projects and only view other projects in the repository. 

If this is possible can someone point me towards how to do this?

[PeterHeintz]

This is possible!
What you can do, you find here:
http://sparxsystems.com/enterprise_architect_user_guide/12.1/the_model_repository/usersecurity.html

[Stirl]

Thanks for your reply.  I must be missing something however as these permissions appear to be set at a repository level.  I was hoping to have multiple projects in the one repository with security setting such that users could view all models but only edit a smaller number of models where this was appropriate.  I understand that different permissions on a repository can be given to a user - but can these permissions be done on a project by project basis?

I do see now from the images that you linked to in your reply that it is possible to lock a package to a group - this isn't exactly what I was after but it's getting closer and might be something I can work with failing a better solution being available.

[qwerty]

That is sort of possible. You lock certain packages to certain groups so only the members in that group can modify them.

q.

[Stirl]

Thanks its not exactly what I was looking for but I should be able to get this to work for me.

[Geert Bellekens]

Another option is to connect your repository to a version control system and handle access rights there.

Geert

[PeterHeintz]

Yes, but in this case you work in a lock/import->change->export/unlock procedure which at least slows down someting.
But could be the right way for you!?

[Paolo F Cantoni]

Is it possible to set up permissions in a repository so that different projects in the same repository have different permissions?  IE so a user maybe able to edit some projects and only view other projects in the repository. 

If this is possible can someone point me towards how to do this?

Sorry for coming in late to this, but this is entirely possible and how we manage our corporate repository.

It needs s little planning, but we've found it works fine for the past year.

Firstly, you need to partition your repository so that different branches can be specific to each group of users you want to have.

In our case we have, so far, three basic groups of users:
Enterprise Architects (EAs)
Solution Architects (SAs)
Modelling Architects (MAs)

We have three principal branches:
Projects
Enterprise
Integrating

Solution Architects can change Project level objects
Enterprise Architects can change Enterprise level objects
Modelling Architects can change Integrating level objects

Each Branch is Group locked to the relevant Group (SAs, EAs and MAs - as appropriate) recursively.
Each user is then assigned one or more groups as required.  (for example, most EAs are also SAs)

You can use the same concepts to suit your particular situation - with the correct degree of granularity for your purposes.

BTW, for reasons expounded elsewhere, we DO NOT use version control on our repository, successfully relying on Project Transfer snapshots to track evolution and to provide repair mechanisms for the repository.

HTH,
Paolo

[PeterHeintz]

FYI!
What Paolo describes seems to me, is exactly the same what we are doing.
We also transfer, from time to time, our data from MS-SQL to eap/Access-DB and this EA-File goes for some other reasons in a SVN repository.