Setting access permissions to DGN's via the PCF

This can be accomplished via the User Preference File (UPF)
The user configuration file has two basic workspace functions. First, it contains values for any configuration variables set by you, the user, to control the product's behavior. Second, it specifies the active workspace components. For example, the MS_USERPREF configuration variable setting points to the user preference resource file that defines the active user preferences component. (The user configuration file is the file that opens when you select Workspace > Configuration.)
User configuration files have the suffix “.ucf” and are stored in Bentley's "...\Workspace\Users" directory. You can select any available user, project, and interface as the components of the active workspace. The active workspace components are identified by the user configuration file.
You can also restrict / deny users permission to projects via the programs desktop icon, by right mouse click and from the pull down menu, select property’s, and the security tab from the following dialog box Here you can allow or deny a particular user selective permissions.

Hi Stan, thanks for the prompt response.

I've actually configured a network deployment in line with Marc Thomas's blog post (communities.bentley.com/.../aecosim-building-designer-ss6-quickconfig). Therefore we don't use the User, Project & Interface drop-downs in the way you're describing.

A "CompanyStartup.cfg" script remaps each user's workspace to the network deployed workspace. We leave User & Interface as their defaults ("BuildingDesigner" & "default" respectively), and only change the Project drop-down to select the particular project we're working on.

Our BIM server file-structure is as follows & Windows permissions are as follows:

Everyone has read-write access to:
\\BIM\_Projects
\\BIM\_Users
\\BIM\_Users\<username>\prefs
\\BIM\_Users\<username>\interface

Read-write (BimAdmins) & read-only (BimUsers) to:
\\BIM\_Workspace
\\BIM\_Workspace\Dataset_Company
\\BIM\_Workspace\PCF
\\BIM\_Workspace\Standards

I was just wondering if there was a way to lock-down particular nominated DGN's in a project via the PCF (or some other mechanism only modifiable by BimAdmins. Forcing the nominated DGN's to open read-only would be one way; An acceptable alternative would be if we could perhaps password protect nominated DGN's against being edited (reads ok)?

Hi Thomas,
I assume you're not using ProjectWise? This sounds exactly like something that is typically achieved through PW permissions/work states. That said, is it down to specific DGN files within the \models folder or the entire \models folder? I'd imagine the latter may be possible using a similar process that you're already following, but I've never come across a way that allows one to lock permissions at the file level. Not saying it can't be done, but if so, I'd also be curious how. :)

Hi Steve,

We're not using PW no. Too costly & slow for now.

What I am trying to achieve *is* technically to do with permissions and file status. It'd basically be the entire models folder I'd want to lock down. I'm trying to avoid having to do it with windows permissions, as our it dept have to set those, and managing them will be a nightmare.

Next option is to have a mirror/duplicate projects structure, one "approved" and one "wip" which will be easier to manage permissions for, but which will duplicate a lot of files. :/

I mean, is there a way to %lock a whole dgn against edit? Perhaps even password protect??

So far I haven't found any good way to do this... Locking down all of ABD thru configuration, simple. Locking down a folder using Windows permissions, simple. Locking down a specific folder - should be doable, but I'm afraid I don't know workspace configuration quite well enough to figure that one out. Hopefully someone reading this thread will have additional input...

So far I haven't found any good way to do this... Locking down all of ABD thru configuration, simple. Locking down a folder using Windows permissions, simple. Locking down a specific folder - should be doable, but I'm afraid I don't know workspace configuration quite well enough to figure that one out. Hopefully someone reading this thread will have additional input...