If you know what vendor and/or solution was chosen, I would check their docs.
One key thing is whether this is a network based DLP solution (in which case, you could check the docs for BroIDS to see how they conceive of DLP), or a local agent based one (i.e. some extension to an antivirus solution).
On a very basic level, a DLP solution will look for either keywords, or content hashes (e.g. sha256 digests) to identify 'sensitive' data that should not be allowed to leave your control/area of visibility.
As usual, it is more complicated than that, but that's the very, very basic functionality you should expect.
In theory at least, DLP shouldn't prevent you from accessing something (that's a job for ACLs and other access control mechanism), it is more meant to prevent you from storing the data in bad or unauthorised places (e.g. sending yourself or others passwords, credit card data, proprietary code/information, etc).
There are generally ways around DLP if you really, really, want to find them, but if your DLP solution isn't allowing you to do your job, fix the solution, don't work around the limitation.