Granting access to packages

[ea0921]

Hello guys
We are going to hide some packages in EA software for some people and they can only work on the packages that we specify.
We did not find this feature in EA software, if anyone knows a solution, please help us.

[qwerty]

You cant. If you want to divide your model then do just so. Create individual packages and have a place where you can merge. Good luck.

q.

[Geert Bellekens]

You can hide root nodes for certain groups, but that's just a visual feature, not security.
They can still access the elements in that root node if they use search, or...

If you are serious about this then you'll have to make custom project for each group, and use version control to stitch it all together.
A lot of overhead for a small gain

Geert

[ea0921]

Is it possible to get the permission to read a package from a certain group by activating the visibility level admin feature?

[wivel]

Is it possible to get the permission to read a package from a certain group by activating the visibility level admin feature?

Hi

I almost went that route at a customer, to hide certain packages for a certain group of people in WebEA, but never did it. Since the information that should be hidden was not related any part of the 'unhidden' model, we decided to have 2 separate models. Less admin hassle and easier to maintain.

If you decide to go down the 'Visibility level' path, please share your experiences.

Henrik
Henrik

[BobM]

I almost went that route at a customer, to hide certain packages for a certain group of people in WebEA, but never did it. Since the information that should be hidden was not related any part of the 'unhidden' model, we decided to have 2 separate models. Less admin hassle and easier to maintain.

If you decide to go down the 'Visibility level' path, please share your experiences.

Sharing our experience for making WebEA folders invisible:
It's perfectly possible to hide folders for users, note that navigation by navigation cells or passthrough child models always allows you to navigate to invisible parts, which is a good thing

We did have to remove breadcrumbs and path button so people couldn't try to navigate to parts they are not supposed to see 'yet' (as breadcrumb and path do display the "invisible" parts allowing people to take a peek and potentially waste their precious time)

By default, we have disabled browser as well

[wivel]

I almost went that route at a customer, to hide certain packages for a certain group of people in WebEA, but never did it. Since the information that should be hidden was not related any part of the 'unhidden' model, we decided to have 2 separate models. Less admin hassle and easier to maintain.

If you decide to go down the 'Visibility level' path, please share your experiences.

Sharing our experience for making WebEA folders invisible:
It's perfectly possible to hide folders for users, note that navigation by navigation cells or passthrough child models always allows you to navigate to invisible parts, which is a good thing

We did have to remove breadcrumbs and path button so people couldn't try to navigate to parts they are not supposed to see 'yet' (as breadcrumb and path do display the "invisible" parts allowing people to take a peek and potentially waste their precious time)

By default, we have disabled browser as well

Thanks. I didn't know that you could still navigate to 'invisible' parts, which I also see as a good thing. Also, disabling the breadcrumbs. Would not have thought of that myself.

I always recommend disabling the browser and navigate through the model via diagrams and landing pages, to both steer and help the user through the information in the model(s).

Henrik