Events
Events carry training metadata, so a session can record who ran it and who attended. Attendance feeds the training records used for promotion decisions.1
Create the event
Give it a time and, where it is a training, the training metadata that goes
with it.
2
Announce it
Publish a post so it reaches staff.
3
Record attendance
Attendance recorded against the event becomes part of each attendee’s
training history.
Posts
Posts go to staff channels in the portal and can be categorised so people can filter to what concerns them. Announcements are separate and pin to the top — use those sparingly, for things everyone must see.Discord
When it is enabled, posts can also publish to a Discord audience.Verify the integration after connecting it. A misconfigured webhook fails
quietly: the post still publishes in Crovant and simply never reaches Discord.
Doing this over the API
Both are available programmatically — seeevents and posts in the
API reference. Both are workspace-scoped and
need a workspaceId: