Manage calendars and events
Review calendar context, create or change events, and validate time zone, attendees, and visibility before saving.
Audience, roles, and scope
Workplace calendar views and event interaction; tenant scheduling policy and downstream attendee delivery are separate.
Who this is for
- Workplace users with calendar access
Roles
- Calendar user
- Event organizer
Before you begin
- Calendar access
- Known meeting time zone and attendee list
Article tags
- calendar
- events
- attendees
- time-zone
Procedures
Follow the sequence and stop when identity, authorization, target, or result differs from the article.
Create an event
Check scheduling details before notifying attendees.
- 1Select calendar and time
Choose the intended calendar, date, start and end time, and confirm the displayed time zone.
- 2Add event details
Enter a clear title, location or meeting context, attendees, and only information appropriate for the selected visibility.
- 3Save and verify
Review conflicts and recipients, save once, then reopen the event to confirm its stored time and details.
The event appears on the intended calendar with the correct time, visibility, and attendee context.
Security and data handling
- Use only the identity, tenant, role, and data scope approved for the task.
- Verify targets and expected effects before saving, sending, publishing, exporting, deleting, or approving.
- Keep secrets and regulated data out of screenshots, URLs, free-text diagnostics, and ordinary support messages.
- Keep sensitive agenda or attendee details out of broadly visible calendars.
Known limitations
- Calendar visibility selections in the client can be locally represented and may not persist without connected backend support.
- Invitation delivery, free/busy data, conferencing, and recurrence behavior depend on the configured calendar service.
Troubleshooting
You cannot open Vianordis Workplace
Likely cause: The session expired, the account is not entitled, or the required tenant or role claim is missing.
- Open the service through the approved Vianordis entry point and sign in again.
- Confirm the intended organization, tenant, and account are in use.
- If access remains denied, record the time and request an entitlement check; do not attempt direct-URL bypasses.
A documented control or navigation item is not visible
Likely cause: The current role, subscription, tenant configuration, release status, or feature flag does not expose it.
- Confirm the audience, role, prerequisites, and limitations in this article.
- Refresh after a new sign-in and verify the correct tenant context.
- Ask the responsible administrator whether the capability is enabled before reporting a defect.
A saved change or background result is not visible
Likely cause: Validation failed, processing is incomplete, the view is stale, or the feature is locally simulated rather than persisted.
- Review inline validation, status indicators, filters, and the selected tenant or workspace.
- Refresh once and search by a stable identifier before repeating the action.
- Do not repeat irreversible or externally visible actions until the first operation's state is known.
Source verification
Calendar views, event fields, and interaction controls were reviewed in the pinned source.
Reviewed paths at 5752ab1
src/app/calendars/page.tsxsrc/lib/calendar/api.tssrc/app/api/calendar/events/route.tssrc/app/api/calendar/events/[id]/route.ts
Contact support
Contact support when
- A repeatable Vianordis Workplace error blocks an approved task
- Expected access, tenant scope, data, or status appears incorrect
- A security, privacy, financial, compliance, or data-loss concern is suspected
Include
- The page, action, expected result, and exact error text
- The time of occurrence with time zone and whether it is reproducible
- Your tenant, role, browser, and sanitized record or correlation identifier
- The troubleshooting steps already completed
Never include
- Passwords, access tokens, API keys, recovery codes, session cookies, or private keys
- Unredacted personal, financial, health, student, employee, or other regulated data
- Confidential documents or message bodies unless support provides an approved secure channel