> 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/3.-flaik-connect-api/employee-management/rtp-prerequisites.md).
# RTP Prerequisites
Notes for setup in RTP.
The Employee Upsert functionality introduces an Alternate ID. You RTP administrator will need to enable this.
**Create a new Profile Type** (will need to be completed by an RTP Admin - or via a database update)
> The Admin entity 'Profile Type' needs to be set in dbo.AdminEntity to 1 and then Profile Types need to be added to the RTP Admin Security Group.
```sql
// Example Step 1
UPDATE a
SET a.StatusCode = 1
FROM dbo.AdminEntity a
WHERE a.Description = 'Profile Type'
AND a.StatusCode = 2
```
1. The ResortServiceAPI contains this configuration - default value is 99
**Create a Profile Type (make sure the profile type is added to the Flaik POS Integration's appsettings files (POS section)**
---
# 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/3.-flaik-connect-api/employee-management/rtp-prerequisites.md?ask=&goal=
```
`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.
