> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/configuration/appointments-agent-+-employee-linking.md). # Appointments - Agent + Employee Linking **Available on:** Desktop · Web · Phone This screen links each **stylist** (agent) to their **employee** record. The link lets the diary use each stylist's own attendance — shift, leave and personal holidays. You need it when **Use Employee Wise Attendance** or **Hide Non Employee Agents** is ticked in Configuration: * With **Use Employee Wise Attendance**, a stylist without a link has a shaded column heading in the diary and is left out of **Stylist Attendance**. * With **Hide Non Employee Agents**, stylists without a link are not shown in the diary at all. Open it with the **Agent-Employee Linking** button in **Configuration › Settings**. The window is titled **Agent + Employee Linking**. (The main-menu entry *Appointments - Agent + Employee Linking* only controls who may change or delete links — it does not open the screen.) ## Linking The grid has one row per link — **AGENT NAME** and **EMPLOYEE NAME**. * Type in **AGENT NAME** (or press Enter) to open the stylist search and pick a stylist. On a new row, the employee whose name contains the stylist's name is filled in for you — change it if it is wrong. The cursor moves on to **EMPLOYEE NAME**. * Type in **EMPLOYEE NAME** to open the employee search and pick a different employee. * Click **Save** and answer *"Are you sure to Save changes ?"*. Each stylist can be linked to only one employee, and each employee to only one stylist — otherwise you see *"Agent Name Already Exists."* or *"Employee Name Already Exists."*. To remove a link, delete its row and answer *"Are You Sure You Want To Delete Row"*, then **Save**. Changing or saving links needs modification rights for *Appointments - Agent + Employee Linking* in user rights (*"You Are Not Allowed To Modify Row."* / *"Modification rights not available....."*); deleting needs delete rights (*"You Are Not Allowed To Delete Row."*). > **Example.** Your stylist *Anita* is also employee *ANITA SHARMA* in payroll. Add a row: type in **AGENT NAME** and pick Anita — ANITA SHARMA is filled in under **EMPLOYEE NAME** (pick another employee if it is wrong). Then **Save**. With **Use Employee Wise Attendance** on, Anita's own shift, leave and holidays now block out time in her diary column. ## On the web The screen works the same way on the web, as a window opened from Settings. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/configuration/appointments-agent-+-employee-linking.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.