Attachments

Attachments allow operators to upload files to steps during execution. These files serve as evidence, supporting documentation, or output artifacts that are permanently associated with the step. Attachments are particularly important for steps that have the Requires Evidence setting enabled — those steps cannot be completed until at least one file has been uploaded.

---

Supported File Types

RAMP accepts the following file types for upload:

Category	Extensions
Images	.jpg, .jpeg, .png, .gif
Documents	.pdf, .doc, .docx, .txt
Spreadsheets	.xlsx, .xls, .csv
Archives	.zip

Note

Files outside the supported types will be rejected at upload time. If you need to attach a file type not in this list, consider packaging it inside a .zip archive.

---

File Size Limits

The maximum file size per upload is 50 MB. Files exceeding this limit will be rejected with an error message.

Tip

For very large files (e.g., video recordings, database dumps), consider uploading them to an external storage location and referencing the link in a step comment or execution note instead.

---

Uploading Attachments

1. Select the step you want to attach a file to in the step structure panel
2. Navigate to the Attachments area in the notes panel (right side of the execution view)
3. Select the target step from the step dropdown (if not already selected)
4. Click Upload or drag and drop files directly into the upload area
5. The file uploads immediately and appears in the attachment list

Each uploaded attachment records the following metadata:

Field	Description
File name	Original name of the uploaded file
Content type	MIME type of the file (e.g., image/png, application/pdf)
File size	Size in bytes
Uploaded by	The user who uploaded the file
Uploaded at	Timestamp of the upload
Description	Optional description text

---

Viewing and Downloading Attachments

Inline Preview

Images (.jpg, .jpeg, .png, .gif) and PDF files support inline preview directly in the execution view. Click on the attachment thumbnail to expand the preview without leaving the page.

Download

All attachments can be downloaded with their original filename. Click the Download button next to any attachment to save it locally.

---

Grouped Display

When viewing attachments at the instance level, files are organized by step in an accordion layout:

• Each step that has attachments appears as an expandable section
• A badge next to each step name shows the attachment count
• Expand a section to see all files for that step
• Collapse sections to keep the view manageable when many steps have attachments

This grouped display makes it easy to locate evidence for a specific step during review or audit.

---

Deleting Attachments

Attachments can be deleted by users with the appropriate permissions.

1. Locate the attachment in the attachments list
2. Click the Delete button (trash icon) next to the attachment
3. Confirm the deletion in the dialog
4. The attachment is permanently removed

Caution

Deleting an attachment is permanent. All attachment uploads and deletions are recorded in the audit trail. If a step has the Requires Evidence setting and you delete the only attachment, the step will return to a state where it cannot be completed until a new attachment is uploaded.

---

Requires Evidence Enforcement

When a step has the Requires Evidence setting enabled (indicated by a red chip with an attachment icon), the following enforcement applies:

• The Complete button is disabled until at least one attachment has been uploaded to the step
• The red “Requires evidence” chip serves as a visual reminder
• Even after uploading, the attachment remains associated with the step — it must not be deleted if the step has already been completed

Tip

If evidence was submitted through an external channel (email, ticket system, etc.) and cannot be uploaded to RAMP, the Instance Head or Deputy Head can use Force Complete to bypass the evidence requirement. A reason explaining the external evidence location must be provided. See Force Actions for details.

---

Permissions

Action	Instance Head	Deputy Head	Executor	Editor	Observer
Upload attachments	Yes	Yes	Yes	Yes	No
View/download attachments	Yes	Yes	Yes	Yes	Yes
Delete attachments	Yes	Yes	No	No	No

---

Audit Trail

All attachment operations are logged in the instance audit trail:

• Upload: Records the filename, uploader, timestamp, and target step
• Deletion: Records who deleted the file, when, and from which step

These audit entries are visible in the instance’s History tab and can be filtered by action type.

---

Best Practices

Document with Screenshots

Take screenshots of key system states, configuration screens, or terminal output during step execution. These serve as valuable evidence during post-execution review and compliance audits.

Name Files Descriptively

Use clear, descriptive filenames (e.g., step3-db-migration-output.txt rather than output.txt). This makes it easier to identify files during review.

Upload Promptly

Upload evidence as soon as the relevant work is completed. Waiting until the end of execution increases the risk of missing files or uploading evidence to the wrong step.

Use Descriptions

When uploading files, add a brief description to provide context. For example: “Database backup verification log showing successful checksum validation.”

---

Related topics

Notes & Comments Document observations and decisions with execution notes and comments

Step Actions Execute steps with granular completion statuses, skip, pause, resume, and manage execution modes