> ## Documentation Index
> Fetch the complete documentation index at: https://docs.crovant.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Events and posts

> Keep staff informed with schedules and updates.

Events and posts are how a workspace communicates: events for anything
scheduled, posts for announcements.

## 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.

<Steps>
  <Step title="Create the event">
    Give it a time and, where it is a training, the training metadata that goes
    with it.
  </Step>

  <Step title="Announce it">
    Publish a post so it reaches staff.
  </Step>

  <Step title="Record attendance">
    Attendance recorded against the event becomes part of each attendee's
    training history.
  </Step>
</Steps>

## 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

<Warning>
  The Discord bot is currently disabled. Posts publish in Crovant as normal, but
  nothing reaches Discord until it is turned back on, and existing integration
  settings are left untouched in the meantime.
</Warning>

When it is enabled, posts can also publish to a Discord audience.

<Note>
  Verify the integration after connecting it. A misconfigured webhook fails
  quietly: the post still publishes in Crovant and simply never reaches Discord.
</Note>

## Doing this over the API

Both are available programmatically — see `events` and `posts` in the
[API reference](/api-reference/introduction). Both are workspace-scoped and
need a `workspaceId`:

```bash theme={null}
curl "https://crovant.com/api/events?workspaceId=YOUR_WORKSPACE_ID" \
  -H "Authorization: Bearer YOUR_API_KEY"
```