‘Permissions’ upgrade
- continually enhancing DataFrameworks.

DataFrameworks has introduced the ability of allowing users to take control of how DataFrameworks sets and manages physical folder permissions. DataFrameworks will now allow privileged users to set specific user/group ownership on target folders, along with being able to set variable read/write permissions throughout the managed structure.

Both virtual and physical permissions in DataFrameworks can be defined at the Framework level. This will allow users to continue to set a facility-wide standard in the way that folders are named, positioned and secured. Users will also have the ability to further manage these permissions at the Virtual Folder level.

DataFrameworks defined users and groups will be used to determine which system specific username and groupname will claim ownership of target directories related to Virtual Folders. DataFrameworks user properties already contain the necessary properties that allow you to define which system specific usernames will be used. User groups will now contain properties that will allow you to define which system specific groupnames that you’d prefer to use for each group. Groupnames must be defined in order to allow a DataFrameworks group to become a legal candidate for physical permissions use.

There are a few special options that can be selected on a Framework Node’s permissions properties. Selecting [Use Logged In User] on a Framework Node’s physical user owner will set DataFrameworks to look to the logged-in user who is running DataFrameworks to determine who will become the physical user owner of a newly created and related Virtual Folder. Selecting [Use User’s Primary Group] on a Framework Node’s physical group owner will look to the user owner and apply that user’s system primary group.

It is important to note that that the write options will not be enabled on an Virtual Folder that exists above a Reservation-level. Since users shouldn’t be allowed to write above that point, DataFrameworks will disable that option to prevent it. When multiple Reservation-levels are possible, DataFrameworks will adjust write options, as necessary, to protect against users writing where they shouldn’t.

Only users with Virtual Folder Administration security access will be allowed to alter existing Virtual Folder permission values. Users with this access can adjust permissions values at any time and any related physical folders will adjust immediately.

Virtual groups that are associated to Virtual Folders are no longer passed down to child Virtual Folders through inheritance. Virtual Folders now look to their related Framework Nodes to receive the virtual groups that they are to be associated with. This way, a facility can easily pre-determine which virtual groups should have access to which types of Virtual Folders. As before, virtual groups can be added and removed at will from Virtual Folders by users with Virtual Folder Administration security access. No virtual groups are assigned to Framework Nodes by default, so it is heavily recommended that users assign these relationships immediately to any existing Framework Nodes to allow appropriate access to their users.

Recursion options exist for both virtual and physical permissions settings in order to allow users to quickly pass down appropriate settings. ‘Write’ options will be ignored at levels in which ‘write’ options are illegal. Interrupting a recursion request process by hitting the ‘Cancel’ option will leave affected Framework Nodes/Virtual Folders changed, based on how far it has traversed.

Customer Benefits

"We’ve reduced our storage needs by 40%."


"We’re managing over 70 TBytes of data with only two people."