Foxden Admin, the console
This page explains what Foxden Admin is as a part of the suite: what its console holds, how it changes the server, and what it means for an app to be connected to it.
Admin is installed on your server like the apps, at its own address (admin. under your domain). It is the suite's one sign-in, the place where the company's people, settings and AI live, and the console from which the Owner runs the server. It is not an app people work in day to day: everyone else uses it only for their own profile and to connect their AI assistant.
Who opens the console
- An Owner can change everything in the console.
- A person who is View only in Admin can open every console page and change nothing.
- Every person who can sign in can open their own profile and connect an AI assistant. Anyone else who signs in to the console is told No access to Foxden Admin. That is normal for most people in the company.
See Identity and access.
Home, Workspace and Server
The console's sidebar has Home, then two groups named like the settings in every app: Workspace for the company's side, Server for the machine's side. Each row is one page; anything long opens as a page of its own with a way back.
Home shows the workspace at a glance, AI requests over the last 14 days, the server's memory, disk and processors, the week across your products, the products and their state, what needs your attention (most urgent first, each row leading to the page that fixes it) and recent sign-ins.
Workspace
- People: everyone in the company and their level in each app, on one table, with invitations and the company directory (Google Workspace or Microsoft 365). See Give people access to the apps.
- Company: the company's name and brand (logo, colour, paper size, support address), which every connected app shows. See Company name and brand.
- Sign-in: which ways to sign in are on, the company email domain, and whether people on it may join. See Choose how people sign in.
- AI: usage and spend by app, model and person, and the limits and models each app may use. See Turn on AI.
- Assistants: calls, failures, rules, scheduled actions, events, and Asking before acting. See Assistants.
- Activity: the activity log of Admin and every app. See The activity log.
Server
- Products: each app's version, whether a newer one is published, whether it has read the latest access changes, who manages its people, and buttons to update, restart or add an app.
- Connections: what the apps share: the email sender, the Google client, the Microsoft client and the AI providers.
- Backups: the newest backup of each app, a button to back up now, and the off-site copy.
- System: moving to another domain, where each app is reached, the server's health check, and install codes for the
foxdencommand line.
See Self-host for each of these tasks.
The control service
The Server pages read the server's real state and change it with buttons. Neither happens in Admin's own code: Admin asks a small control service on the same server, which runs the same foxden commands an operator would type. The settings files on the server stay the one truth, and a change made in the console and the same change made with foxden are the same change.
- The control service ships with Admin and is on wherever Admin runs. Set
FOXDEN_CONTROL=offin Admin's settings file to switch it off; the Server pages then show what is set and change nothing. - Admin can ask only for operations on a fixed list: read the server's state, set shared settings (email, Google, Microsoft, the domain, captcha keys), link apps to each other, change an app's settings, update, turn automatic updates on or off, restart, back up, set the off-site copy, add an app, and hand an app's people to Admin.
- Only an Owner sees the buttons, and only when the control service answers. Each request is signed, and each change is written to the activity log with who asked and how it ended.
- Some settings are never changed from the web. See Security and trust.
What "connected" means
An app is connected to Admin when it holds two things, which foxden init writes when you install Admin with the app:
- Sign-in through Admin: the app sends people to Admin to sign in (see Key flows, end to end).
- The feed pair: Admin's address and a feed secret shared by that app and Admin alone. With it, the app reads who may use it, the company's name and brand, and each person's name and photo, and sends AI requests through Admin.
A connected app hands three things to Admin:
| Handed to Admin | What the app shows instead |
|---|---|
| People, when Admin manages the app's people | No People page of its own; levels come from Admin. |
| The company's name and brand | The values from Admin, without an edit button. A value the app sets for itself still wins where the app has one. |
| Updates | No Updates page of its own; Admin's Products page updates and restarts it. |
What belongs to one app stays in that app, connected or not: its own activity log, keys, webhooks and background work.
On Server › Products, each app shows Running (or Up to date) when Admin can reach it, or one of Not reachable, Needs connection or Status unavailable when it cannot.
An app running alone
Every app can run without Admin. It then keeps its own sign-in, People, Company and Updates pages. Because AI and the assistant gateway live in Admin, an app running alone has no AI features and is not reached through the gateway. See Plan your server.