Carerealm workflows have two scopes: realm (fires on events anywhere in your realm) and area (fires on events inside one specific area).
Pick the right scope
Use realm scope when… | Use area scope when… |
|---|---|
The trigger event can happen anywhere (e.g. user signs in) | You're automating something specific to one area |
You want a single policy to fire across every {{area}} | A bespoke per-supported-person workflow |
You're a realm admin | You're an {{area}} moderator (not a realm admin) |
Where to build
Realm — Admin → Workflows. Realm admins only.
Area — Open the area, then Workflows in the sidebar. area moderators (and realm admins) can build.
Scope-limited triggers
Some triggers only make sense in realm scope:
admin.user_signed_in/admin.user_signed_out/admin.user_invited— realm only.policy.*— realm only (policies are realm-wide).area.archived,area.access_granted,area.access_revoked— realm only.
Most other triggers (diary.*, forms.*, emar.*, about.*, files.uploaded, webhook.received) work in both scopes.
Heads up — A workflow's scope is fixed at creation. You can't move a realm workflow into an area (or vice versa) without rebuilding it. Pick scope carefully — moving later means duplicate work.