Loading
Decisions & Rules
Your rules decide the routine. Everything else waits for a person, in one inbox, with a clear yes or no.
Give Priya Shah admin access to the CRM
Only a workspace admin or the owner can decide this.
Every decision that needs a person is in one place, next to the work it's about.
Saying no never runs the work again with your answer. The step is skipped or declined, and the record keeps who said no.
Some decisions only an admin can make. Changing a rule takes an admin, or an API key an admin gave that right.
Say when work should run, like “every weekday at 8”. It reads it back in your time zone before anything is saved, and asks instead of guessing.
Say what may run alone and what needs a person.
What your rules don't cover waits in the inbox. What they forbid is refused.
Your yes or no, with who and when, goes on the job's record.
No. An API key decides nothing: a signed-in person says yes or no.
It depends on what was asked: a step is skipped or declined, or the mission ends as cancelled. A no never runs the work again with your answer.
Every day, weekdays, named days, a day of the month, or every few minutes or hours, at a time you give. Words it can't read get a question, not a guess. A schedule shows you its plan and asks before each run.
Your rules handle the routine. You see only what needs you.