Non visible Packages

[cfranco]

Hello,
I want to add more security to our Documentation repository. I would like to assign the visibility of a package to a user or a group. When a user A open the project, then only some package will be showed.

Is it possible? As I saw in the online documentation, you can only protect the write access, but not the read one.

Thank you for your support!

[Geert Bellekens]

No that is not possible.
You'll have to use different repositories to achieve that.

Geert

[cfranco]

No that is not possible.
You'll have to use different repositories to achieve that.

Geert

And which is the best way to share some common packages? Example:
Package A -- Common for both repositories
Package B -- Only visible for group X
Package C -- Only visible for group Y

As I understand, I need to create 2 repositories R1 and R2.
In the R1 I will create the package B
In the R2 I will create the package C

But how can I add the Package A in both repositories? I want to keep all the relations between elements in different packages also.

Thank you for your good support.

[Stefan Bolleininger]

You could write an addin, which denies the the user the access to an package.

Give your inaccessible package an value or modification which will be casted at the package click and doubleclick.

BUT:

what are you doing if someone shuts off the add-in  


What are you trying to achieve with the permissions for groups?

regards

Stefan

[cfranco]

You could write an addin, which denies the the user the access to an package.

Give your inaccessible package an value or modification which will be casted at the package click and doubleclick.

BUT:

what are you doing if someone shuts off the add-in  


What are you trying to achieve with the permissions for groups?

regards

Stefan

Thanks Stefan, we have some users that should not have access to some packages, but we want to have the repository as centralized as possible. Look at the scenario in the previous post.

Thanks again for your support!

[Geert Bellekens]

We use version control to manage shared models.
We currently have two repositories (databases), lets call them A and B
Both repositories use a common model (C)
C has been started in one of the two repositories and then the complete model has been controlled in version control.
Then it was imported in the other repository.
From then on we can work on the common model from either repository.
The only thing is that you have to do a "getlatest" in one repository if you have checked from the other in order to see the latest changes.

Geert

[Robert Sheridan]

You could export from your master to the other repositories and lock the packages from the master that you do not want the users of the other repositories to use.  This would enable them to reference the elements but not change them.  You would them do the reverse, import from the sub repostories into the master to maintain the master.  All very time consuming  but do able.

If you make the packages invisible then you run the risk of people replicating the functionality or missing dependencies etc.