Administration

The admin panel is at /admin and in the menu at the bottom of the workspace sidebar. Only administrators can open it. For everyone else the address returns a 404 page.

Settings

Site. Name and public address. The address is used in emails, the sitemap and sign-in callbacks, so it must match the real domain including https://.

Accounts.

• Allow new people to register. Untick it for a private site. Existing users can still sign in.
• Require email verification. New accounts must confirm their address before using the workspace. This needs working outgoing email, and the setting cannot be saved without it.
• Chat requests per user per minute. A rate limit that protects against runaway scripts.

Outgoing email. SMTP host, port, username, password and sender. Without it, password reset and verification emails cannot be sent, and the sign-in pages say so. After saving, send a test from System.

Sign in with Google and GitHub. Create an OAuth application with each service, set its callback address to the one shown on the settings page, then enter the client ID and secret. The buttons appear on the sign-in page once both values are saved.

Web search for agents. A site-wide Brave Search key, Tavily key or SearXNG address. Users can override it with their own.

Providers.

• Allow providers on local or private network addresses. Needed for Ollama and other servers on your own network. Leave it off on a public site with open registration, because it would let any user make your server contact internal addresses.
• Presets. Untick a preset to hide it from the "Add provider" list.

Secrets such as the SMTP password are write-only. The page shows whether a value is saved, never the value itself.

Users

Search by name or email. For each account you can mark the email as verified, suspend or restore it, grant or remove administrator rights, or delete it. Suspending signs the user out everywhere. Deleting removes their conversations, files and provider connections.

The list shows how many chats and provider connections each user has. It does not show their content.

Content

• Blog posts and Documentation are written in Markdown. Each has a URL slug, a title tag and a meta description for search engines. Unpublished items are hidden from the site and the sitemap.
• Legal pages are the privacy policy and the terms. They ship as templates marked "Needs owner review". Edit them for your situation and tick Reviewed.

Raw HTML in content is shown as text. Use Markdown formatting.

Contact messages

Submissions from the contact page are listed here. They are stored in the database and are not emailed, so check the page from time to time.

System

Shows software versions and PHP limits, runs database updates after an upgrade and sends a test email.

Things to check before opening the site to others

1. HTTPS works and the site address in the settings uses it.
2. Outgoing email is configured and tested.
3. The privacy policy and terms have been reviewed.
4. Registration is set the way you want it.
5. You have a backup routine for the database and the .env file.