--- url: https://docs.codefox.ai/self-host/running-admin.md --- # Running Foxden Admin This page covers what is specific to running Foxden Admin on your server: its parts, its data, the secrets that must never change, and its own switches. Admin is the suite's front door: one sign-in for every app, the people and their access, the company, AI and the server. ## Where it runs | | | |---|---| | Folder | `/opt/codefox-auth` | | Address | `admin.` | | On the server | `127.0.0.1:3020` | | Services | `app`, `db`, `migrate`, `control` (the control service), `updater` | | Smallest size | See [Server sizes](/reference/sizing) | | Settings | [Admin settings](/reference/settings/admin) | The installer adds Admin for you when you install two or more apps, or one app other than Arctic in the `foxden init` wizard. What it does for the other apps is explained in [Admin](/how-it-works/admin) under How it works. ## The first Owner Admin has no passwords. The installer makes your email address the first Owner and prints a one-time setup link, which signs you in until someone has signed in another way (an email link, Google or Microsoft). `foxden console link` prints the link again. Set up a lasting way in early, on **Workspace** › **Sign-in**; see [Sign-in](/run-your-company/sign-in). ## Its data * **Database**: everything set in the console. Backed up each night at 01:30. * **Files**: files that assistants hand through Admin's assistant gateway. On a server with Library they are kept in Library; on a server without it, in Admin's own `files` folder for seven days. They are not in Admin's backup. ## Secrets that must not change Admin's `APP_SECRET` protects the keys Admin signs with, and every app trusts Admin because of those keys. With a different `APP_SECRET`, the keys cannot be opened, and no app can trust what Admin signs. Keep a copy off the server, and on a new server put it back before you restore Admin. See [Back up and restore](/self-host/backup). Admin also holds one feed secret per app (`FEED_SECRET_FENNEC`, `FEED_SECRET_CORSAC`, and so on); each app holds the same value as `CODEFOX_AUTH_FEED_SECRET`. The installer writes both ends. Change one end and that app no longer hears from Admin. ## The control service Admin's stack runs the control service, which lets the **Server** pages change the server. It runs as root on the server, from a fixed list of `foxden` commands, and logs every request to `/var/log/foxden/control.jsonl`. Turn it off with `FOXDEN_CONTROL=off` in Admin's settings, then restart Admin. See [Keys, secrets and access](/self-host/secure). Admin cannot update itself from inside: the server does it, as for every app. Its row on **Server** › **Products** has **Update** and **Restart** like the others, and the console is away for a minute or two while either runs. ## Switches for emergencies Admin's settings have three switches, each of which stops one part of Admin while it is set. They work even when the part they stop is what is broken. Turn one on with the switch on Admin's settings page (open **Server** › **Products** and select **Admin**), or with `foxden config set 1 --product admin`, then restart Admin. | Setting | While it is set | |---|---| | `LLM_GATEWAY_DISABLED` | Every app's AI refuses, whatever keys are pasted. | | `MCP_DISABLED` | Admin's assistant connections, tokens and tools answer nothing. | | `SUITE_MCP_SCHEDULER_DISABLED` | Scheduled assistant actions wait; nothing scheduled runs. | ## Email Admin sends sign-in links and invitations through Resend only. Without email, people sign in with Google or Microsoft. See [Set up outgoing email](/self-host/email).