> ## Documentation Index
> Fetch the complete documentation index at: https://docs.msportal.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Create and update account notes
> Save an account note or manual QBR entry, maintain commitments, and control optional Autotask writeback.
**Audience:** MSP staff with write access to the company's account notes. Deleting requires the applicable management permission. Company administrator status does not grant access to this internal history.
## Create an account note
Go to **Settings > Companies**, open the company and select **Notes**. Check the company before adding a record.
Open the dialog and let any Autotask settings finish loading before entering a long draft. Choose **Account note** under **Kind**.
Enter a **Title**, check **Date**, then write in **Note**. Title is required and supports up to 250 characters. Date defaults to today for a company note; a backdated note appears according to that date.
Check any optional Autotask settings, then choose **Save**. Wait for the result and confirm the entry in the list. **Cancel** closes the dialog without saving the draft.
The note's dialog Save is separate from company settings and meeting notes. Adding a decision or commitment row only changes the open draft until this Save succeeds. There is no automatic draft recovery after closing the dialog.
If a newly opened dialog resets while connection settings load, wait for those settings to settle before re-entering the draft. Check the final fields and Kind before saving.
## Record a QBR entry by hand
In company **Notes**, choose **Add note**, then **QBR log** under Kind. On a company-linked meeting's **QBR Log** tab, **Add entry** starts a QBR entry linked to that meeting when one does not already exist.
| Field | What to enter |
| ----------------------------- | -------------------------------------------------------------------------------------------------------- |
| **Title** and **Date** | A recognizable review title and the date it records. A meeting entry starts with the meeting title/date. |
| **Discussed** | The subjects and context covered in the review. |
| **Agreed > Add decision** | One decision per row. Remove an unwanted row with its trash control. |
| **Actioned > Add commitment** | What will be done, optional **Owner**, optional **Due date**, and **Done** when already completed. |
Choose **Save** to persist the whole draft. Empty decision rows and commitments without descriptions are omitted. The dialog supports up to 50 decisions and 50 commitments; keep each description concise.
Owner is descriptive text in this editor, not a user selector. Creating a manual commitment here does not assign a portal user, notify its owner, or create a meeting action item. Create or check those working actions separately.
A QBR entry added directly from company settings is not automatically linked to a meeting. A meeting can have one linked QBR entry; if it already exists, edit that entry rather than trying to add a duplicate.
## Edit a note or commitment
Choose **Edit** on a portal entry. Change its title, date, body or QBR fields, then **Save**. An existing entry's Kind is fixed in this dialog. **Cancel** discards the current edits.
On the saved QBR card, ticking or unticking **Done** writes immediately. Inside the edit dialog, the tick is part of the draft and needs Save. A commitment tick also counts as a manual edit, which protects the entry from automatic QBR regeneration.
Manually changing the QBR log does not keep meeting action items or the Autotask copy synchronized. Check each destination separately. AI generation has its own optional action-creation behavior, described in the [QBR overview](/user-guides/calendar/account-notes).
## Choose whether to update Autotask
This workflow supports optional **Autotask Company Note** writeback when the company is linked and note types are available. It does not require Autotask for ordinary portal notes.
1. Choose an **Autotask note type**.
2. Turn on **Push to Autotask when saved**, or **Update the Autotask copy when saved** for an existing linked copy.
3. Save and check the result. The portal save and provider update are separate outcomes.
Autotask also needs a resource associated with your user or a configured integration fallback. Ask an MSP administrator to check that mapping if the sync reports a missing resource.
MSPortal sends the note body as plain text and limits the sent body to 32,000 characters. Rich formatting and content beyond that limit are not included. Updating an existing Autotask copy sends its title, body and note type; changing Date in MSPortal does not retime that existing provider note.
The push checkbox starts off each time the editor opens. Selecting a note type alone does not send the note. Saving a local edit without requesting an update can leave the Autotask copy unchanged even when an earlier **Synced to Autotask** badge remains.
If the push fails, the note can still be saved in MSPortal with **Autotask sync failed**. Resolve the connection, company mapping or note-type problem, then use **Sync to Autotask** when offered. A successful portal save is not proof of provider synchronization.
Imported **From Autotask** notes are read-only here. A portal note pushed to Autotask remains a portal-authored entry that can be edited here; the synchronized duplicate is normally omitted from the combined list.
## Delete a portal note
Choose **Delete** on the exact entry and check the title in **Delete this note?**. **Cancel** keeps it; confirming Delete removes the portal record. There is no undo control in this panel.
Deleting does not remove a copy already pushed to Autotask and does not remove separate meeting action items. A retained Autotask source copy may appear in the combined history after its portal counterpart is gone. Do not use deletion as a way to erase every copy of a review.
## Frequently asked questions
Open Settings > Companies, select the company, choose Notes and Add note, then save the Account note dialog.
No. Portal account notes and manual QBR entries can stay in MSPortal.
No. Dialog changes need Save. The Done checkbox on an already-saved QBR card is a separate immediate write.
No. It closes without saving the current edits. Keep a separate draft if you need it later.
Connection settings can arrive after the dialog opens. Wait for those controls to finish loading before re-entering the draft and check Kind and all fields before saving.
Choose QBR log under Kind in the company Notes dialog, or use Add entry on a company-linked meeting's QBR Log tab, then fill Discussed, Agreed and Actioned and save.
No. Owner is descriptive text. Create or check any portal assignment, meeting action or notification separately.
No. Add it from the meeting's QBR Log tab to create that link when no entry exists.
Kind is not editable for an existing entry in this dialog. Create the appropriate new entry if needed.
No. The tick updates the log's commitment only. Check the separate action item and any provider copy.
No. Enable Push to Autotask when saved or Update the Autotask copy when saved, then save deliberately.
The editor's update checkbox starts off each time it opens. Enable it when the provider copy should receive this save.
The portal note can already be saved. Check it in the list and retry the provider sync after resolving the reported problem.
MSPortal sends plain text and at most 32,000 body characters. Rich formatting and content beyond that limit are not included.
No. Updating an existing copy sends title, body and note type. It does not retime the existing provider note.
The push needs a resource linked to your user or an integration fallback. Ask an MSP administrator to check those mappings, then retry the sync.
No. It removes the portal record, not a previously pushed Autotask copy or separate meeting action items. Confirm the correct entry before deleting.
## Related guides
* [Find and read account notes](/user-guides/calendar/read-account-notes)
* [Account Notes and QBR Log](/user-guides/calendar/account-notes)
* [Draft and send a meeting summary](/user-guides/calendar/send-meeting-summary)