Category: Mobile Navigation

ORCHESTRIS support articles for Mobile Navigation.

  • What should I do if a timeline card does not open on mobile?

    What should I do if a timeline card does not open on mobile?

    What should I do if a timeline card does not open on mobile?

    Short answer

    If a mobile timeline card does not open, refresh the page, try another card, and report the role, device, event, and whether the page stopped accepting taps afterward.

    Quick checks

    • Refresh the event page.
    • Try another card in the same timeline.
    • Try opening the same card on desktop if available.
    • Confirm the card is visible to your role.

    What should happen

    • On smaller screens, opening a card should move to a focused card detail view or open a clean mobile-friendly card panel.
    • The back control should be reachable below the phone camera and status area.
    • The page behind the card should not scroll while the card is open.

    What to report

    • Device model
    • Browser or app
    • Role
    • Event name
    • Card name
    • Whether tapping stopped working after the card failed to open

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.

  • How do I stay signed in and refresh on mobile?

    How do I stay signed in and refresh on mobile?

    How do I stay signed in and refresh on mobile?

    Short answer

    Mobile and PWA sessions should remember trusted devices where possible, while still letting users refresh content without breaking the current event view.

    Session behavior

    • ORCHESTRIS should keep users signed in on trusted devices when the browser or app allows secure session storage.
    • Users may still need to log in again after clearing browser data, switching workspaces, or using a private browser session.

    Refreshing

    • Pull-to-refresh should reload the current content without unexpectedly opening the first planning card.
    • If the page reloads into the wrong section, return to the dashboard and reopen the event.

    Security

    • Do not rely on IP address or device recognition alone for secure access.
    • Magic links and saved sessions should still respect workspace, role, and event permissions.

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.

  • How does mobile card navigation work?

    How does mobile card navigation work?

    How does mobile card navigation work?

    Short answer

    On mobile, planning cards should open in a focused card screen with a back control so users can complete one card at a time without losing their place.

    Card view

    • Tapping a planning card should open that card's details in place or in a focused mobile view depending on the current portal layout.
    • The back control should sit below the phone safe area so it is not hidden by the camera, time, or battery area.

    Scrolling

    • When a card is open, the page behind it should not scroll by mistake.
    • The active card content should scroll only when the card content itself is longer than the screen.

    Consistency

    • Mobile card controls should match desktop behavior for notes, songs, questions, and blur-save fields.

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.