Try having the end-users create the processes they will be using. That way you can bridge the gap between their work knowledge, and the quality control of knowledge which Promapp allows, while putting things in a form they can engage with.
Not sure how the permissions are set up on your Promapp environment but I would say, the display of the information (process) is key.
The way you categorise processes into groups will be critical. Don't create groups based on org structure, but instead create it by function or service.
So the groups almost serves as a Service Catalogue.
== Example ==
Org Structure Based Groups: HR > Compensation Team > Claims > "Submit a Claim for xyz" process
Function/Service Based Groups: Maintain Workforce > Compensation Claims > "Submit a Claim for xyz" process