> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/1.-resort-pos-integration/rtp/4.-rtp-specific-flaik-functionality/flaik-greater-than-rtp-employee-config-interface.md).

# flaik -> RTP Employee Config Interface

### Current Implementations

<table data-header-hidden><thead><tr><th></th><th></th><th data-hidden></th><th data-hidden></th></tr></thead><tbody><tr><td>Powdr</td><td>ADP -> flaik -> RTP</td><td></td><td>RTP</td></tr><tr><td>Alterra </td><td>Workday -> flaik -> RtP</td><td></td><td></td></tr></tbody></table>

### Objectives

* Create a standard, static employee identification, unique per employee per resort within a centralized or decentralized environment.&#x20;
* Minimize manual re-entry of employee information in multiple systems to reduce effort and data entry issues.&#x20;
* Enable standard business process capabilities across all RTP Resorts, while retaining core scope.

### Scope

#### In Scope

* Employees only
* Employee/Instructor Onboarding

#### Out Of Scope

* Dependents/Inheritance profiles
* Off boarding/hotlisting
* Continuous updates of employee information&#x20;
* Preference from Resorts to allow nickname/contact info updates in RTP without being overwritten
* Automation of Badge ID creation in ADP Vantage

### Import Logic/Profile Management

**Matching Logic**&#x20;

* Employee ID&#x20;
* Else: Look for customer matching on Email, First/Last Name and Birthdate&#x20;
* If no match, new record will be created

#### Profile Management

* If relationship exists with inheritance of profiles, break the inheritance and write existing to each profile&#x20;
* IP Type Code: Currently set to utilize Person or Employee Type&#x20;
  * Investigation to occur to identify if status code types can be utilized to match to different employee types


---

# 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, and the optional `goal` query parameter:

```
GET https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/1.-resort-pos-integration/rtp/4.-rtp-specific-flaik-functionality/flaik-greater-than-rtp-employee-config-interface.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.