Documentation‎ > ‎

Permissions

Summary

Permission levels are defined for view, update and insert resources. A permission code specifies how permissions will be propagated:

  
View
 
Edit
 
Use
 n User cannot view  User cannot edit  User cannot add data to (= use) the resource
 s User can view, given that the owner of the resource is the user User can edit, given that the owner of the resource is the user User can add data if  the resource created by the user
 yUser can view User can edit  User cannot add data


Downstream Permission Propagation

Whenever a user is given a permission level on an S3DB entity, for example a project, that same permission migrates equally to downstream resources (collection, rules, etc). If for some reason the user is given a different permission level on a downstream resource, for example in a collection, than that permission will be merged with the permission being propagated from the project and it is the final permission that will migrate to downstream resources (items). Merge is restrictive in case the permission level is described using uppercase symbols (for example, a merge of 'y' and 'N' results in 'N') and generous otherwise (for example, a merge of 'y' and 'n' results in 'y'). If the user received propagated permissions from more than 2 sources, all of the sources will be merged to produce an effective permission level.

Comments