What are Tines Pages and when should I use them?

Tines Stories: Ask + Answer
1

I keep seeing Pages mentioned in Tines content and I have a rough sense they’re related to human interaction in workflows, but I’m not totally clear on what they actually are or when they’re the right tool. Can someone explain what Pages are, what they can do, and what kinds of problems they’re best suited to?

2

Pages are Tines’ built-in way to create web-based interfaces that connect people to your stories. They let you build forms, approval screens, and simple dashboards without needing any external tooling.

What they actually are

A Page is a web UI you design inside Tines using a drag-and-drop editor. You can add form fields, text, images, tables, and buttons. When someone interacts with a Page (submits a form, clicks an approval button), that interaction triggers actions in your story, passing the submitted data along as an event.

What you can do with them:

  • Intake forms. Let users submit requests (access requests, incident reports, onboarding info) without needing to know anything about your story.
  • Approval workflows. Present a summary of something that needs a decision and give the approver Accept/Reject buttons.
  • Self-service tools. Give non-technical teammates a clean interface to kick off automations they’d otherwise need to ask you to run.
  • Status displays. Show tables or summaries of data pulled from your stories.

When to use them

Pages are great when your story needs human input or decision-making at some point in the flow. If your workflow is fully automated end-to-end, you probably don’t need one. But any time you’re thinking “I need someone to fill something in” or “someone needs to approve this before it continues,” that’s a Page.

They’re also useful when you want to give people access to trigger a story without giving them access to the story itself. You can share a Page URL with anyone (or restrict it with SSO), and they interact with a clean UI rather than the story builder.

Things worth knowing:

  • Pages are part of the story they belong to, so permissions follow the same model.
  • You can control access to a Page: public, anyone in your tenant, or restricted to specific groups.
  • They support conditional logic for showing/hiding fields based on previous inputs.