Skip to content

Commit cc1d533

Browse files
committed
Adding in doc about application specific webhooks.
Pulling from FusionAuth/fusionauth-issues#169 comments.
1 parent f0e1b30 commit cc1d533

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

site/docs/v1/tech/events-webhooks/events.adoc

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,24 @@ These are the events that FusionAuth generates that can be optionally consumed b
2727
* <<JWT Refresh>> - when an access token is refreshed using a refresh token
2828
* <<JWT Refresh Token Revoke>> - when a refresh token (or multiple tokens) are revoked
2929

30+
=== Application Scoped Events
31+
32+
There are some events which can be sent for only one or more specified applications.
33+
34+
The events that are considered "application" events and can be scoped to an application based up the Webhook config:
35+
36+
* `user.action`
37+
* `jwt.refresh-token.revoke`
38+
* `jwt.refresh`
39+
* `jwt.public-key.update`
40+
41+
=== Tenant Scoped Events
42+
43+
Any events which are not application scoped events are tenant scoped.
44+
45+
Tenant scoped events can't be limited to a certain application. These either fire for all applications in a tenant or none of them.
46+
47+
All user events are tenant scoped. For example, the `user.delete`, `user.create`, `user.update`, and `user.deactivate` events are all non-application specific.
3048

3149
== User Actions
3250

0 commit comments

Comments
 (0)