Prevent New Public Content Folder Creation
In BI Office, a setting in the Admin Console (called Multi-Tenancy within the Networking settings) prevented anyone without admin rights from creating new "top level" folders under the Public Content folder. Is there a way to do something similar in Pyramid 2018 such that only Enterprise Admins would have the ability to add new folders directly under the Public Content folder?
Currently we do not support that functionality, Unlike BI Office, Pyramid 2018 has multiple public folders (each tenant is designated its own public folder). Also in the upcoming release Pyramid 2018 will enable the possibility for cross tenant items to be created (only an enterprise admin will be able to create cross tenant folders & items).
Roi, cross-tenant functionality will be the only way we (the VA) will be able to use the tenant options of Pyramid 2018 at all. Do you know when this functionality will be available? Also, will that functionality extend beyond folders to include roles and data sources?
Its coming out in Q1. The cross tenancy will be driven by roles & will extend to all item types including data sources. We will produce a detailed explanation on how the cross tenancy works with the release notes.
Roi, going back to the original question on this, I think being able to prevent "top level" folders under the Public Content folder (with or without tenants involved) is still valid. Without tenants involved, there are likely still scenarios where only a set of "trusted" users should be able to create folders just under the root of the Public Content folder; otherwise, with hundreds or thousands of users, the Public Content folder will likely get fairly chaotic fairly quickly. And even with tenants involved, this still seems to be a valid need within each tenant.
Should we submit a feature request for this?
Brand new Pyramid customers here and we are infuriated that we cannot set "read only" access to the top-level Public Content folder.
How in the world are we supposed to implement quality control & approval processes when any user can simply create new folders at the top level structure?
This is really an insane oversight. Pyramid: There's no centralized control.
This functionality is available in the product.
FYI We just updated to 2018.05 and the option now exists.
Turns out the feature "Settings - Multitenancy - Disable folder creation at the top level of the public content domain" has been implemented.