Whose rights a flow has
A flow that works on the CRM acts as the person who published its current version, not as the workspace account.- A step creates or changes a record, a task, a note or a list entry only as far as that person’s CRM roles allow. The roles are read again for every step, so a right taken away stops the next run.
- A trigger starts a flow only for records that person may read, and its data holds only the fields their roles show.
- Notes the flow adds carry that person as author. A private note stays private to them.
Triggers
A flow never starts from a change one of its own runs made. A change by another flow does start it, up to the usual depth of chained runs.
A deal that moves out of a won or lost stage starts only Deal stage changed. The five-second wait for CRM record changed is kept in memory, so a restart of Collabase inside it drops that event.
Actions
Fields, contact points, links and cells are JSON text, for example
{"industry": "Retail"}. A wrong shape fails the step and names the input, never the value. Creating a task twice in the same step of the same run makes one task. Adding a record to a list twice leaves one entry.
Each action goes through the same service as the CRM screens, so audit, the timeline and notices to assignees work as for a person. The audit log shows the person and that the change came from a flow.
The CRM has no trigger or action for roles, the model, mailboxes or calendars. Rights stay manual work.