Hi @evanadley, being new to Jamf Pro I'm not an expert on this product but the method I use to deploy a package is:

1. Settings > Computer Management > Packages > New > Filename, Choose File to point to .pkg file > Save (to upload). Edit Display Name, Category etc. as necessary.

2. Computers > Policies > New > Packages > Set Display Name, Trigger, Frequency etc. > Add newly created package > Scope (set as required) > Self Service (enable).

Users are then able to select the package through Self Service.

Hope this helps, or at least points in a direction where you may be able to self-resolve, but feel free to request more info.

Deploying a package is fairly simple. 

1. If the source files are in a .pkg or .dmg you can upload directly to Jamf.
   
   
   
   1. If they are not in a .pkg, or .dmg you will need to package the source files, and this can get complex.
   
   
   
   


2. Add the source files to a policy payload.


3. Scope the policy, and set triggers.


4. Done.

However, lots can go wrong even assuming you did nothing wrong. Knowing what issues, you are seeing would help us provide advice. 

https://learn.jamf.com/bundle/jamf-now-documentation/page/Deploying_Mac_Packages.html 

I have a package that i need to import into Jamf Pro. The package itself has more then just a .pkg file and it looks like the other files are needed for the application to be installed. How do i set that up? It's been awhile since i used jamf and to be honest i am a windows guy.