This will tell you how the In Vivo Sync App permissions should be configured and how certain users should have the correct permissions to create (or not create) studies objects.
Organization level permissions (with Folder Selector feature turned on):
- The In Vivo Sync app should be permissioned as a “Member” of the organization in Benchling core. If the folder selector is turned on and the In Vivo Sync app is a member of the organization it will have access to all projects that are permissioned to Members of the Organization. It will essentially be permissioned access to Benchling core in the same way that a user in the Organization would be granted permissions.
- The In Vivo Sync app can be added to certain teams to inherit team-specific permissions in Benchling core
Registry level permissions:
- The In Vivo Sync app must have WRITE access to the Registry
Schema Level Permissions:
- The In Vivo Sync app has schema-level permissions set to CREATE on all In Vivo schemas
- Members of the Organization should have schema-level permissions set to READ on all In Vivo schemas. This will ensure only the In Vivo Sync App is able to create entities in this schema set.
Project Level Permissions (with Folder Selector feature turned on):
- The In Vivo Sync app must have WRITE access to any project in which you want the sync to be creating entities
- The In Vivo Sync app can have NONE access to any project in which it should not be creating entities
- Note that even if a specific folder is selected in In Vivo, it does not guarantee that the required permissions for the In Vivo Sync app are present on this folder in Benchling.