ORD/CONNECT One User Preference across multiple workspaces?

i'm back onto setting up my ORD workspaces for clients.

I plan to use the default location for userpreferences to simplify things. This will require me to lock down a few variables in our Organization configuration.

My question is, is there any HARM in using the same user preferences for multiple clients? As far as I can tell, user preferences are personal preferences, and shouldn't really be dependent on client setup, but I'm not certain about that. Some of the clients have user preference seeds, some of them do not. Can you think of anything in


that would be essential to functioning in a specific client environment?

_USTN_PREFNAMEBASE does vary from client to client. I believe that is what I would need to lock down. Either that, or _USTN_HOMEPREFS...

I plan to %lock _USTN_USERNAME = $(USERNAME)

Can you think of anything wrong with this?
If I need to allow for separate preferences for each client, I can do that, but it would be cleaner and neater if I could just go around that.

Parents Reply Children
  • How are you dealing with this sort of thing? What's your preferred approach to managing multiple clients?

    I can't think of too many preferences that would actually affect the design file settings of any project. If that's the case, I'm not convinced that each client really needs its own set of preferences. But I could be very wrong!

    My other thought for managing preferences at the organization level instead of the client level is control of the preference seed. Since UPFs are still corruptible, I'd rather control the preference seed used to create the new one on a reset. While I don't believe client preferences should affect production, I can just imagine the confusion when the replacement preferences are generated from Colorado instead of Ohio.


    Power GeoPak
    Power InRoads
    OpenRoads Designer 2021 R2