Enhancement request to provide folder-specific Library Admin role. Our release processes for Spotfire objects need to be folder specific, because top level folders are business-area specific. Currently Library Admin role spans the entire repository. For a Spotfire environment that spans multiple business units/lines of business, this type of access is against risk policies for individual business units [You can't see objects for other Business Units].
Ideally we are seeking a more granular Library Admin that can align specific license functions to different object types at the folder level.
Here is a sample repository structure:
\Fixed Income
\Analysis
\Data
\Equity
\Analysis
\Data
1) A DBA in the Equity business unit would need access to change passwords and database connection information for only the Equity folder. He should not be able to see analyses in the Equity Folder, nor should he be able to access/browse/modify database connections in the FixedIncome folder.
2) A lead business analyst in the Fixed Income business unit should only be able to manage a library for the Fixed Income folder, but should not be able to manage anything in the Equity folder.
Similar to SPF-I-759?