> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/helpdesk-integrations/front/install-and-set-up.md). # Install and set up Connect your Front company to Screendesk, enable the app in Front, and choose its settings. You need to be an admin in Screendesk and in Front. You connect Front once, for the whole workspace, and each Screendesk workspace connects to one Front company. {% embed url="" %} ## Connect 1. In Screendesk, go to **Settings → Integrations** and click **Connect** on the **Front** card, under **Helpdesk**. 2. Front asks you to approve Screendesk's access. Choose the Front workspaces whose shared inboxes Screendesk may post in, and approve. 3. Front sends you back to Screendesk, which opens the Front settings. The Front card then shows Screendesk as connected to your Front company. 4. In Front, enable Screendesk in Front's App Store. 5. Invite your teammates to the Screendesk workspace with the email address they use in Front. Any role except Watch only can use the app. 6. Open a conversation in one of those shared inboxes, open Screendesk in the sidebar and click **Request a recording**. If a recording link appears in your reply, setup is done. Screendesk reaches the shared inboxes of the Front workspaces you chose. A recording requested in another inbox stays in Screendesk; a teammate's individual inbox needs API access switched on by its owner in Front. ## Settings Click **Configure** on the Front card in **Settings → Integrations**. The settings follow a recording's way: ![The Front settings](https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2FciedN3pbL208QMymIVyZ%2Fdocs-front-configure-sheet.png?alt=media) 1. **Ask from a conversation**: **Recordings in the app** sets what the app lists under its actions, **From this customer** or **In this conversation**. 2. **When a recording arrives**: Screendesk adds an internal comment to the conversation, with a link to the recording. **Tag the conversations** tags the conversations Screendesk works in: `screendesk-recording-requested`, `screendesk-recording-received`, `screendesk-recording-sent`, `screendesk-video-shared`, `screendesk-booking-link-shared` and `screendesk-live-screensharing`. Use them in Front's reports, or turn **Tags** off. 3. **The app in Front**: the Front company and who connected it. **Sidebar app** says when Front last loaded the app, and **Inboxes Screendesk can post in** lists the inboxes the connection reaches. Settings save as soon as you change them. ## If the app shows a message * **Connect Front to Screendesk**: the workspace isn't connected yet. A Screendesk admin follows **Connect** above. * **You're not in this Screendesk workspace**: the teammate's email in Front doesn't match a member of the workspace. Invite them with the email they use in Front. Already invited, they see **Accept your Screendesk invitation**. * **Your Screendesk role can't use the app**: Watch only members can watch recordings but not request or send them. Change their role in [Members](/settings/member-management.md). * **Update Front to use Screendesk**: this version of Front can't confirm who the teammate is. Update or reload Front. ## When the connection breaks If Front stops accepting Screendesk's access, for example because the app was disabled in Front or its access was removed, the Front card shows **Action required** and the app says **Reconnect Front**. Recordings still arrive in Screendesk but no longer reach your conversations. To fix it, click **Reconnect** on the Front card, signed in to Screendesk as an admin, and approve the access in Front again. ## Disconnect 1. In Screendesk, click **Disconnect** on the Front card, then **Disconnect** in the dialog. Screendesk stops posting to your Front conversations. 2. To remove the app from Front too, disable it in Front's App Store. --- # 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://docs.screendesk.io/helpdesk-integrations/front/install-and-set-up.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.