...

SnapLogic has a completely uniform access control model based on Read, Write, and Execute permissions. All assets and containers can have an associated user and group access control list (ACL). Specific permissions can be inherited through the nested containers to simplify ACL specification. Groups of users within an organization, when combined with the new permissions model, make it easy to control how assets are used.

Customer Benefits

The assets-and-container-hierarchy model brings immediate benefits to both enterprise customers as well as resellers. 

Enterprise Customers

For mission-critical enterprise customer needs, this approach to organization and permission provides many benefits:

...

In addition, this permissions model introduces simple Read, Write, and Execute (RWX) controls for all containers and assets. This approach, which also draws from existing file systems, lowers the conceptual weight of managing access to different assets. Any asset can be assigned zero or more permissions which form the access control list. A permission consists of a subject type, which can be a user or a group, a subject, which is a user name or a group name and, a set of permissions (RWX). In addition, a permission set as inherited. This allows a user a group to be given access to everything within a folder, including everything in subfolders. This greatly simplifies the assignment of permissions to assets, especially for customers with several projects consisting of several assets.

...

By virtue of fine-grained ACL permissions at the assets and container level, the model is flexible to provide complete security isolation between folders, projects or sub-organizations for each asset type. For example, Snaps, APIs, pipelines can now be completely isolated to maintain security between different containers. On the other hand, assets can also be shared across containers, thus enabling cross-departmental and organizational collaboration. 

Example Customer Hierarchy and Permissions 

...