When an app is shared with another user by granting that user permissions the user may not able to use the app to run a job because file permissions have not been set up in the files service for various directories on the execution system and archive system.
The user may need READ or MODIFY permissions in order to run the app on a target execSystemId.
One option is to automatically grant permissions using calls to the files service, possibly with an option to turn it off. One scenario to consider is when the app owner is not the execSystemId owner.
When an app is shared with another user by granting that user permissions the user may not able to use the app to run a job because file permissions have not been set up in the files service for various directories on the execution system and archive system. The user may need READ or MODIFY permissions in order to run the app on a target execSystemId.
One option is to automatically grant permissions using calls to the files service, possibly with an option to turn it off. One scenario to consider is when the app owner is not the execSystemId owner.
Quick summary of systems and directories:
See related issue in tapis-systems concerning the jobWorkingDir defined in a system.