Tenant entitlement
Automation runs only for workspaces entitled to it.
Explore a P5 concept where conversation events become CRM tasks only after identity, entitlement and admin approval — with every step recorded.
P5 concept · Illustrative demo · Availability not confirmed
Concept state: waiting for admin review. No task is created.
P5 concept. No SQL 016, production worker, Meta channel or live CRM task execution. Buttons change local page state only; no API calls or automated messages.
Automation runs only for workspaces entitled to it.
An admin reviews and approves each workflow.
Idempotent jobs are a requirement so retries don't repeat work.
Every decision and outcome is recorded for review.
STEP 01
An event arrives and identity is checked.
STEP 02
The tenant's plan and permissions are confirmed.
STEP 03
A person approves, or suspends, the workflow.
STEP 04
An idempotent job creates a CRM task, logged in history.
Human review checkpoint
Nothing here is live: no production worker, Meta channel or CRM task execution exists for this page. Automation never sends messages on its own.
Proposed safeguards. Compliance, security and retention details need confirmation before any launch.
No workflow runs without admin approval.
Duplicate prevention is a design requirement, not a live claim.
Admins can pause a workflow; the history is kept.
What to expect from these channel concepts, and what still needs to be confirmed.
See how Workflow Automation fits alongside the other REBNAL solution concepts.