Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum The parent folder conundrum...
    • Sign In

    • State Not Answered
    • Replies 8 replies
    • Subscribers 63 subscribers
    • Views 4577 views
    • Users 0 members are here

    The parent folder conundrum...

    spear
    Offline spear over 8 years ago

    I've found and read about the issue of not being able to lock down the read/write/modify properties of a parent folder while still enabling those permissions on subfolders below it.

    My question is... what have people used as the best workaround or compromise to it?

    • Sign in to reply
    • Cancel
    • Scott M. Turner
      0 Scott M. Turner Mon, Jan 19 2015 2:50 PM
      There are a few ways to do this, but I sure do wish PW would handle security a bit differently.
      What I do is to create environments and set security there. This has advantages since you can also associate a view with the environments which allows you to show subfolder names and details at the parent level but still provide document details below.
      I also use workflows as a means of providing different security settings to different folders that are in the same environment.
      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Yvonne Veltman
      0 Offline Yvonne Veltman Tue, Jan 20 2015 3:26 AM
      We use a template folder structure that gives (limited) access rights to the top folder and more (write/modify) rights to one sublevel.
      Later you can adjust the rights on the top folder; use the top bullet for inheriting access. Then people still can work in everything underneath like they used to.
      The template also provides the right environment and workflow settings, similar to what Scott says.
      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • spear
      0 Offline spear Tue, Jan 20 2015 4:15 AM in reply to Yvonne Veltman
      Thanks! So to confirm, I can copy the environment in the administrator that has default project folders with no permissions to delete or rename folders and then enable those two settings and make it the default environment for new folders being created by users within the project folders ?
      Or will the users have to specify the environment when creating subfolders?
      Will changing the default environment for new folders created will not effect any existing projects will it?

      Thanks again for the insight!
      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Yvonne Veltman
      0 Offline Yvonne Veltman Tue, Jan 20 2015 5:48 AM in reply to spear
      Uhm, I am not quite sure if I understand the first part of what you're saying. Environment is about metadata of the documents; security settings is a different thing.
      Let me try to make things clearer by explaining the basics of our template: the top folder in a project gives read-permission only. Environment is not important, since it contains no documents. It has a few subfolders, like CAD (with an appropiate environment for drawings) and Office (environment for Word, Excel etc). Within those subfolders, people have create/change permission to folders, and create/change/delete permission to documents. The subfolders they make, will inherit automatically the right environment and security settings from the direct parent. People are able to choose a different environment for a folder (as long as the folder is empty), but won't easily be likely to do so.

      Changing defaults in permissions, or changing the default environment will only apply to new folders/projects etc. Changing environmental properties (different fields) will always show the new properties, even for old documents.

      Hope this helps!
      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • spear
      0 Offline spear Tue, Jan 20 2015 7:26 AM in reply to Yvonne Veltman

      "The subfolders they make, will inherit automatically the right environment and security settings from the direct parent."

      This is the issue... we want users to be able to create, change, and delete subfolders but don't want them to be able to change or delete their parent folders that are defined in the project template.

      I guess I misunderstood Scott's point about setting security in the environment.

      Alternatively, can we achieve this by creating a workflow and state for new subfolders?

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    >

    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies