Currently, Notes must be associated with a specific object (Opportunity, Contact, Company, etc.), making it difficult to capture information that applies across multiple records or that should remain independent of any single object.

We would like the ability to create and manage Notes without requiring an association to an Opportunity, Contact, or Company.

Desired Functionality:

Allow standalone notes that are not tied to any specific record.

Provide an option to remove or change associations without deleting the note.

Allow a single note to be linked to multiple objects while maintaining one source record.

Create a centralized Notes repository where users can search, filter, and organize notes independently.

Allow admins to control whether notes require associations.

Use Case:

In many organizations, users capture meeting notes, project updates, internal discussions, strategy notes, research, and planning documents that do not belong exclusively to a single Opportunity.

For example:

Current Behavior:

❌ Strategic discussion note → Must be attached to Opportunity A

Later:

❌ Opportunity A is closed or deleted → Finding the note becomes difficult

Desired Behavior:

✅ Strategic discussion note exists independently

Optional associations:

Opportunity A

Company B

Contact C

The note remains accessible regardless of changes to associated records.

Benefits:

Improved knowledge management

Better cross-project collaboration

Reduced risk of losing important information when records change

More flexibility for project management and account management workflows

Easier documentation of internal discussions, meeting notes, and strategic planning

Current Behavior:

❌ Notes are dependent on associated objects and can become difficult to locate when relationships change.

Requested Behavior:

✅ Notes can exist independently while optionally being linked to one or more Opportunities, Contacts, Companies, or other CRM records.