Gebeurtenissen beheren
Browse events · Manage event rsvp · Edit event
Voor wie
Beheerders, medewerkers en IT-teams die ITLedger gebruiken voor dienstverlening, assets, compliance en rapportages.
Taken
Kies je taak. De volledige werkwijze, voorwaarden en aandachtspunten staan hieronder in het Engels.
Browse events
Browse events.
Who can do this: Tenant administrator, Operator
Before you start
- Use an account with access to the stated page and permission for the chosen action.
Safeguards
- Events must be enabled; disabling the feature hides event surfaces but retains stored events.
- Events belong under ITSM → Events.
- Use the displayed event number and name when identifying an event.
- Events can involve forms, acknowledgments, voting, resource context, and history; they are broader than a simple date on a calendar.
- Upcoming events can surface in portal/home widgets, so event wording should be understandable to the intended audience.
- Event resource links should be kept accurate so affected assets, locations, or services can be understood later.
- Open ITSM → Events or the event widget where the event appears.
- Use event cards or the detail modal to review timing, description, status, and linked resources.
- Review event history when reconstructing what changed or who interacted with the event.
Expected outcome: The user has reviewed the result of browse events in the application.
Manage event rsvp
Manage event rsvp.
Who can do this: Tenant administrator, Operator
Before you start
- Use an account with access to the stated page and permission for the chosen action.
Safeguards
- Events must be enabled; disabling the feature hides event surfaces but retains stored events.
- Events belong under ITSM → Events.
- Use the displayed event number and name when identifying an event.
- Acknowledgment and voting hooks imply user-specific state; one user responding does not mean all users have responded.
- Review the particular acknowledgment or vote before submitting your own response.
- Open ITSM → Events or the event widget where the event appears.
- Use event cards or the detail modal to review timing, description, status, and linked resources.
- Use acknowledgment or voting sections when the workflow requires user response.
Expected outcome: The user has reviewed the result of manage event rsvp in the application.
Edit event
Edit event.
Who can do this: Tenant administrator, Operator
Before you start
- Use an account with access to the stated page and permission for the chosen action.
Safeguards
- Events must be enabled; disabling the feature hides event surfaces but retains stored events.
- Events belong under ITSM → Events.
- Use the displayed event number and name when identifying an event.
- Relation-tab plus actions should link existing events first. Dedicated create-new affordances can exist where users are intentionally scheduling a new event, but linking flows should not default to creation.
- Upcoming events can surface in portal/home widgets, so event wording should be understandable to the intended audience.
- Event resource links should be kept accurate so affected assets, locations, or services can be understood later.
- Open ITSM → Events or the event widget where the event appears.
- Create or edit events through the event form when scheduling new operational work or communication.
- Add affected resources or context so users can understand impact.
- Review event history when reconstructing what changed or who interacted with the event.
Expected outcome: The user has reviewed the result of edit event in the application.
Aanbevolen werkwijze
- Maak eigenaarschap duidelijk.
- Gebruik statussen en prioriteiten consequent.
Gerelateerde handleidingen
Lees verder in Tickets en aanvragen
Dagelijkse support: tickets, e-mailbeoordeling, taken, uren en goedkeuringen.