@ltproberto Screenshots (and the ability to capture them) is part of an operating systems … like Windows or Mac iOS, not of an application. While there are some ways of doing this on a mobile device, computers don’t seem to have that functionality. Google searches might be your best bet on learning more.

I don’t see this ever being truly achieved.

The browser will never know if I am using my phone.

If they want it that bad - they’re getting it.

@ltproberto Since you can’t really prevent this from happening, the next best thing might be to really know who it is that is accessing your content. For example, if you content ‘for official use only’ (aka gov’t security compliance required) you can implement SAML 2.0 (aka single sign-on) which will require additional Docebo administrative and IT coordination to register the learners in your platform. You can implement SAML 2.0 for any of a number of reasons, not just FOUO.

Agree that this is a big issue and one that is very hard to solve. One potential deterrent, but not a foolproof solution, is dynamic watermarking. Learn doesn’t have anything like this at the moment, but there’s an idea you can vote up if you like.

@ltproberto Hopefully all of your content, like every “slide” contains a copyright statement.