> For the complete documentation index, see [llms.txt](https://compassly.gitbook.io/compassly-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://compassly.gitbook.io/compassly-docs/core-modules/medications/logs-history.md).

# Logs History

**Audience:** Super Admin, Admin, Supervisor, Clinician, Basic\
**Page type:** Overview\
**Status:** Draft\
**Owner:** Compassly Documentation Team\
**Last verified:** 2026-04-03

## Purpose

Use **Logs history** to monitor medication administration activity across clients. This workspace helps staff confirm whether medications were administered, identify missed or not-administered doses, and export records for review or compliance.

## Before you start

Before working in Logs history, confirm the following:

* You are signed in to Compassly.
* You can access **Medications** in the left navigation.
* The medication assignment you need already exists in **Client medications**.
* You understand that **Time group** is set during medication assignment and is not changed from the log-entry workflow.
* Your role includes permission for the action you want to perform.

## How to get there

1. Sign in to Compassly.
2. In the left navigation, select **Medications**.
3. Select **Logs history**.

## What you can do here

Depending on your role, you may be able to:

* view medication logs across clients
* filter logs by date, client, medication, status, or other table columns
* add a new medication log entry
* update log status
* download the current log list

## Log statuses

Compassly currently uses these medication log statuses:

* **Administered** — the medication was successfully given.
* **Not Administered** — the medication was not given and a reason was recorded.
* **Not logged** — the medication is due today, but no log has been entered yet.
* **Missed** — the medication was due, the day has passed, and no log was entered.

## Role differences

* **Super Admin / Admin / Supervisor / Clinician / Basic:** Can view the logs list.
* **Super Admin / Admin / Supervisor / Clinician / Basic:** Can add a new log entry and update status.
* **Super Admin / Admin / Supervisor:** Can download logs history.
* **Super Admin / Admin / Supervisor / Clinician:** Can update status in batch where available.
* **Super Admin / Admin / Supervisor:** Can reset status where available.
* **Basic:** Add-log permissions may be limited for certain medication frequencies based on workspace rules.

## Common tasks

* [View Medication Logs](/compassly-docs/core-modules/medications/logs-history/view-medication-logs.md)
* [Add Medication Log Entry](/compassly-docs/core-modules/medications/logs-history/add-medication-log-entry.md)
* [Download Medication Logs](/compassly-docs/core-modules/medications/logs-history/download-medication-logs.md)

## What happens next

Choose the task that matches what you need to do next:

* review current medication activity
* document an administration outcome
* export logs for offline review

## Related guides

* [Medications Module](/compassly-docs/core-modules/medications.md)
* [View Client Medication List](/compassly-docs/core-modules/medications/client-medications-view-list.md)
* [Assign Medication to a Client](/compassly-docs/core-modules/medications/client-medications-view-list/assign-medication-to-client.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://compassly.gitbook.io/compassly-docs/core-modules/medications/logs-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.