@Meg - biggest use case right now is based on another limitation in the system (I will post ideas related to this and follow up here with idea #s). Because bulk action is bundled with view access at the role permission level, we are having a hard time separating operations from governance. Our Foundation CEO has to approve all grants over a certain amount based on Foundation delegation of authority. These grants all get reviewed by a grant committee and decided which ones will move forward for formal approval. There are a lot that could need to be approved at once, AND we need to log the CEO's approval. So for efficiency sake, we ideally would want the CEO to bulk approve those that need approved rather than going into each grant record to approve when he's already gone into each record once to review. We've done all we can on this end to separate those that need approved into a different workflow for him, labeled that workflow appropriately, set up filters for CEO to use on applications tab so he can bulk approve, but because view all access and take action is bundled together, if he forgets to apply the filter, he accidentally approves grants that are premature. This is a HUGE control issue. If these role permissions can't be separated, to satisfy the control issue, we would need to remove his access to take action on all, take his approval of offline, but document it in each grant record for our auditors and for our finance folks who are checking that DOA is followed before releasing a payment. This is even not the most efficient manner because it has finance having to check multiple places for the right info, rather than being able utilize a merge doc to systematically document who approved the application and when (would also need to add 'approved by' as a standard useable/reportable field under the Application/Nomination report area). I would think that the system would be able to allow us to utilize it to the fullest capability from an operations AND governance standpoint. Right now it very much feels operations focused and creates offline workarounds to document governance when we are really trying to encourage the behavior of everyone using this system that we are paying a lot of money for :).

Thank you for your feedback. Could you please provide a specific use case for how you would like to use this with a real world example? What kind of attachment would you want to apply to multiple applications?