Notes

What Notes Are For

Notes give your team a private workspace for recording context that should stay inside FSRevs. Use them for customer conversations, follow-up context, internal decisions, or information another team member may need later.

When something needs an assignee, progress status, or due date, use Tasks, Issues & Reminders (Beta) instead.

Open Notes under Team Workspace to see every Note you are allowed to access. You can also select Quick Note from a Customer card or workspace to begin with that Customer already attached.

Create a Note

Select New Note, then choose whether to attach it to a Customer. A Note can be:

Attached to a Customer — Available from that Customer’s Notes tab as well as the main Notes directory.
Unattached — Kept in the shared Notes directory without a Customer relationship.

Choose Company-wide or an available location. Creating a Note requires the appropriate Data access for its scope; company-wide Notes require global Data access. A Customer attachment also requires permission to manage that Customer’s Notes.

In the editor you can add:

An optional title and the Note body
Urgency and categories
A pinned flag for important Notes
An audience and scope
Comments after the Note has first been saved

Use Save Note to publish the current editor contents or Save & Close to publish and return to the Notes directory. Only a saved version changes the shared Note that other permitted team members see.

The person who first publishes the Note becomes its owner and automatically follows it. The owner remains identified on the Note and in the directory.

Find Notes

Search the Notes directory by title or body. Filters can narrow it to:

Notes you own
Notes you follow
Notes with one of your unpublished drafts
Customer-attached or unattached Notes
Team, Private, or Managers Only visibility
Company-wide or location-specific scope
Categories
Deleted Notes

Cards identify the owner, audience, scope, categories, urgency, Customer attachment, comment count, pinned state, and last activity. The directory and every count are permission-aware.

Audience and Scope

Audience and location scope work together:

Audience	Who can see the Note
Team	Team members who can access the selected company-wide or location scope
Private	The Note’s owner and eligible managers in that scope
Managers Only	Eligible managers in that scope

Your role and location access still apply. Being given a link does not grant access to a Note or its attached Customer.

Private does not mean hidden from every manager. Use the audience table when deciding where to record sensitive internal information. Notes stay in the team workspace and are not sent to the attached Customer.

Audience changes save immediately without publishing text that is still only in your editor. If the new audience or scope removes somebody’s access, that person is also removed as a follower. Review the warning before confirming a change that affects collaborators.

Follow and Discuss a Note

After the first save, select Follow when you want in-app updates. Followers receive an in-app notification when another person publishes changes or adds a comment. The person making the change is not notified about their own action.

Comments appear in the Note’s activity timeline alongside important system events. Use them for discussion about the saved Note; changing the editor text still requires Save Note before it becomes shared content.

Notifications and links are checked against current access when delivered. A person who can no longer view the Note does not receive its content through a notification.

Draft Backup and Saving

FSRevs quietly backs up editor changes before you publish them. When possible, an unpublished draft is saved to your account so it can be recovered on another device. A browser-only recovery copy provides an additional fallback on the current device.

Draft backup is not the same as Save Note:

Other people do not see your unpublished draft.
A draft does not create a published Note version or audit entry.
The editor reports whether recovery is available and warns when a backup could not be stored.
Browser recovery copies are temporary and should be removed after using a shared device.

If FSRevs finds newer unpublished work when the editor opens, it displays Unsaved changes found so you can review the recovery copy instead of silently replacing either version.

Review History and Recover Content

Select History to review:

Changes not yet saved — Account-backed or browser-only recovery drafts
Earlier saved versions — Previously published versions of the Note

Review an item to compare it with the current editor. Load this draft or Load this version copies the selected content into the editor; it does not publish anything immediately. Check the restored content, then select Save Note when it should become the shared version.

You can also remove an unwanted recovery draft or discard your current unpublished changes without deleting earlier recovery copies.

Concurrent Editing

If somebody else saves the same Note while you are editing, FSRevs compares both sets of changes. Independent changes can be combined automatically. If both people changed the same field, the conflict dialog shows the saved and local choices side by side.

Choose the value to keep for each conflicting field, then save the resolved Note. You can instead save your work as a new Note or reload the latest saved version. Nothing is selected or discarded automatically in a conflict.

Notes in a Customer Workspace

A Customer workspace has a Notes tab for every attached Note you can access. Its Overview shows up to three recent Team Notes, with pinned Notes first. Private and Managers Only Notes stay out of that Overview even when you personally have access; open the Notes tab for the complete permission-aware list.

Use Quick Note from the Customer header or directory card to record an interaction without searching for the Customer again.

Delete, Restore, and Audit

Deleting a Note moves it to deleted records so an authorized user can restore it. Permanent deletion is restricted more tightly and cannot be undone.

Published versions and important metadata, category, follower, audience, deletion, and restoration changes are audited. Draft backups are intentionally excluded. Access to the Note itself does not automatically include access to its detailed audit page.

See Audit Trail for more information.

Troubleshooting

Problem	What to check
A teammate cannot see the Note	Confirm that it was saved, then check audience, scope, and access to any attached Customer.
You see your edits but a teammate sees older text	Draft backups are unpublished. Select Save Note to share editor changes.
A Note is missing from a Customer’s Overview	Open the Notes tab. Overview shows up to three Team Notes, with pinned Notes first, and excludes Private or Managers Only Notes.
Another editor saved first	Resolve the displayed conflict, review both versions, and save the result.
You expected a notification	Follow the saved Note and check the in-app notification center. Your own changes do not notify you.