Costs are estimates from logged token counts at list prices.
Evals
Three judges per conversation: Human (an admin's hand label) · Haiku (the production review) · nimble (the local decision model)
Users
Actions
Click a user to see their chats.
Beta features
New users: switched on for each account the first time it signs in; existing users keep the flags they have (change those on each user's page). Everyone: on for every user right now, a trial before the feature goes GA; switching it off again leaves users who had their own flag with it. GA features have no flag and aren't listed.
Members of a team can read and continue every chat in it; each turn is charged to the member who asked. Any user can create teams and invite people by email. Here you can also add members directly and change a team's owner. Deleting a team deletes its chats.
Users ask for more usage with a reason; they never see dollar amounts. Approving sets the user's monthly limit to the amount you enter (it stays until changed again) and emails them. Denying emails them your note. One-time resets are self-serve; they show up here under Approved and All.
Notes come from resolved chats and are shown to every user as community experience. New notes start as drafts, which chat can't see, until you publish them. Every save and publish is checked for personal details server-side.
Published posts pop up once for each user on their next visit, newest first, and stay under What's new in the user menu. Someone who signs up later only gets posts published after they joined, unless the post is marked Show to new users. A publish date in the future holds a published post back until then. The admin password can only write drafts, so Claude's posts wait here for you to publish.
Blocked addresses can't request a sign-in link, and any session they already have stops working immediately. Use @domain.com to block a whole domain.
Products
Order
Id
Product
MCP URL
Tools
Headers
State
Last change
Actions
These are the documentation MCP servers chats answer from, in the order users see them. A change applies on the next message anyone sends, no restart. A product that's on is on for every user until they turn it off themselves (⚙ menu). Turning one off here removes it from every chat but keeps users' settings; deleting forgets it. The server itself must be reachable from the chatJPt container (the shared mcp docker network, http://<container>:8000/mcp). The id is the tool prefix the model sees and what users' settings refer to, so it can't be changed once set.
Add product
Becomes the tool prefix (proliant__search_docs): lowercase letters, digits, - or _. Can't be changed later.
For a server behind torii, put its service key here as Authorization: Bearer <key>. A saved key is shown as •••• plus its last 4 characters and stays as it is unless you type a new value. Test connection uses these headers too, so a wrong key shows up here as the server's error.
Playbooks
Title
Id
State
Version
Runs
Avg cost / chat
Updated (UTC)
Actions
A playbook is a curated advisor prompt: a persona and procedure in Markdown that users will launch as a chat. Users see one only when it's on, every product it requires is visible to them, and, for a beta one, they have its beta flag (on each user's page under Beta features). Playbooks shipped with chatJPt are added once, off and beta, and never overwritten: what's here is the truth. Deleting hides a playbook and keeps its id reserved; Show deleted lets you restore it. The admin password can only work on playbooks that are off.
New playbook
A stable slug: lowercase letters, digits and -. Can't be changed later.
Preview
Admins
Email
Role
Added by
Added at (UTC)
Actions
Admins sign in to this page with their own chatJPt account (email link or passkey); they don't need to have used chatJPt before. New admins get an email. Removing or blocking an admin locks them out on their next click. Owners are set in CHATJPT_ADMIN_EMAILS and can't be removed here.