Reception is your server's safe front door: public pages that outsiders can use — book a slot, submit a form, drop a file, answer an approval — served straight from your own server, never routed through Recued's cloud. Visitors need nothing but the link.
#What you can publish
- Reception pages — general-purpose pages composed from blocks: text, forms, links.
- Scheduling links — offer slots, take bookings.
- Intake forms — structured requests from clients or collaborators.
- File drops — a place for someone to hand you a file.
- Approval links — let a specific person answer a question you routed to them.
#Author from a template or a sentence
Two paths produce the same endpoint. Pick a template from the gallery and fill its slots, or describe what you want in a sentence and let AI propose the page. Templates compile deterministically from their slot values — AI can improve wording and infer optional defaults, but it is never required, and an offline or model-less server can still publish every first-party template. Either way you review the proposed page and edit it before anything goes live.
#Requests wait for you
Reception is review-then-approve by default. An incoming submission does not execute anything: it becomes a held operation at the same enforcement boundary as everything else and lands in your inbox. There you see what was submitted, edit the arguments if they need correcting, and approve or decline. Nothing a visitor sends runs ahead of your decision.
#Attachments
Files a visitor submits land in your warehouse like any other inbound file and attach to the request. Optional scanner packs can annotate attachments with an advisory scan result before you open them.
#Reachability
A public page needs a public name — see Reachability. The name points directly at your server; the page, the submissions, and the files never pass through the cloud.
#Related
- Grants and approvals — the gate that holds incoming requests.
- Selling access — reception pages can carry the link to a seller's checkout.