# Run site-specific work after signup

Source: https://zotonic.com/cookbook/1591/run-site-specific-work-after-signup

URI: https://zotonic.com/id/1591

Language: en

Use the current signup notification and make follow-up work repeatable.

Add the following to an active module, merging the include and export declarations:

```erlang
-include_lib("zotonic_core/include/zotonic.hrl").
-export([observe_signup_done/2]).

observe_signup_done(#signup_done{id = Id, is_verified = IsVerified}, _Context) ->
    ?LOG_INFO(#{text => <<"Garden signup completed">>,
                in => mod_garden, id => Id, is_verified => IsVerified}),
    ok.
```

Compile, refresh observer registration and create a practice account. Confirm a log entry with the new resource ID. The current record also has `props` (a map) and `signup_props` (a list); use the header instead of a positional tuple.

`signup_done` does not mean every identity is verified. Gate sensitive provisioning on the required verification event or state, and check it again when deferred work executes. For slow provisioning, queue a task keyed by the user and operation. Check whether the destination account already exists before creating it; retries and repeated notifications must not create duplicate accounts.

Use <a href="/id/1445" class="doc-reference doc-reference-notification"><code>notification#signup_check</code></a> for checks before creation and <a href="/id/1446" class="doc-reference doc-reference-notification"><code>notification#signup_confirm</code></a> for confirmation follow-up. Do not grant editor or administrator groups automatically to public signups.

License: 

Attribution: 

Related resources: https://zotonic.com/api/agent/related/1591?language=en


## API access

- [API help](<https://zotonic.com/api-help>)
- [OpenAPI specification](<https://zotonic.com/openapi.json>)
- [This resource as JSON](<https://zotonic.com/api/agent/resource/1591?language=en>)
