Collaborate with your team: Team notes and simultaneous editing

When several people work on the same site—for instance, you’re reviewing prices while someone else polishes copy or uploads photos—you need a quick place to leave internal updates and a reliable safeguard so nobody accidentally overwrites someone else’s design.

Using the Team notes widget on the Home screen as a shared log

On each project’s main Home (Dashboard) screen, you’ll find the Team notes card, designed as an internal collaborative log:

• Who can write: the Owner as well as any member with the Administrator, Editor, Design, Content, or Finance role can post notes, to-dos, or reminders for the rest of the team (members with the Read-only role can read them, but cannot edit or post).
• Quick keyboard shortcut: type your message in the “Write a note, to-do or jotting for the team…” box and click Post note (or press Cmd + Enter on Mac / Ctrl + Enter on Windows and Linux).
• Author, timestamp, and editing: every note shows who wrote it, when it was posted, and an edited label if it was updated later. You can edit or delete your notes at any time from their action menu.

Alongside the general project notes on Home, remember that inside Contacts each customer profile has its own internal Notes tab where your team can jot down details specific to that person (agreements, preferences, or sales follow-ups).

What happens if two people open the editor at the same time (save conflict detection and how to resolve it without losing work)

véltica’s visual editor saves your work automatically as you design. However, if two team members—or you yourself across two different tabs or computers—open the same project at the same time, one person’s autosave could overwrite what the other person just did.

To prevent work from being silently lost, véltica includes a save conflict detector:

1. How it detects a conflict: every time the editor saves your changes to the server, it checks whether the project was modified by another session since you opened it.
2. What happens when someone else saved before you: instead of blindly overwriting your teammate’s changes, the editor pauses saving and shows a clear notice explaining that the project was updated in another window or by another team member.
3. How to resolve it without losing anything:
   • You can reload the latest version saved by your teammate to see their updated work and continue editing on top of that foundation.
   • If you were drafting a long block of text or tweaking a specific section, you can copy your block before reloading and paste it into the updated version.

Watch out for Settings → Style (Brand) too: the global colors and typefaces you see in the dashboard are the exact same ones used in the editor. If you have the editor open in another browser tab, close it before changing colors or fonts in Settings → Style so that tab’s next autosave doesn’t put the old styles back.