Object Privacy and Controls

The open nature of BlueDolphin makes the execution of confidential projects difficult or impossible. 

What is your wish?
For BlueDolphin to support confidential projects with a number of enhancements, specifically to object security. See the end of this post for the features.

What is the problem you encounter?
As a large company we have many projects that are confidential. Because all objects are visible to all users in BlueDolphin at all times we cannot use BD for these projects.

Why do you want this wish?
BlueDolphin does not fully support our enterprise because of this gap. We must either spin up a new tenant and later merge it, risk project exposure, or just not use BlueDolphin until the project is no longer secured, which results in a huge amount of retroactive work. 
 

Do you have a workaround? And if so, what is it?
Not an acceptable one. 
 

How would you ideally solve the problem?
Implement the features described below. 

How big is the problem on a scale from 1 to 5?
5 - This ultimately will threaten the use of BD in our enterprise. 

Features

1. Add the concept of groups within the user administration. See this Product Wish for a complete list of admin enhancement wishes.
2. Add the ability to group objects. This could be an app-level feature or an implementation of the Archimate Group concept.
3. Add the ability to control the visibility of objects by group. 
   1. Ability to add users to the group
   2. Ability to add objects to the group
   3. Ability to specify default access level for all objects in the group
   4. Ability to specify access levels for each user in the group
   5. The available access levels would be:
      1. No access
      2. View
      3. Update
4. Objects could be obscured in one of these ways:
   1. Be completely invisible to users without privilege in all aspects - views, search, object repository, reports.
      1. This would leave visible gaps in views
   2. Be obscured to users without privilege - the objects would appear on views, but would just be a box with no information. The properties would state that the user does not have privilege to see the object. 
5. Relationships involving a visible object and an invisible / secured object would also be hidden. Relationships would only be visible if the user had privilege to see both objects. 
6. Enhance the Jaspersoft reporting engine to be aware of object security.