Overview

This editor configures one Information screen: how it looks, when the app may show it, what happens when a member taps each button, and which platforms receive it. A phone-style preview on the right updates as you type and uses your brand colour settings.

Navigation sections: Screen settings (header card), Edit screen (main content), Workflow (trigger + button actions), Platform Settings.

Labels match brand mek (en) in Admin.

Screen settings

The header card above is the settings surface—name, category, and type. There is no separate save for the header; it is included when you click Save.

Edit screen

Default editor for Popup, Curtain, Full Screen, Slider Screen, Menu Screen, Tabs Screen, and Content Screen types.

Fields appear in a draggable list—you can reorder blocks (image, title, body, buttons) except on Slider and Menu types where order is fixed by type. Each block below is optional unless your brand’s design requires it.

FieldWhat to enterMember sees
Image Upload from gallery or pick an existing asset. Optionally check Show App Icon or Show Partners (two placeholder avatars) instead of a custom image. Set Image size in pixels. Hero image or icon above the title. App icon and partner placeholders are mutually exclusive with a custom upload.
Screen title + Title size Headline text and font size (defaults: 28 px popup, 36 px full-screen types). Primary heading on the screen.
Screen subtitle + Subtitle size Supporting line; multiline allowed. Secondary text under the title.
Screen body Main paragraph for standard types. For Slider Screen, this area becomes a list of slide text blocks. For Menu Screen, it becomes the menu item table editor. Body copy, swipeable slide text, or menu rows depending on type.
Button 1 title + colour Primary button label. Pick a brand colour token (primary, secondary, link, and so on). Main call to action. Wired to Next event in workflow.
Button 2 title + colour Second button when you need two choices. Secondary action. Wired to Next event 2.
Cancel button title + colour Dismiss or “Not now” label on modal types. Closes the popup or sheet without running the primary next event.
Additional text Footnote or legal line. Small print below buttons on supported layouts.

Slider Screen: Add one text block per slide in the body editor. Members swipe horizontally through slides on a full-page layout.

Menu Screen: Each row has title, subtitle, and panel id, plus an expandable next event for that row—see workflow action types in the reference.

Cards, grid, and instruction types

Cards Screen

Replaces the generic field list with a card list. For each card:

  • Title — headline shown on the collapsed row.
  • Body — description (multiline) shown when the member expands the row.
  • Image — optional illustration inside the expanded section.

Drag cards to reorder. Remove or add cards with the row actions. Members see a vertical accordion (one topic expanded at a time)—not a horizontal swipe carousel. See Cards Screen in the reference.

Grid Screen

Replaces the generic field list with a tile grid editor. Use this for “pick a topic” hubs (support home, shortcuts into App Content categories).

ControlWhat to enterMember effect
Grid columns Number of columns (default 2). How many tiles appear per row on the full-page grid.
Tile aspect ratio Optional decimal (for example 1.85 on desktop web). Higher = shorter tiles. Tile height relative to width on wide screens.
Title (per tile) Short label on the tile. Primary text on the grid button.
Subtitle (per tile) Supporting line under the title. Secondary text on the tile.
Disabled (per tile) On/off. When on, the tile is visible but not tappable.
Icon / image (expand row) Upload in the detail panel for that tile. Illustration above or beside the title on the tile.
Next event (expand row) Same action types as workflow buttons—for example open an App Content category, another info screen, or a built-in app page. What happens when the member taps the tile. Content category opens that category’s article list in the app.

Drag rows to reorder tiles. Use Add grid item for new tiles. Each tile’s next action is independent—unlike Menu Screen, there is no shared body block above the list.

Instruction Screen

Uses a dedicated form:

  • Title — heading for the whole instruction sheet.
  • For each instruction step: title, description, bad image (example of what not to do), good image (example of what to do).

Members see a bottom sheet with horizontally scrollable good/bad examples—useful for photo or profile quality guidance.

Workflow

When the screen appears and what each button does afterward.

Trigger (when to show)

FieldWhat to chooseEffect
Trigger event One of the app-defined moments (welcome, after approve, no suggestions, settings, share-phone workflow, and others). When the member app reaches that moment, it looks up a published screen with the same event (and matching param/platform). If none exists, the app continues without showing your screen.
Param Free text. Required when multiple screens share one event—for example each step of the share-phone workflow uses the same event with a different param value. The app passes a param string at runtime; your screen matches when param is empty or equals that string.

Event catalog: Trigger events reference. Two picker options—Pre login end and Before delete profile—are inactive in the current member app; see inactive triggers before publishing.

Next events (button actions)

Next event runs when the member taps button 1. Next event 2 runs for button 2. Each has an event type and a target:

Event type (typical label)Target you pickWhat happens for the member
None—Button closes the screen; no follow-up navigation.
Generic screenAnother info screen by internal nameOpens that configured screen next.
App screenBuilt-in app page (home, settings, questionnaires, conversation, and so on)Navigates to that route in the member app.
Content screenPublished app content item (by category then name)Opens static app content—not a dynamic info screen.
GroupA user groupCan attach the member to that group (same family of actions as questionnaire post-actions).
ElementMe-tab element (premium, tasks, questionnaire, settings, support, and others)Scrolls or focuses that section on the Me page.
Back office linkInternal matchmaker link patternUsed in operator-facing flows embedded in app WebViews—not typical member marketing popups.
CustomNamed custom action (share, logout, break the ice, and others)Runs app-specific handler code tied to that action name.
Comm triggerTrigger or cancelStarts or cancels a linked communication template from a questionnaire answer action—advanced pairing with comms.
ShareParam textOpens the device share sheet when configured.
LambdaParam textServer-side custom function—used from questionnaire flows more often than standalone info screens.

Details and param notes: Next event types reference.

Platform Settings

FieldWhat to setEffect
Desktop image Wide hero image for web layouts. Shown on desktop web when the screen type supports a wide banner. Mobile preview may not reflect this asset.
Platforms (multi-select) Android, iOS, mobile web, desktop web—any combination. When set, only those platforms load this screen for the trigger event. Empty means all platforms.

Save, status, delete

ControlWhat happens
Save Writes the full screen row to the database (including field order and translations for your editing language). Does not push to members by itself.
Screen status chip / status control Switch between Draft, Active, and Deactive. Only Active rows export on list .
Delete Screen Permanent removal after confirmation. Published JSON updates only after the next publish without this id.

After saving and setting Active, return to the screens list and publish so members receive the change. Saving an existing screen sets a publish needed indicator on the list until you publish.

Audit history

At the bottom of the edit page, Audit log history lists changes to this screen record (who changed what and when). Use it when troubleshooting unexpected copy or workflow changes.

Create new screen

From the screens list, click Add to open /screens/new. Enter internal name and category, then Save to create the row. Admin navigates back to the list — open the new screen to configure content, workflow, and platforms before publishing.

New screens start as Draft. Set Active and publish from the list when ready.

Reference