Admin guide
Everything is managed from the admin area. Collaborators get a subset; administrators get all of it.
Roles
- Visitor: posts ideas, votes, comments.
- Collaborator: the team, who see internal notes, private ideas and the scorecard, and can restatus and moderate.
- Administrator: full access, including settings, products, theming and authentication.
Products
Run several products from one portal. Each product gets a public board at /p/<slug>; every view (board, roadmap, scorecard) filters to any combination of products with shareable ?products= URLs. Ideas with no product land in a General bucket.
Statuses & roadmap
Statuses are fully custom: names, colors, and whether each appears on the home page. On the roadmap, collaborators drag a card between lanes to change its status.
Theming
Set a brand color and per-function accents (buttons, votes, links, header) as design tokens that apply across light and dark mode. Choose a default appearance (light / dark / follow system), set per-product colors, and drop raw custom CSS in Advanced for anything else.
Private ideas
Collaborators and admins can mark any idea private, with the toggle on the share form when creating or the "Make private / Make public" action on an existing idea. A private idea is hidden from everyone else on every surface: board, lists, search, roadmap, RSS, the API, status/product counts, and notifications. Your team sees an amber "Private" badge, and can filter the board to just private ideas.
Disable Sign-ups (Admin, Privacy) stops visitors from creating accounts on their own while the board stays public; registered users, invited users and trusted OAuth providers can still sign in. Private boards always have sign-ups disabled.
Under Admin, Privacy you can also let members submit private ideas (off by default). A member's private idea is visible only to its author, collaborators and admins. A second switch, Members can publish their private ideas (on by default), lets the author make it public later; a member can never make an already-submitted idea private.
Internal notes & comments
Collaborator-only comments sit inline in the discussion but never reach visitors or public counts. Each idea also has one shared internal note, live-synced between the idea page and the scorecard.
Moderation
Optionally require approval before ideas are published. Pending ideas are visible to their author and to collaborators, who approve or decline them from the board and post pages.
MCP (AI assistants)
Off by default. Under Admin, MCP you can let AI assistants such as Claude work in Upvora as the signed-in person: turn MCP on, choose who may connect (administrators only, administrators and collaborators, or any signed-in member), and decide whether clients may register themselves. See MCP.
Vora: the AI ideation agent
Optional and off by default. Enable it under Admin → AI, choose a provider (Anthropic, OpenAI, or any OpenAI-compatible endpoint including a local LLM) and paste a key. Vora interviews the submitter, then drafts a title, summary, tags and a full Idea Brief for them to review before submitting. You can give per-product instructions, view the conversation transcript on submitted ideas, and optionally enable web search (Serper or a self-hosted SearXNG). Submitter email addresses are stored only as a token and never rendered to any browser.
Require Vora for new ideas
Under Admin → AI, Require Vora for new ideas makes the board's form start with Vora for everyone, admins included: Vora interviews, drafts the title, description and Idea Brief, and the person reviews, edits and submits. Products without an enabled agent keep the plain form. The server enforces it too, so the form cannot be skipped by calling the API from a browser session. Assistants connected over MCP, and integrations using an API key, can still submit directly.
File attachments
Ideas always take up to 3 images (5 MB each, re-encoded on upload). Under Admin → General, File attachments on ideas (off by default) also allows PDF, .txt and .md files, within the same 3 attachments per idea and 5 MB each. Comments stay images only.
- Viewed inside the board. A PDF is drawn page by page with pdf.js (no PDF scripts run, links inside are not clickable), Markdown is rendered through the same sanitizer as idea descriptions, and text is shown as text. An Open in a new tab link is there as a fallback.
- Checked on upload. The type comes from the file's content, never its name. Every PDF is fully parsed, including compressed object streams, and refused if it contains JavaScript, launch, submit or import actions, links to other documents, embedded files, XFA forms, multimedia, or encryption that would hide any of that. Text must be valid UTF-8. HTML and SVG are not accepted.
- Served safely. Files are served with their exact type,
X-Content-Type-Options: nosniffand a sandbox that allows nothing to run, only to people who can see the idea (private ideas included), and never on an MCP-only public address. - Turning the switch off keeps existing files viewable; it only stops new ones.