Record history and link a task
Keep text, dates and evidence links; CRM does not send messages.
How to use it
- In the contact record, add a note, inbound or outbound interaction. Include context, time and an optional URL or original message ID.
- An outbound event records a past interaction. Importing historical messages does not remove a block or authorize new contact. There is no automatic email fetch, mailing or publication.
- In shared CRM, link an event only to an existing task in the same team and project. Personal CRM accepts tasks you can access. Access is checked before saving; the link opens the original task and does not create a new one.
Advice and practical context
Log events with enough context
In a contact history, add notes and distinguish inbound from outbound interactions. Briefly record what happened, when it happened, and where the material can be checked; add a URL when useful. An outbound entry is a manual log, not an email, message, or publication sent by MARPLA. Do not treat it as proof of delivery: record only facts you can verify.
System events appear when a contact or collaboration is created or changed and when its stage moves. They help reconstruct sequence, but do not replace useful notes about agreed terms. For a shared project, link a CRM event to a task in a team or project you can access. Access to the selected task is checked before saving, and the link opens the original task.
Link a task without copying private context
Choose an existing task and link it to a contact, optionally attaching it to a particular opportunity. CRM adds a reference to the original kanban item in the history; the task stays in its project under that project’s permissions. A new task is not created automatically, so create one in the usual team kanban first if no suitable task exists.
Private contacts and notes are not copied into the shared task. Confirm the project and task title before linking, especially when several games have similar names. Open the history link after saving to check that it points to the intended item. If access is revoked or the task moves, use the current project list and update the link through the available actions.
Technical detailsCalculations, permissions and behavior
History and tasks
A contact history can contain a manually logged note, inbound or outbound interaction, URL and time. An outbound entry records only what you enter; CRM does not send messages or publish content. System history separately records data and stage changes.
You can link an event to an existing project task you can access; access is checked before saving, and the link opens the original task. Shared CRM accepts only tasks from the same team and project; personal CRM accepts tasks you can currently access. Validation uses current access, not a previously saved role.
CRM does not create a second task or duplicate the kanban board.