This was described in a number of places, but the place referenced in the description was the one place that this was not made clear. This PR fixes that.
One thing to note is that deploying a user artifact just requires acess to the rest apis, while a system artifact requires access to the filesystem on the cdap master, so it is more of an admin operation, (by design)
John Jackson November 19, 2015 at 7:20 PM
System artifacts are available across all namespaces while user artifacts are local to one namespace.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
The documentation doesn't clearly specify what the difference between deploying the hydrator plugin as a system artifact vs user artifact here:
http://docs.cask.co/cdap/3.2.1/en/included-applications/etl/custom.html#plugin-packaging-and-deployment