# Sending documents saved to a job

Source: https://help.mucka.ai/clients/send-saved-job-documents
Category: Clients
Last updated: 2026-08-23

> Attach certificates, warranties, receipts or anything else filed against a job to the emails you send from it.

Anything you've saved to a job can go out with the emails you send from that job. No second message, no digging the file back out of your phone.

## Attaching a document

Open the job and send as normal, whether that's a quote, an invoice, a certificate, or just an email. Underneath your message you'll see **Saved to this job** with the documents filed against it listed below.

Tap a document to attach it. Tap it again to take it off. Attach as many as you need, up to five in one email.

If a job has nothing saved to it, you won't see that section at all.

## Sending documents on their own

Sometimes there's nothing to say and you just need to get the paperwork over. Leave the message empty, attach what you need, and send.

Mucka writes a short line for you so the email isn't blank, naming what's attached. Your usual sign-off still goes on the bottom.

## Saving a document to a job in the first place

Open the job and find the **Attachments** section. Drag a file in, or tap to browse for one. You'll be asked to name it and pick a category (certificate, warranty, receipt, contract and so on) so it's easy to find later.

PDFs, Word and Excel files, CSVs and images all work, up to 10 MB each.

## Asking Mucka to do it

You can also just ask. Say or type something like "send Dave the certificate off this job" and Mucka will find the document, show you exactly what's going and who to, and wait for you to approve before anything leaves.

## Certificates Mucka made itself

A CP12, a boiler service record or any other certificate you've filled in on Mucka isn't a file you uploaded — it lives with your certificates rather than in the job's attachments, so you won't see it in the **Saved to this job** list.

Ask for it anyway. "Email Dawn the service record off that job" works exactly the same way, and the certificate goes out as a PDF with the email. Mucka names the certificate on the approval card so you can see it's the right one before you send.

Two it will refuse, and it'll tell you which: a certificate that's still a draft, because there's no finished PDF until it's signed off, and one you've since replaced with a newer version, because that shouldn't be going to a customer at all.

Sending a certificate this way needs the same permission as the **Send** button on the certificate itself. If you can't send certificates on your account, Mucka won't send one on your behalf either.

## Things worth knowing

**Five documents per email, and 15 MB in total.** Past that, mailboxes at the other end start bouncing them, so send a second email rather than one enormous one.

**Documents only attach to email.** Texts can't carry attachments at all, so anything with paperwork goes by email.

**Only people already on your books.** Like every email from Mucka, the recipient has to be a client on your account or someone on your team.