--- url: https://docs.codefox.ai/apps/pampas/set-up-for-your-team.md --- # Set up Pampas for your team This page shows people who can manage Pampas how to set it up once for everyone: the link to Fennec, fonts, the operator details respondents see, captcha keys and API keys. It also says what Foxden Admin manages instead. ## Before you start * You can manage Pampas. **Settings** appears in the sidebar only for people who can manage it. * Most changes on this page affect the whole server, so Pampas asks you to confirm it is you first: enter your password again, or sign in again. Settings has two parts: **Workspace**, how Pampas is set up for the team, and **Server**, what belongs to the installation. Pampas has no settings of a person's own, so there is no **You** part. ## Pair Fennec A Fennec destination on a form turns each response into a lead (see [Send responses to your team and tools](/apps/pampas/send-responses)). It needs Pampas paired with Fennec. When the two apps were set up together on the server, **Fennec pairing** says **By this server** and there is nothing to do. Otherwise: 1. Ask whoever manages your Fennec server for Fennec's address and its website secret. 2. Under **Fennec pairing**, type Fennec's address in **Base URL**. 3. Paste the secret in **Shared secret**. It needs at least 16 characters, is stored encrypted and is never shown again. 4. Select **Pair Fennec**. **Remove pairing** stops the Fennec destinations on every form until Fennec is paired again. ## Install fonts 1. Under **Fonts**, find a font in the **OFL catalog**, for example Inter, Fraunces or IBM Plex Sans. 2. Select **Install**. Pampas downloads it once and serves it from your own server from then on. Anyone building a form can then choose it under **Installed font** in the form's theme. ## Name the operator of your forms Every form shows respondents a short privacy notice built from the form's real settings: who runs the form, how long answers are kept, and how to delete them. Under **Operator details**: 1. In **Operator name**, type the name respondents should see. Leave it empty to use your company name, from Admin when Admin is connected. Fill it in when the notice must use another name, such as a legal name. 2. In **Operator contact**, type an email address, phone number or contact page. Leave it empty to use the support address set in Admin, if there is one. 3. Select **Save operator details**. ## Turn on captcha Forms set to ask for a captcha (on **Share**, under **Access**) need a provider's keys, saved once for every form. Pampas works with **Cloudflare Turnstile** and **hCaptcha**. 1. Get the keys from the provider: * Cloudflare: in Cloudflare's dashboard, open Turnstile, add a widget for the address people open your forms on, choose Managed, and copy both keys. * hCaptcha: add a site for that address, and copy its site key and your account's secret. 2. Under **Captcha**, choose the **Provider**. 3. Paste the **Site key** and the **Secret key**. 4. Select **Save keys**. Pampas checks the keys with the provider before it saves them. **Remove keys** turns captcha off: forms set to ask for one are then sent without it. When Foxden Admin is connected, it holds the captcha keys instead, and **Captcha** says they are set on Pampas' page in Admin (**Server** › **Products** › Pampas). When the server's own settings file holds keys, **Captcha keys** shows **In use** and the keys are changed there by whoever runs the server. ## Create an API key Scripts and other systems reach Pampas with an API key. 1. Under **API keys**, type a **Label** that says what the key is for. 2. Choose a **Scope**: **read** to read forms and responses, **readwrite** to change them too. 3. Select **Create key**. 4. Copy the key. It is shown only once. Select **Revoke** on a key you no longer use. For what a key can do, see [the Pampas API page](/connect/pampas-api). ## Check AI and updates * **AI usage** says **AI is off** when this server has no AI, or leads to Admin, where the model, limits and spend for Pampas are set. See [Set up AI](/run-your-company/ai). * **Updates** shows Pampas' version and installs updates when Pampas runs alone. When Admin is connected, updates are on Admin's **Server** › **Products** page for every app. ## What Foxden Admin manages instead When Pampas is connected to Admin: * People and their level: **People and access** leads to Admin, where you give people access to Pampas and choose whether they can use it or manage it. A change reaches Pampas at the person's next sign-in, or within five minutes. See [Give people access to the apps](/run-your-company/people). * Your company's name and support address, which the operator details fall back to. See [Your company's name and brand](/run-your-company/company). * Captcha keys, AI and updates, as described above. * Sign-in: people sign in to Pampas through Admin. Forms, destinations, fonts, the Fennec pairing, API keys and Pampas' own activity stay in Pampas. Pampas has no page of its own to add people or change their level. Without Admin, people sign in through the server's own sign-in, and the first person who can manage Pampas is named when the server is set up. Connect Admin to add people and set their levels. ## Troubleshooting ### "That URL is not reachable from here. Use Fennec's public https URL." Pampas could not reach the address in **Base URL**. Use the address people open Fennec on, starting with `https://`. ### "Cloudflare does not know that secret key" (or hCaptcha) The provider refused the secret key: it is mistyped or belongs to another account or widget. Copy both keys again from the same widget or site. ### "That site key and secret key belong to different hCaptcha sites." Copy the site key and the secret from the same hCaptcha account and site. ### The captcha does not show on a form The site key is wrong, or the provider does not allow the address people open the form on. Check both in the provider's dashboard, then save the keys again. ### Captcha keys cannot be edited here Admin or the server's settings file holds them. Change them in Admin's Pampas page, or ask whoever runs the server.