customize terms of use text from the admin#591
Draft
e-lie wants to merge 3 commits into
Draft
Conversation
AppSettings gets a terms_content field to let admins override the /terms page text. Expose it (and the rest of the public settings) via a new unauthenticated GET /settings, following the same pattern as LLMDataPublic/GET /models/, and drop the now-redundant GET /admin/settings.
Add a Textarea field to the customization admin page and render terms_content on /terms (split into paragraphs) instead of the default content when it is set. Admin pages now read settings from the new public GET /settings.
e-lie
force-pushed
the
feat-customize-terms-of-use
branch
from
July 16, 2026 15:17
c0aec33 to
128bad5
Compare
e-lie
marked this pull request as draft
July 16, 2026 15:17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Test plan