CollaboratorAccountReady

CollaboratorAccountReady fires when a collaborator’s account is fully set up and ready to participate in programs. At this point, the collaborator record has been persisted, any auto-assigned programs have been applied, and the account is in a usable state. This is the event to listen to when you need to trigger welcome emails, provision external accounts, or notify administrators of a new signup.

The event ID is collaborator_account_ready, and its fully qualified class is Siren\Collaborators\Core\Events\CollaboratorAccountReady.

What does this event carry?

The event carries the completed Collaborator model, which provides access to the collaborator’s profile, assigned programs, and account status.

use Siren\Collaborators\Core\Events\CollaboratorAccountReady;

public function handle(Event $event): void
{
    $collaborator = $event->getCollaborator();

    // The collaborator is fully set up at this point.
    // Use this to send welcome emails, sync to external systems,
    // or trigger any post-registration workflows.
}

How does this relate to other registration events?

The registration process fires several events in sequence. CollaboratorSubmissionReceived fires first and allows listeners to modify the submission before the record is created. After the record is persisted, CollaboratorSubmissionComplete fires to signal that the record exists but setup may still be in progress. CollaboratorAccountReady fires last, once everything is finalized.

If you need to modify the registration data, listen to CollaboratorSubmissionReceived. If you need to react to the fully provisioned account, CollaboratorAccountReady is the right choice. The distinction matters because listeners on the earlier events should not assume that programs, permissions, or other post-creation setup steps have finished.

For the full lifecycle of system events and how they connect to the rest of Siren’s architecture, see the System Events overview.