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:

Customizing the URL 

A page URL looks like https://tenant.tines.com/pages/url-identifier/dynamic-identifier. By default, the url-identifier is a randomly generated string. It must be unique to the tenant to ensure that your users can find it.

You can provide your own url identifier to customize where your users can find it, e.g. analyze-email. Be cautious, for this may break existing bookmarks. If changing the url identifier of an existing page, consider using another page to redirect users from the old identifier to the new one.

The dynamic-identifier is generated in the context of a story run (i.e. downstream pages) and cannot be customized.

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. Only team members (default): only signed-in members of the team that the page is in can load the page

  2. Members of this Tines tenant: anyone signed into the Tines tenant can load the page (even if they’re not a member of the page's own team).

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

  4. Via SSO authentication: anyone in your organization granted access to the Tines app on the SSO provider can load the page. Useful for company-wide access scenarios. It's possible to add a further layer of granularity by restricting access to a particular group:

    • Firstly, an admin needs to turn this feature on in the Authentication settings

    • Then select Via SSO Authentication under the access options of your page, enable Restrict to specific SSO groups and type a comma-separated list of SSO group names into the field below.

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

Was this helpful?