I'm hoping for future ArcGIS Pro releases that an ability to password protect an APRX will be added. Similar to how you can password protect a WORD Document.
But what exactly do you want to protect? The data in the file-geodatabase can be accessed anyway. Wouldn't it be more feasibly to just do the access managment outside of arcgis pro?
The idea of locking down layers and making them read-only is very different as it assumes anyone would have access to the project. I can see a use for that; creating a project, making its contents read-only, but allowing access by anyone.
My request/suggestion is password protection so ONLY those persons given access/the password to the ProProject could open it at all - just as in any password protection paradigm.
These are two different requests, serve very different purposes, and should remain separate requests.
Thanks for the clarification, @JannSamuels. I've re-opened the idea.
Can you explain a bit more about where you and your ArcGIS Pro users are storing their Pro projects (.aprx files) and who has access to those directories? I'm assuming that there are one or more common locations that multiple ArcGIS Pro users have access to, and all .aprx files are stored there, yet you only want some Pro users to be able to open certain projects and so on. Possibly due to data sensitivity issues?
Anyway, that is how I'm conceptualizing the issue, but if you could share some details about the problem you're trying to solve it will help us better understand the need to password protect projects. Perhaps the planned portal project capability shared on the Pro roadmap would meet your needs.
I love this idea. We are currently using ArcGIS Pro Layout to configure/display our current GIS configuration/infrastructure to show how and where our GIS data is coming/going. Since this Pro Project shows server names and some sensitive information, it would be nice to password protect it. I understand that not everyone can access ArcGIS Pro (since its named licenses) but there are still some GIS staff who do not need access to this information.
@AJFerrand1 Can you explain some more about the use case?
What is the end "product" of the Pro projects? Is it a layout that is printed/exported to PDF? Is that shared to others who need information to make decisions? Are there web maps that are published from it?
My understanding is that GIS staff still need access to sensitive projects like this, but those same staff should not be able to see server names? What other information about these projects should be restricted to some users?
Is it possible to store the projects in a file share and control who can access to the share? Or do you have a requirement for Pro users to access the project how - like a view-only mode? What are your expectations about what those users should be able to do vs. what they shouldn't be able to do?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
