nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Prevent or limit ArcGIS Pro publisher ability to create a new REST folder

MickC

It would be a great enhancement if administrators were able to prevent users from creating new folders within the REST structure when publishing to hosting and referenced servers. It would also be ideal that users can be limited to specific, existing folders when they do publish features.

Currently users can create a new folder in REST at the time of publishing. This opens the risk that structured folders become unstructured.

Similar ideas have been mentioned previously; however this remains an issue and concern for good data management.

I would like to see this included in a future update please.

Find more posts tagged with

Under Consideration

Status: Under Consideration

Comments

JenniferSmits

This is an important governance improvement - seconded.

DeanMoiler

I agree, this would still be a very useful capability to have. Custom roles have been around quite some time, though they have gotten more fine grained they don't allow restriction of publisher users to create folders for server based services.

You can restrict users from publishing to entire servers, by changing the server role, but not from publishing anywhere / creating folders on the server.

AxelLévy

Essential if you have to manage many publishers

JoshuaThomson1

If Organisations with many publishers are to have any chance of creating and maintaining consistent server folder structures, this is essential.

NielsVemmelund1

i agree - and would like to add a special case: prevent users from publishing to the root folder

Scooter42

Might need to post a new idea, but in the same arena...

Prevent certain publishers from using dedicated instances.

KatherineMichael

We really need this ability to restrict which folder a publisher can put services in and the ability to restrict the creation of new folders within the REST structure. I have many users in multiple departments that need to be able to publish and manage their specific services, but having it wide open like this results in services getting dumped in the root folder, folders being created that don't conform to the naming convention, and folders created with different names that serve the same department/purpose.