Event Management Applet

Keeps a tenant’s calendars and the events on them, with members on a calendar, participants on an event and companies linked to an event: master data plus links, no journal, no posting status, no stock. The Event Expense Report and an event’s Expenses tab are not an expense store — a cost reaches an event only when a staff claim line is tagged with it on the claims side, and reading those screens needs the claim-report permission, not a calendar one. Creating or changing an event notifies nobody.

Overview

The Event Management Applet keeps a tenant’s calendars and the events on them, and the links that put members on a calendar, participants on an event, and companies against an event. It shows the same data three ways — a month/week calendar view, a flat event listing, and a calendar listing.

Its fourth screen, the Event Expense Report, is not an expense store. Costs reach an event because a staff claim line can be tagged with an event, and the report is served by the claim reports. The applet reads that data; it never writes a claim.

It is master data plus links: no journal, no posting status, no stock.

Where it fits

Direction	What	Why
Before	Calendars, created in this applet	An event belongs to a calendar. The applet settings hold the calendar an event defaults to.
Before	Employee	The event’s PIC (person in charge) is an employee record — the one whose e-mail matches the login of whoever creates the event. Participants and calendar members are not: they are people with a login to your tenant, found by their login e-mail.
Before	Organization / Entity	The event’s Company is required, and the Company Linking tab attaches further entities to an event.
Alongside	The audit/assurance/tax claims module	An expense appears against an event because a claim line is tagged with the event GUID. Reading the report needs claim-report permission.
Adjacent	Engagement Applet	The other applet in the same audit/assurance/tax family; both feed the claims reporting.

Screens and menus

Four sidebar entries, all under the applet’s main router:

Menu	Route	What it is
Event Calender	`event-calender`	The scheduler view. Clicking a slot pre-fills the start date of a new event.
Event Listing	`events`	A grid of events: Title, Event Code, Event Type, PIC, Event Venue, Description, Status, Date From, Date To, Updated Date.
Calendar Listing	`calendars`	A grid of calendars: Calendar Name, Description, Time Zone, Creation Date, Modification Date, Status. Removed from the menu when `HIDE_CALENDAR_LISTING_MENU` is on.
Event Expense Report	`event-expense-report`	Claim lines tagged to events, across all events: Event Title, Event PIC Name, Employee Name, Claim ID, Claim Item, Claim Status, Claim Amount, with a statistics panel.

The applet name shown in the layout header is Events Management; the registry name is Event Management Applet.

Event Edit

Tab	Shown when	Contents
Details	always	The event record — see Fields — plus the Required Recurring box and a Delete button. Delete asks Delete recurring event on every event, repeating or not, and makes you choose how far it reaches — see Recurring under Fields before you pick.
Company Linking (label follows the relabel setting)	`HIDE_ENTITY_LINKING_TAB` is off	Companies/entities attached to the event, with add and edit panels.
Agenda	always	File attachments: File Name, Size, Uploaded Date, Uploaded By. Despite the tab name it is an attachment list, not a structured agenda.
Events Participant	always	The people taking part. The picker offers the members of the event’s calendar — logins on your tenant, not employee records — so someone who is not a member of that calendar cannot be added until they are made one (Calendar Edit → Members). Participant Name and Email are looked up from each person’s login every time the tab opens. Adding or removing a participant re-saves the event, which is why it jumps to the top of Event Listing. Nobody is told they were added: the organiser sends the invitation from their own mail or calendar, and checks this tab against the replies.
Expenses	always	The single-event version of the expense report: Event Title, Employee Name, Claim ID, Claim Item, Claim Status, Claim Amount. Read-only.

Calendar Edit

Two tabs: Main (name, time zone, description) and Members (Member Name, Email, Status), with an Add Member panel.

Settings

The settings menu (settingItems) lists three entries: Field Settings, Default Selection and Events Calendar Permission — the last of which opens the calendar-member listing, so “permission” here means who is a member of which calendar.

settings/feature-visibility, settings/applet-log (an audit-trail listing and viewer) and the team permission listing are routed with no menu entry and can be reached by URL only. Webhook (listed as Triggers), Applet Access, the permission wizard and the permission-set, user and role permission listings are linked from the left-hand list of the Settings screen, which the shared settings shell draws. The settings path with no child redirects to feature-visibility.

No product screenshots exist for this applet. The only image in the repository was an AI-generated marketing infographic and it has been removed.

Configuration

Before you can use it

Prerequisite	Where	Why
At least one calendar	Calendar Listing, in this applet	An event has to sit on a calendar; the settings screen also wants one as the default.
Employees, and tenant logins	Employee; your tenant’s users	The PIC is an employee record. Calendar members and participants are logins on the tenant, found by e-mail, so the people you want to invite need a login first.
A company	Organization	Company is `Validators.required` on Event Create.
Claim-report permission, for the Expenses screens	The claims side of the audit/assurance/tax module	Both expense reports are claim reports, which require `TNT_AAT_CLAIM_REPORT_OWNER` / `_ADMIN` / `_CREATE`. Calendar permissions do not open them.

Applet settings

Settings live on the applet’s own settings screen, and it is a working one: nine controls, saved for the whole applet.

It is called Field Settings in the menu and has three tabs. Anyone who can open Applet Settings can change these, and they apply to the whole tenant.

Setting	Tab	What it controls	Default	Effect when on
`HIDE_EVENT_CODE`	Main	The Event Code field on Event Create and Event Edit, and the Event Code column on the listing	unset (off)	The field and the column disappear.
`HIDE_EVENT_TYPE`	Main	The Event Type field on Event Create and Event Edit, and the Event Type column on the listing	unset (off)	Same. New events then carry whatever Event Type was already set.
`RELABEL_COMPANY_TO_ENTITY`	Main	The word used for the company	unset (off)	Reads Entity instead of Company on Event Create, Event Edit, the event listing, the tab label of Company Linking, and both expense reports. Label only — the field still writes the company GUID.
`RELABEL_BRANCH_TO_JOB_GROUP`	Main	The word used for the branch	unset (off)	Reads Job Group instead of Branch on Event Edit and both expense reports.
`HIDE_ENTITY_LINKING_TAB`	Entity Linking	The Company Linking tab on Event Edit	unset (off)	The tab disappears. Existing links are kept, just not visible.
`HIDE_CALENDAR_LISTING_MENU`	Calendar Menu	The Calendar Listing sidebar entry	unset (off)	The page still opens if its address is typed.
`selectedCalendar`	Calendar Menu	The calendar new events default to	unset	Read by Event Create and by the calendar-member screens. The drop-down lists calendars most recently changed first.

Two controls on this screen are not read anywhere:

Hide Default Select Calendar is rendered and saved. It hides the Default Select Calendar drop-down on the settings screen itself, and nothing else in the applet reads it — turning it on does not stop selectedCalendar being applied.
Enable Audit Trail is rendered and saved, and changes nothing. The audit-trail screen is not switched on or off by it (and has no menu entry either).

Feature visibility and permissions

The applet has no HIDE_*/SHOW_* client-side permission pairing. Server-side:

Area	Permission codes
Calendars (`calendar-hdrs`)	`TNT_API_CMS_CALENDAR_` `OWNER` / `ADMIN` / `CREATE` / `UPDATE` / `DELETE` / `READ`
Events (`calendar-events`)	`TNT_API_CMS_CALENDAR_` `OWNER` / `ADMIN` / `DELETE` / `READ`
Calendar members, participant links, post links, event link queues	the same `TNT_API_CMS_CALENDAR_*` family
Both expense reports	`TNT_AAT_CLAIM_REPORT_` `OWNER` / `ADMIN` / `CREATE`

The expense screens are gated by claim permissions, not calendar permissions. Someone who can create, edit and delete events will still get nothing from the Expenses tab or the Event Expense Report unless they also hold TNT_AAT_CLAIM_REPORT_CREATE (or OWNER/ADMIN). Note that the read is gated by a _CREATE code — the report endpoints are POSTs.

Fields

Event — Create and Details

Details holds PIC, Company, Event Name (the listing calls it Title), Event Code, Event Type, Event Venue, Start Date, End Date, Status, All Day, Description, Event Color and the Required Recurring box. Event Name, Company, Start Date and Status must be filled before SAVE lights up. On Create New Event, SAVE also stays grey until at least one file has been added on the Agenda tab, and removing that file afterwards does not grey it again. That is read from the code, not tried: fill every required field on one new event, look at SAVE, then add a file on Agenda and look again. If a file is demanded, attach the invitation or the running order you would have sent anyway.

There is no calendar box. Every new event goes onto the calendar named in Field Settings → Calendar Menu → Default Select Calendar, and Edit keeps whatever calendar the event already has, so nothing on this screen moves an event to another calendar. Whoever owns the settings sets the default calendar before anyone creates events; if it is empty, new events are saved with no calendar (read from the code, not tried). Nothing checks for a second event with the same name, on either side.

Field	Required	What the screen does not tell you
PIC	Filled for you	Create fills it with the employee whose e-mail matches your login, and neither Create nor Edit offers a way to change it — the box is read-only and no picker opens from it (read from the code, not tried: open one event you did not create and try to change its PIC). So the PIC is whoever raised the event. If someone else is in charge, have that person create the event, or name them in Description. If your login e-mail matches no employee, the box stays empty, and Edit then refuses to save that event because it wants a PIC.
Company (Entity when relabelled)	Yes on Create	The list is every company on the tenant, shown as name \|\| code. The company is what Event Listing’s Advanced Search filters on, and the listing looks its name up each time it loads.
Event Code	No	Hidden by `HIDE_EVENT_CODE`.
Event Type	No	Hidden by `HIDE_EVENT_TYPE`. A two-value list; there is no per-calendar privacy model behind it.
Start Date	Yes	Pre-filled when the event is started from a slot in the calendar view. On Edit, changing Start Date empties End Date, and the End Date picker then offers nothing earlier than one day after the new start (read from the code, not tried). A same-day event that is moved therefore comes back with no end, or with an end a day later than intended: after moving a start, set End Date again and check Date To in Event Listing.
End Date	No	On Create nothing checks it against Start Date, on the screen or on the server, so an event can be saved ending before it starts. On Edit the picker will not offer a date before the start. Left empty, the event is saved with no end. The person who creates the event is the check: after saving, compare Date From and Date To in Event Listing.
Status	Yes	ACTIVE or INACTIVE, and it starts empty, so SAVE waits until one is picked. INACTIVE is a label: Event Listing still shows the event and filters nothing by it, and it does not delete, hide or cancel the event or tell anyone. To call an event off, tell the participants yourself, then set INACTIVE or delete it.
All Day	No	Hides the time pickers and saves the start as the first second of the start day and the end as the last second of the end day. Tick it with End Date empty and the event is saved with no end (read from the code, not tried).
Event Color	No	Defaults to `#b7c08b` and is saved with the event, but the calendar view does not use it: it paints each event a random colour chosen per event name, the same for every event with that name and different on the next visit. The colour you chose is only seen again in Event Edit.
Recurring	No	The box reads Required Recurring. Save on Edit and Delete both ask which occurrences to act on — This event, This and following events, All events — on every event, including one that does not repeat. On an event that does not repeat, always choose This event. Read from the code, not tried: on a one-off event, This and following events deletes every event on the tenant that starts at or after it, and All events deletes events on every calendar — each up to 500 at a time. Deletion is outright, with no deleted status to restore from. Do not try this on live data. If it has happened, nothing in this applet brings the events back; they are re-entered by hand from the organisers’ own mail and calendars.

Delete refuses an event that a staff claim line is tagged with, with Event is already in used, cannot be deleted!; untag the claim line on the claims side first.

Calendar — Create and Main

A calendar has a Calendar Name (required), a Time Zone and a Description. Nothing checks that two calendars have different names, and the Default Select Calendar drop-down shows names only, so whoever creates calendars looks at Calendar Listing first and gives each a name nobody will confuse.

Field	Required	What the screen does not tell you
Time Zone	Yes	Create and Update stay grey without it. It is stored as a GMT offset and shown in Calendar Listing, but nothing in this applet moves an event’s times by it: an event keeps the times typed on the screen of whoever entered it. For a calendar used across time zones, agree whose local time events are entered in and put it in the calendar’s Description.

Calendar members and event participants

Calendar members (Settings → Events Calendar Permission, or Calendar Edit → Members) carry Member Name, Email and Status. They are logins on your tenant, found by their login e-mail, not employee records: Add Member checks the e-mail, and for an address with no BigLedger login it offers to send a registration invitation instead. Event participants carry Participant Name and Email and are picked from the members of the event’s calendar, so the order is: give the person a login, make them a member of the calendar, then add them to the event.

Event expense report rows

Read-only, from the claim reports: Event Title, Event PIC Name, Employee Name, Claim ID, Claim Item, Claim Status, Claim Amount. The single-event version inside Event Edit drops the Event Title and PIC columns.

Lifecycle and effects

Posting proof

Aspect	Value
Document	None. Calendars and events are master data, not documents.
Journal	None. The applet posts no journal and creates no claim.
Stock	None.
What VOID reverses	There is no VOID and no posting status. Calendars and events carry a status of ACTIVE or INACTIVE only. An event is removed with Delete, which asks which occurrences to remove (see Recurring under Fields) and removes them outright — nothing is kept to restore.

What it writes

Calendars, calendar members (from Calendar Edit → Members and from Settings → Events Calendar Permission — the same list), events, and each event’s companies, participants and attachments. Event Edit → Expenses and the Event Expense Report write nothing — both only read claims.

How an expense reaches an event

A staff claim line can carry the event it was spent on. A claim line tagged with an event is what makes that cost appear on the event — on the one event’s Expenses tab, on the multi-event report, and in the dashboard panel’s totals.

Nothing in this applet tags a claim line. The tagging happens on the claim side; this applet only reports on it.

The notification queue

Creating or changing an event sends no e-mail, SMS or notification. An event notification queue exists, but nothing sends from it.

Related applets

Employee — the PIC is an employee record; the participants and calendar members are logins on the tenant, not employees.
Organization and Entity — the required Company on an event, and the entities attached on the Company Linking tab.
Engagement Applet — the other applet in the audit/assurance/tax family; both surface claim data rather than owning it.
CP Commerce Admin — its Activities group also covers facilities, activities, calendars and scheduling, for the storefront rather than the back office.

Troubleshooting

Symptom	Cause	Fix
The Expenses tab and the Event Expense Report are empty or refuse to load, though events are visible	Both are claim reports, gated by `TNT_AAT_CLAIM_REPORT_OWNER` / `_ADMIN` / `_CREATE`. Calendar permissions do not cover them.	Grant the claim-report permission. Note that reading the reports needs the `_CREATE` code.
An event’s costs never appear on the Expenses tab	An expense reaches an event only when a claim line is saved with `calendar_event_hdr_guid` set. Nothing in this applet tags a claim.	Tag the claim line with the event on the claims side.
Calendar Listing has disappeared from the sidebar	`HIDE_CALENDAR_LISTING_MENU` is on.	Turn it off in Field Settings. The page still opens if its address is typed.
Turning on Hide Default Select Calendar does not stop new events defaulting to a calendar	The switch only hides the drop-down on the settings screen; nothing else reads it, and `selectedCalendar` keeps being applied by Event Create.	Clear `selectedCalendar` instead.
Enable Audit Trail does nothing	The key is saved and changes nothing; the audit-trail screen is not switched by it.	The audit-trail screen is reachable at `settings/applet-log`, which has no menu entry — navigate by URL.
The settings gear opens on Feature Visibility, a screen with no menu entry	`settings` with no child redirects to `feature-visibility`, which is not in `settingItems`.	Pick Field Settings, Default Selection or Events Calendar Permission from the menu.
An event was saved with an End Date before its Start Date	Create New Event does not compare the two dates, and neither does the server. Event Edit’s picker does refuse a date before the start.	Open the event and set End Date again.
SAVE stays grey on Create New Event although every field is filled	Status must be picked, and SAVE also waits for at least one file on the Agenda tab (read from the code, not tried).	Pick a Status; add a file on Agenda.
An event moved to a new start now has no end, or ends a day late	On Edit, changing Start Date empties End Date, and the picker then starts one day after the new start.	Set End Date again after moving the start, and check Date To in Event Listing.
New events land on the wrong calendar, or on none	Create has no calendar box; it uses Default Select Calendar in Field Settings.	Set the default calendar in Field Settings before creating events. An event cannot be moved to another calendar in this applet.
The calendar view shows an event in a colour nobody chose	The view picks a random colour per event name and ignores the saved Event Color.	Nothing to fix on the event; rely on the name, not the colour.
Nobody was notified that an event was created or changed	Nothing sends event notifications. There is no e-mail, SMS or webhook on an event.	Announce events out of band.
“Events Calendar Permission” does not grant permissions	The settings entry of that name opens the calendar member listing — membership of a calendar, not a permission set.	Server-side access is the `TNT_API_CMS_CALENDAR_*` family, granted through the permission screens (routed but unlinked) or the Tenant Admin applet.