Photos and communication
Upload, share, and control access to project documents
Store files in the right project, keep internal files private, and share only the intended customer-facing document. Follow the current customer-facing workflow and verify access, status, and resulting records before continuing.
Before you begin
- Audience: Standard user, manager, company admin.
- Project/document access
- appropriate sharing permission
- current, intended public document version.
Project → Documents (#/sites/:id/v2?tab=documents); item/document controls; tokenized public document route #/public/documents/:token
Upload, share, and control access to project documents
-
Open the workspace
In JobBuddy, go to Project → Documents (#/sites/:id/v2?tab=documents); item/document controls; tokenized public document route #/public/documents/:token.
-
Confirm access and starting state
Project/document access; appropriate sharing permission; current, intended public document version.
-
Complete the main setup
Distinguish internal uploads, item attachments, estimate/invoice attachments, generated PDFs, and public token links.
-
Review the important choices
Review access inheritance, download, customer-visible flags, approved-estimate copies, revocation/expiry where implemented, and replacing versus editing a shared file.
-
Verify the result
Store files in the right project, keep internal files private, and share only the intended customer-facing document.
Expected result: Store files in the right project, keep internal files private, and share only the intended customer-facing document.
Troubleshooting
The page, control, or action is unavailable.
Confirm the required access and starting state: Project/document access; appropriate sharing permission; current, intended public document version.
The result is incomplete or unexpected.
Project permissions, item attachments, customer-visible flags, generated sales documents, public tokens, versions/copies, and revocation are different access mechanisms.
The issue remains after checking the record.
Capture the exact visible error, record status, approximate time, and intended result. Give support only the minimum customer-safe evidence needed to trace the problem.
What happens next
- Store files in the right project, keep internal files private, and share only the intended customer-facing document.
- Review the resulting record, status, notifications, and related history before continuing downstream work.
- Use the related guide when the next action belongs to another JobBuddy workflow.