> For the complete documentation index, see [llms.txt](https://docs.friendlyway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.friendlyway.com/support/definitions.md).

# Definitions

## General

**friendlyway Cloud Platform (or Platform):** A modular cloud-based software platform with a microservices-oriented architecture, which provides a basis for various solutions, including Digital Signage and Visitor Management. [Learn more](/about-the-platform/what-is-friendlyway-cloud-platform.md).

**Module:** An autonomous part of the software platform, which serves a specific use case and can be added or removed as necessary. friendlyway modules include Content Management, Device Management, Visitor Management (Check-in), WayFinding, and more.

**Visitor Management:** A module that allows managing planned/unplanned visits based on a defined workflow, including invitations, notifications, badging, document handling, etc. [Learn more](/visitor-management/intro-to-friendlyway-visitor-management.md).

**friendlyway Player (or Player):** An application that plays media content for signage or visitor management purposes on kiosks’ screens according to the schedule. It is available for Windows.

**Kiosk:** A physical device with one or more displays used for presenting content to end users and typically providing interactive self-service features.

**End User:** A consumer of the content and information displayed on the screen of the kiosk.

**User:** A platform user with personal account information, credentials, and a set of permissions. A personal account is linked with a company account.

## Visits & Visitors

**Visit:** An event or meeting organized by a host and held at a specific location.

**Planned Visit:** A visit prearranged and created by a user in advance.

**Unplanned Visit:** An unexpected visit created at a kiosk on the spot.

**Visitor:** A participant or attendee of a visit.

**Host:** The organizer or coordinator of a visit.

**Visit Type:** A visit category with a collection of distinct custom fields designed to capture particular information relevant to that category.

**Visit Log:** Records of visitors' completed check-in/out and self-registration activities with their timestamps and other data.

## Visitor Management Process

**Workflow:** The configured process for visitor management at a kiosk.

**Registered Visitor:** A visitor with a planned visit who completed registration either online (pre-registration) or at a kiosk using an access code from the invitation.

**Self-Registered Visitor:** A visitor with an unplanned visit registered directly at a kiosk.

**Checked-In Visitor:** A visitor checked in either through the workflow at a kiosk or manually by a user on the Platform.

**Onsite Visitor:** A visitor who has checked in and not checked out yet.

**Checked-Out Visitor:** A visitor checked out at a kiosk or manually on the Platform, typically when leaving the building or premises.

**Manual Check-in/out** is done by a user on the friendlyway Cloud Platform.

**Auto Check-in/out** is done automatically by the system.

**Check-in Result:** The specific outcome or action that occurs at the conclusion of the check-in process at a kiosk. This can include actions such as releasing an RFID card, generating a badge, or any other predefined action based on the workflow.

## Settings

**Static PIN code:** A fixed code assigned to a visitor, allowing them to check in/out at a kiosk. This PIN code remains constant and never changes.

**Email Template:** A predefined template containing text and keywords, designed for creating consistent emails. It serves as a base for crafting visit invitations and notifications to visitors and users.

**Invitation:** An individualized email created using an email template and sent to a specific visitor. It may contain unique details or instructions relevant to that visitor.

**Group Invitation:** An email derived from an email template, containing a list of QR codes, PINs, or similar information for all visitors associated with a particular visit. It is typically sent to a group leader or coordinator for distribution to their respective visitors.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.friendlyway.com/support/definitions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.