Events
Events is a personal diary. A user records something that is happening on a date - a board meeting, a factory audit, a training day - with a time, a colour and an icon so it stands out. It belongs to the person who wrote it, not to a department.
What it is for
Not everything on somebody's calendar is a company record. An audit visit, a supplier arriving, a managing director out of the country for a week - these are things a user wants to see on a date without raising a leave request or a task about it.
Events holds those. An event carries a title, a start and an end, an icon and a colour, and a short description. The colour is the point: a user with twenty things in a month wants the audit in red and the training in green.
An event is written against a user. It is a personal note, not an instruction to anybody. If somebody has to do something, that is a Task or a Create Activity, both of which are assigned and chased. An event is not.
Every field, in plain words
Events are added from the Add Event box on the screen.
| Field | What it means | What to put in it | Notes |
|---|---|---|---|
| Name | The user the event belongs to. | The user who is making the entry | Required. |
| Title | What the event is. | Customs audit, bonded warehouse | |
| Icon | A small picture shown with the event. | A flag for an audit, a people icon for a meeting | Picked from the icon list. |
| Invite Attendees | Other people to note against the event. | The names of the people expected | |
| Date From | The day the event starts. | 12-02-2026 | |
| Date To | The day it ends. | 13-02-2026 | Set it the same as Date From for a one day event. |
| Time From | What time it starts. | 10:00 | |
| Time To | What time it ends. | 16:30 | |
| Description | The detail. | Auditors from the Collectorate. Bring the bonded register and the last three GDs. | |
| Color | The colour the event shows in. | Red for anything with an outside authority in it | Pick one colour per kind of event and keep to it, or the colour stops meaning anything. |
How to configure it
- Open Events.
- Add an event. The user it belongs to is the one thing the save insists on.
- Type the title and the description.
- Set the dates and the times. For a one day event put the same date in both.
- Pick an icon and a colour.
- Note anybody else expected in Invite Attendees.
- Save.
Scenarios
"I want the audit visit on my diary without raising a document for it"
That is exactly this screen. Title, the two dates, a red colour, and the detail in the description. Nothing is assigned and nobody is notified.
"I need somebody to actually do something by Friday"
Then not this screen. Use Task for a piece of work with a due date and a status, or Create Activity for a call or a meeting assigned to a person, which also tells them it is theirs.
What it is connected to
- Nothing else in PeopleNest reads what you enter here.
- For work that has to be assigned and chased, see Task and Create Activity.
If something looks wrong
- "The save says the name cannot be empty" - the event has no user against it. An event has to belong to somebody.
- "Nobody was told about the event" - events do not notify anybody, whatever is in Invite Attendees. Use Create Activity if the person has to be told.