Distribution and access control

Pages are designed to serve audiences beyond your team members already on Tines.

To get pages into the hands of these end users, you'll need to distribute them while ensuring secure access controls are established.

Distributing page URLs to users 

Pages which kick off Story runs 

For pages that kick off workflows – i.e. pages at the root of a Story without anything else upstream – a static URL is provided.

Use the link icon in the top right of the page on the diagram to copy its URL (or click to open in a new tab).

Downstream (mid-Story) pages 

Pages downstream of actions or other pages do not have static URLs. This is because they exist in the context of a particular Story run.

To get the dynamic URL for these pages, you can use the PAGE.page_name variable in Formulas expressions. This produces a link to the page, ready for sharing, in the context of the current Story run.

For example, you could add the page downstream of a Send Email Action, and include a link to the page in a Slack notification. Once the user accesses the link and submits the form on the page, the workflow will continue as usual:

Controlling end-user access 

By default, pages can only be loaded by those currently signed into the Tines tenant.

In total, there are three levels of access control that you can apply to each page:

  1. Private (default): only signed-in members of the Tines tenant can load the page (even if they’re on a different team within the tenant).

  2. SSO: anyone in your organization, authenticated with SSO, can load the page. Useful for company-wide access scenarios.

  3. Public: anyone with knowledge of the page URL can load and interact with pages.

Customize your page's access by selecting it and scrolling to the bottom of the configuration sidebar.

Was this helpful?