Setting Folder Permissions for Several Groups

PDM Pro 2018

I've been setting folder permissions by going into a Group, selecting Folder Permissions, selecting a Folder, then checking each permission that applies.

This works because our folder structure was copied from PDM workgroup.  We then set up users and groups and set the permissions.

Now we have many groups and are making new folders.

Is there a way to select a folder, then set the permissions that apply for several groups at one time?

I find myself going into each group selecting the same folders and selecting the same permissions.

Seems like there should be a more efficient way.

SolidworksSolidworks Pdm/enterprise Pdm
Answers 7
JS
JS 2021-04-09 Best Answer

1-EW-4524 wrote:

Is there a way to select a folder, then set the permissions that apply for several groups at one time?

I don't think so.

1-EW-4524 wrote:

PDM Pro 2018

I've been setting folder permissions by going into a Group, selecting Folder Permissions, selecting a Folder, then checking each permission that applies.

This works because our folder structure was copied from PDM workgroup.  We then set up users and groups and set the permissions.

 

Now we have many groups and are making new folders.

Is there a way to select a folder, then set the permissions that apply for several groups at one time?

I find myself going into each group selecting the same folders and selecting the same permissions.

Seems like there should be a more efficient way.

A more efficient way would have been to organize your folder structure around your groups.  For example:

Then you can set permissions on folders at a higher level and they can apply to any folders downstream.  However, since you missed that chance to reorganize, you may want to make use of templates instead.  Rather than have users create new folders, have them execute a template which will create the folder and apply the appropriate permissions.  You can force (encourage)  them to use the template by locking down permissions on the parent folder and then executing the template as a user with more permissions (e.g. admin).  Them template can also create any subfolders you want and copy in any standard files.  This can help ensure consistency.

For example, I have a Engineering Project template that pops up a dialog where users enter pertinent project info:

When they click OK, a project folder is created with the project number and description as the folder name:

Inside the folder, several standard subfolders are created:

Another great benefit of templates is that you can execute them from any location in the vault and the created files and folders will always go to the right place.

comment imagecomment imagecomment imagecomment imagecomment imagecomment imagecomment imagecomment image
PW
PW 2021-04-09

I would suggest sticking with one vault if possible. There is no tool to combine vaults, so if you have two and decide to go back to one in the future you have to figure out how to export and import all the data.

Just create two sections in the vault for the different groups to have access to. Then you can give access where needed. If you have two vaults then people have to have be connected to both vaults and might think it is a good idea to use parts from 2 vaults in an assembly. 

For the top secret projects you could have a section of the vault dedicated to that and them move the projects out when they go mainstream.

TS
TS 2021-04-09

The hierarchy of folders does present some challenges.  I wish permissions were purely property based.  But we are stuck with an organization method created 35 or more years ago.

Our vendors currently connect to our system with too much access.  I'm considering a few new things for them.

TS
TS 2021-04-09

We currently have 6 engineering groups at 2 locations.  We will be adding 8 more at 4 other locations by the end of the year.

We will have about 160 engineers contributing to the database.  Then there's all the data consumers.  Which may be part of PDM or another system we export to.  Undecided at this point.

Initially the thought was to put everything in one replicated DB. But I'm considering the benefits of separate vaults and less sharability.

There are portions of the office that work on "top secrete" projects that add people as they gain momentum and then become common knowledge.  So the thought of what is a "project" and "how big" a project is needs to be considered. 

I've done training material on both on web sites and document management systems before.  My intention was to add to our company share point but as I started this project a few months back they decided to upgrade and change to a cloud based system.  It's now quite different an will take relearning.  And there's several layers to login and I don't believe they've turned on all the sharepoint features we had before.  My preference is to have it in something I'm in control of.

PW
PW 2021-04-09

I found it is easiest to have a few groups as possible. Have specific groups for users that must have different permissions and then have a general group that gives read access to everyone for every folder. If someone finds the need write access to a folder they don't have they can request to be added to another group.

One thing this brings up in my mind is a situation like vendors that work on projects in the vault. If you have a project folder with a sub-folder that the vendor works in. You can't have any files in the project root folder that you don't want them to see. I like to make the engineers keep the project root folders empty of files at all times.

JS
JS 2021-04-09

Tom Strohscher wrote:

Thanks Jim

For the most part we several folders off the root representing each engineering discipline (Electrical, Mechanical, Mold, Facilities...  Then there's a 3 or 4 user groups for each engineering discipline.

 

My problem comes when we start to think about common areas where we need to include most people or a mix of people.

Examples: PDM training information. General department information.  Should be just about every user but maybe a mix of who can add/edit.  I was thinking why not use the user groups I already have.

Example: Cross Discipline Project Folders.  Do I create a user group for each project?  Can a template create security groups?

I would not recommend project specific groups, and no, templates cannot create groups.  For what its worth, I moved all training type information out of individual documents and into a  Wiki.  Web pages are much easier to edit browse, search etc:

 

If cross discipline projects lump all engineers together and all projects could have all disciplines then what's the point of engineering specific user groups.

 

Good question.  That's probably why I have one group (Engineering) for engineers.  If you have a project that involves only one group (say Mechanical), why would it matter if another group had access?  What are you really concerned about that is making you want to have such fine grained permissions?  How many groups do you have right now?  How many Workflows?

Tom Strohscher wrote:

 

In your example you have Electrical and Mechanical below the project folder.  Are your Electrical Engineers restricted to their folder and are the Mechanical Engineers restricted to their folder?  Do you user security groups get created on the fly?

 

As I said above, there is just the Engineering group.  I do not differentiate between mechanical and electrical from a permissions standpoint.  They each have their WIP folder in the project folder to work from.  If something is saved in the wrong place, it can be moved.  If something gets deleted it can be recovered.  In practice, it is rarely an issue.

comment imagecomment image
TS
TS 2021-04-09

Thanks Jim

For the most part we several folders off the root representing each engineering discipline (Electrical, Mechanical, Mold, Facilities...  Then there's a 3 or 4 user groups for each engineering discipline.

My problem comes when we start to think about common areas where we need to include most people or a mix of people.

Examples: PDM training information. General department information.  Should be just about every user but maybe a mix of who can add/edit.  I was thinking why not use the user groups I already have.

Example: Cross Discipline Project Folders.  Do I create a user group for each project?  Can a template create security groups?

If cross discipline projects lump all engineers together and all projects could have all disciplines then what's the point of engineering specific user groups.

In your example you have Electrical and Mechanical below the project folder.  Are your Electrical Engineers restricted to their folder and are the Mechanical Engineers restricted to their folder?  Do you user security groups get created on the fly?

Some engineering group are more project specific then others.  A few of our engineering disciplines do things project based while others make designs more generic to be reused as much as possible.  Some engineering groups walk projects through start to finish every time and some just put the design out there to be used.  It could be used once or 100 times with no more engineering effort.

Finding a balance seems to be a trick.