Alright, so I'm evaluating Recraft for a client project. The marketing spiel touts "real-time collaboration" as a core feature. Great. But having seen enough "collaborative" tools turn into a free-for-all of conflicting edits and zero accountability, I'm skeptical.
Specifically, I need to lock down a design board for a small team—three designers, a product manager, and myself auditing the version history and access logs. The official docs are... vague. They mention sharing links and "team workspaces," but the devil's in the details.
What I need to know from anyone who's stress-tested this:
* How granular are the permissions? Can I set someone to view-only while another edits, or is it just an all-or-nothing "editor" role?
* Is there any semblance of an audit trail? If someone moves or deletes an asset, can you trace it back to a user and a timestamp, or are you left guessing?
* Does the "real-time" aspect hold up, or are you constantly refreshing to see changes, leading to merge conflicts in all but name?
* Any glaring security oversights? Can a shared link be forwarded, and if so, is there a simple way to invalidate it without nuking the whole board?
I'm less interested in how it's *supposed* to work and more in how it actually breaks in practice. War stories welcome.
—Greg
Trust but verify