FieldCampDocument Package Permissions and Troubleshooting
Who can create, build and send FieldCamp document packages, which plan is required, and how to fix packages that are missing, out of date or not sending.
This article lists the plan and permissions document packages need, and how to fix the most common problems.
Plan and permissions
| Task | What you need |
|---|---|
| Open Package Studio and create or edit packages | The Pro plan or a free trial, and access to Document Templates in system settings (administrators have it). |
| See, build and preview a package on a record | Permission to view the record's files. For jobs this is the Jobs view assets permission. |
| Send a package | Administrator or owner, or permission to send invoices or estimates. |
| Set up an automatic send | Permission to create workflows. |
On a plan without document packages, Package Studio does not open and you are taken back to the Packages tab. Upgrade from Settings → Plan & Billing. See roles and permissions for how custom roles work.
Pages only print the fields the person building the file is allowed to read. Staff who can only see records assigned to them see only those records in the file.
Franchise workspaces may show Managed by HQ — this package is read-only in this workspace. Ask your HQ team to change the package.
Troubleshooting
The Packages tab shows an upgrade message, or Package Studio won't open
Your plan doesn't include document packages. Check Plan & Billing, or ask an administrator.
I can't find the Document packages card on a record
- No package applies to this record. Check the package's For object and its Show when condition.
- You may not have permission to view the record's files.
- If your page layout was customized, ask an administrator to add the Document packages block to the layout.
A package shows Waiting
At least one page would print nothing for this record, for example no estimate or no photos yet. The row says what it is waiting on, for example "Waiting on Estimate, Work order & forms, and Site photos: nothing to print there yet." Add the missing content, or select Generate anyway and those pages are left out.
A package shows Out of date
The record, or something it was built from, changed after the build. Select Rebuild, or confirm Send anyway if the earlier file is still right.
A package shows Missing a section
A page had nothing to print or couldn't be drawn. The row lists each page. Fix the cause, then Rebuild. If you want the page left out on purpose, clear Include in the file on that page in Package Studio.
A build failed or never finished
Select Try again. A build that takes more than a few minutes is shown as Couldn't build, and the last good version stays available.
The email goes as a link instead of an attachment
Files over 20 MB are sent as a secure link. Secure links stay open for 7 days; send the package again after that.
I can't change a package's For object
The For object is locked once the package has built a version. Duplicate the package and create the copy for a different object.
The package didn't send automatically
Open the workflow and check its run history and the Show when condition. If the customer is the recipient, the client needs an email address. A record can also have auto-send turned off from the ⋯ menu on its package row.