Loading or processing
Wait for the visible stage. Do not submit again while a consequential request is active.
Six clear starting points · one authoritative product
Choose the guide that matches what you need to do. This page is guidance, not completion tracking. Selecting a guide never grants access, writes data, connects a provider, or publishes a menu.
Role selector
Each option loads a server-rendered guide. All core instructions and links work without client-side JavaScript.
Analyst, translator, and viewer are part of the complete MenuFaro role contract. The first Sites owner-workspace adapter currently authorizes only owner, manager, and menu editor, so these narrower signed-in workspaces must not be presented as available yet.
Target-platform roles; their dedicated Sites workspaces are not connected.The intended role sees allowed aggregate scans, opens, searches, languages, service modes, and engagement. It must not edit menus or inspect unrelated tenant data.
Menu views are not revenue or proof of a sale. Production analyst access remains unavailable until least-privilege route and export tests exist.Review the current public examplesThe intended translation workflow compares the source checksum, keeps previously approved guest text live, and marks a replacement as machine draft, needs review, approved, locked, or outdated.
A translator does not approve tax, allergen, nutrition, or publication authority. Dedicated signed-in translator access is still a target-track vertical.No action is required from this guideThe intended viewer can inspect assigned restaurant information without save, publish, billing, team, provider, or export authority.
Until the viewer workspace is connected, the safe result is an unauthorized state—not silent promotion to editor.No action is required from this guideAsk the restaurant owner or authorized administrator for the narrow role needed for your task. Use your own account and keep the authorization denial visible if the role is not active.
This guide does not grant a role. Production must test cross-role and cross-tenant denial before these workspaces are enabled.No action is required from this guideShared release model
The website and installed web app use the same release contract. A visual preview is never the live menu.
Dish, price, media, theme, translation, availability, tax/service, and safety changes remain private.
Resolve permission, plan, content, media, language, commercial-policy, allergen, and QR blockers.
Only an authorized owner or manager confirms the exact revision and fingerprint. Success waits for durable readback.
The stable token resolves the current immutable release. Republishing does not require reprinting the code.
State and recovery guide
Wait for the visible stage. Do not submit again while a consequential request is active.
Private work stays network-only. Reconnect, then reload the authoritative revision before editing or publishing.
Sign in with your own account, request the correct role, or ask an operator to restore the missing dependency.
Compare the newer server version with your work. Never force a blind overwrite from another browser or phone.
Trust a release, receipt, or provider state only after the page shows authoritative confirmation and identifiers.
Keep Plus pending, failed, or past due until the billing provider and signed lifecycle event confirm the result.
Optional connected iPhone access
Installation changes how you launch MenuFaro, not where data lives. It is not a native iOS release.