Skip to main content

Adding triggers

Let RFID tags, sensors and other systems switch scenes or show and hide assets.

New in Release 5: triggers open from the top bar and work the same way as on-click actions: choose the action, then the targets. Organisations move to Release 5 on their release weekend, from 9 October.

Not on Release 5 yet? Until your organisation moves over, use Adding triggers (before Release 5).

Triggers let the physical space control your story. An RFID tag, a sensor or a signal from another system can switch scenes or show and hide assets.

Before you start

An Administrator first creates the triggers in Settings > Triggers and assigns them to your setup (see Trigger management). After that, a Triggers button appears in the top bar of the Composer. The Composer shows the triggers of the story's Base Setup.

Add a trigger event

  1. In the top bar, click Triggers. The triggers panel opens.

  2. Click Add trigger action and choose the Trigger.

  3. Choose the action:

    • Go to: switch to a scene.

    • Toggle visibility: show or hide assets.

  4. Choose the targets. Use Add target to add more.

  5. Close the panel. Your changes are saved automatically.

Targets

  • Go to switches one scene per screen. Picking another scene on the same screen replaces the first; picking it again removes it. To switch several screens at once, add a target on each screen.

  • Toggle visibility can show and hide many assets, on any screen and in any scene.

  • One trigger event can't mix Go to and Toggle visibility.

  • Targets on a screensaver scene are ignored when the story is published.

Edit or delete a trigger event

Each trigger event shows as a summary card in the triggers panel. Click the card to edit the trigger event or delete it.

Good to know

  • Each trigger can be used in one trigger event per story. Triggers already in use are greyed out in the list.

  • Only one person can edit triggers at a time. While a collaborator has the panel open, the Triggers button shows "This feature is currently used by another collaborator".

  • Existing triggers keep working on TSS Play exactly as before; only the way you set them up has changed.

  • When you duplicate a story for a setup that doesn't have the same triggers, Compose warns you that some triggers aren't available for that setup.

Did this answer your question?