Landing pages
Landing pages (guest web apps) are authored from the dashboard—either from an organization-scoped list or global overview screens when your role permits. Editors configure shell settings, multilingual copy, visuals, domains or slugs, tile ordering, and optional assistant tooling.
Permissions
Landing page work requires organization-level permissions summarized in /reference/permissions. Guides might see analytics without edit rights; hidden routes usually mean the session lacks the backing permission—not that the feature vanished.
Typical workflow
1. Create or duplicate
Create a fresh shell or duplicate an existing landing page when campaigns repeat structure.
2. Build the tile grid
Open the landing editor, add modules from the tile picker, and reorder them until the story reads correctly on mobile. Refer to /reference/tile-types when comparing choices.
3. Configure each tile
Deep-link into each tile's form to attach backing records—events views, tours, galleries, chatrooms, and similar. Respect allowed sizes; mismatched historical sizes should be corrected so previews match guest runtime.
4. Scheduling, activity, and restrictions
Many tiles support visibility windows, activity modes (always available versus timed), and optional geo or network restrictions described in /product/landing-pages-and-tiles/layout-sizing-and-visibility.
5. Nested landing experiences
Landing page tiles can link to another landing page for hierarchical navigation (overview → detail sections). Confirm tenancy and branding rules before cross-linking experiences owned by different teams.
6. Preview and publish
Use dashboard previews or embed snippets to validate translations, imagery, media-heavy tiles, and moderation-sensitive modules before distributing QR codes broadly.
Operational tasks
Analytics
Organization analytics surfaces complement /dashboard/web-apps-and-tours/analytics.
Assistant authoring
When AI drafting assistants appear, treat suggestions as drafts—verify facts, accessibility, moderation policy, and multilingual completeness before publishing.
Troubleshooting
| Symptom | Check |
|---|---|
| Tile missing for guests despite appearing active | Schedule windows, inactive overlays, organization restrictions. |
| Unexpected layout | Tile size versus embedded expectations—re-save with supported sizing. |
| Map modules centered incorrectly | Saved map viewport or filter defaults inside the tile configuration. |
| Nested navigation loops | Linked landing page accidentally points back to its parent. |
Escalate cross-tenant concerns through your internal support process.
Related concepts: Tile reference, Site plans, Gallery, Offers, Product hub.