Remus Avram Posted August 2, 2016 Report Share Posted August 2, 2016 Hi all, is there a way to disable upload files to ftrack server? We would like to restrict the permissions for publishing new versions using the web interface. All versions published should be done via the API. Cheers! Link to comment Share on other sites More sharing options...
Björn Rydahl Posted August 3, 2016 Report Share Posted August 3, 2016 Hi Remus, thank for the request. I have heard this one before, so it would be interesting to see if anyone else is also interested in this. One question though, when you say disable all publishing. Do you really mean that? I'm thinking about things like uploading into a review session, adding reference media to things etc. which are also versions. Or would you see it more as a permission? Cheers Link to comment Share on other sites More sharing options...
Remus Avram Posted August 3, 2016 Author Report Share Posted August 3, 2016 Hi Bjoern, thanks for your answer! I think the most awesome way is to manage it as a permission. The main idea is to not allow users to publish versions using the web interface. Also to limitate the publish using the ftrack-connect. Everything that is published needs to go through our Pipeline. Even uploading into a review session or adding reference media needs to go through our Pipeline as we don't want them them on the ftrack server. If we can control where the files go, then we can allow some uploads using the web interface. I hope this makes sense. Cheers! Link to comment Share on other sites More sharing options...
Remus Avram Posted August 9, 2016 Author Report Share Posted August 9, 2016 Hi Bjoern, I was just wandering if there Is any estimation when this will be implemented? The most critical part is the part of publishing a new version using the web interface. This can not be handled in pipeline and can create confusion. Cheers Link to comment Share on other sites More sharing options...
Björn Rydahl Posted August 10, 2016 Report Share Posted August 10, 2016 Hi Remus, it is currently not planned, so I cant give you any dates at this point. But, there is another feature coming soon which would allow you to communicate with a user after they have uploaded something. Do you think you could use that as a workaround? Basically a user uploads something, you listen to that event and respond with a message "You are not allowed to upload in the UI, please do like this instead..." and then you remove the uploaded version. Cheers Link to comment Share on other sites More sharing options...
Remus Avram Posted August 10, 2016 Author Report Share Posted August 10, 2016 Hi Bjoren, thanks for your answer! It is not the best workflow for us, but we can give a try. Are the update new version and update thumbnail 2 different events? cheers Link to comment Share on other sites More sharing options...
Björn Rydahl Posted August 11, 2016 Report Share Posted August 11, 2016 Hi Remus, you can use the component added event and then just check if it belongs to a version. Or listen to update events and find assetversion of the type upload. Cheers Link to comment Share on other sites More sharing options...
Remus Avram Posted August 25, 2016 Author Report Share Posted August 25, 2016 Is it possible to limit the size of the file which is allowed to be updated on the server? Link to comment Share on other sites More sharing options...
Lucas Correia Posted August 26, 2016 Report Share Posted August 26, 2016 Hi Remus, At the moment is not possible to restrict the file size of user uploads. Regards, Lucas Link to comment Share on other sites More sharing options...
Remus Avram Posted August 26, 2016 Author Report Share Posted August 26, 2016 I think restricting the files size of user updates will be a better approach then disable update to the server. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.