Events

Events are the dates that matter — filing deadlines, renewal dates, board meetings, review milestones. An event attaches to a record and sends reminders ahead of time so nothing slips. To see your events, use the Calendar; this page covers creating and configuring them.

Adding an event to a record

Adding events requires Editor access to the record’s module.

1. Open the record and expand the Calendar section.
2. Click add (+) to create an event.
3. Enter the event name, its date and time, and an optional description.
4. Set a recurrence pattern if it repeats (daily, weekly, monthly, annually, or custom).
5. Add one or more reminders and invite anyone who should be notified.
6. Save.

Reminders

Each event can carry several reminders, each with its own timing — for example, 90, 30, and 7 days before a deadline. Reminders arrive in-app (the notifications bell) and by email, according to each recipient’s preferences. An individual reminder can also repeat — say, daily for the final week.

Invitations

The person who creates an event can invite other users to receive its reminders. Invitees get the same notifications without needing to find the event themselves.

Recurrence vs. event templates

There are two ways to handle repetition:

• A recurring event is one event that repeats on a regular schedule — a monthly board meeting, a weekly check-in.
• An event template is a reusable, pre-filled event definition. Use templates when the same kind of event recurs across different records, or when a single obligation needs several events at different intervals (for example, patent maintenance reminders at 3.5, 7.5, and 11.5 years).

Event templates

Admins manage event templates in Settings → Calendar Event Templates. A template pre-fills the event name, default recipients, reminder schedule, and recurrence, so creating the event is quick and consistent. Templates can also include suggestion triggers that prompt the right people to create an event automatically — for example, a set number of days before a date field, or whenever a record is created or changed.

Events vs. workflows

Events are strictly date-based reminders — they don’t track whether anyone acted. When you need to track who did something and when, use a workflow (a workflow with a due date creates a linked event automatically).

Who can create and see events

• Viewing an event requires access to the record’s module.
• Creating or editing an event requires Editor access to that module. Viewer users can see events but not change them.

On Enterprise plans, organizational unit (OU) scoping limits which records’ events you see.