FAQs

How do I stop users from accessing downloads ?

At times you may wish to stop certain users being able to access downloadable resources from your site. For example, you may allow paying subscribers to download reports, but not free accounts.

You can manage this within Zephr using a two phased approach – a feature rule to remove/disable the Download buttons on the front end, and a request rule to navigate users away from the resource.

Hiding the Download Button

  1. Create an entitlement – for example, ‘Download’
  2. Add the entitlement to the relevant bundles – for any users who will be allowed to download content.
  3. Create a UI component – for example ‘download-disabled’. Within this UI component, add the relevant paywall you would like users to see instead of the download button – this could be a paywall, or may just be a block to hide the button.
  4. Create a Feature Rule – for example ‘Download’.
  5. Within the rule, add an Entitlement check for your Download Entitlement. If yes, choose No Transformation. If no, choose UI Component, and select your download-disabled UI component. The rule should look similar to this:

  1. Copy the Zephr Feature Tags from the ‘Site Integration Tip’ and wrap these around the relevant download buttons within your CMS.

 

Redirecting from Resources

After hiding the download button, you may also wish to remove access to the sections of your site where downloadable content is hosted. For this, you will use request rules.

  1. Add a new Request Rule – for example ‘Download Content’
  2. Under Conditions, check ‘URL Path Matches’
  3. Enter the URL path for Downloadable content – ideally a pattern, e.g. ‘/downloads/*’ or this could be for a specific path.
  4. Within your rule, add an Entitlement check for your Download Entitlement. If yes, choose Allow (under Responses). If no, set what you would like the desired outcome to be – for example, you may wish to use a Simple Redirect to send users to a page that displays a paywall.

How do I stop users being able to copy and paste my content ?

Some companies wish to stop end users from being able to copy and paste the content on their site, which adds another layer of protection against users sharing content.

This can be done in Zephr using an entitlement, a UI component, and a feature rule:

  1. Create an entitlement – for example, ‘Copy and Paste’
  2. Add the entitlement to the relevant bundles – for any users who will be allowed to copy and paste.
  3. Create a UI Component – for example, ‘copy-and-paste’ and add the following script:

<script>

window.addEventListener(‘load’, function() {

window.body.addEventListener(‘copy’, function(e){

e.clipboardData.setData(‘text/plain’, ‘{{copy-paste-message}}’);

e.clipboardData.setData(‘text/html’, ‘{{copy-paste-message}}’);

e.preventDefault();

});

});

</script>

  1. Click Save.
  2. Create a Feature Rule – for example, ‘Copy and Paste’
  3. Within the rule, add an Entitlement check for your Copy and Paste Entitlement. If yes, choose No Transformation. If no, choose UI Component, and select your copy-and-paste UI component. The rule should look similar to this:

  1. Copy the Zephr Feature Tags from the ‘Site Integration Tip’ and add these to the body of all pages you wish to limit copy and paste access to.

 

Broken Feature Rules

In this FAQ we’ll answer questions around regular issues we see regarding broken Feature Rules.

Your Feature Rules need to be connected otherwise Zephr will view this as misconfiguration and “fail open” ie. all the content viewed via Zephr will be visible.

In order to make sure the Feature Rules are connected you’ll need to ensure the work flow is joined up without any in the admin console.

For example;

 

Correct!

Incorrect!

 

 

What is User Authentication by Email?

Zephr includes a feature allowing end-users to register and login to your site, via Zephr, without the need to enter a password.

This process works through the use of email verification – users logging into your site will enter their email address, and an email with an access link is sent. Clicking on this link redirects your users to your website, and logs them in.

The tokens generated for this access link are for single use only. If a user tries to use the link for a second time, they will receive an error and Zephr will not log them in. When configuring this feature, you can also choose how long a token is valid. If a User clicks on the link outside the token validity, they will not be logged in and will need to complete the process again.

Learn how to configure this functionality in our User Authentication by Email guide.

Why cant I see new pages published on my site ?

Zephr caches the content from your Origin website as a means of improving your site performance when making access decisions.

By default, website content is cached for 10 minutes, meaning updates made to your CMS will take up to 10 minutes to propagate to the end user.

In some cases, you may wish for this cache to be removed – for example, if you publish breaking news and want pages from /breaking-news to be excluded from the cache.

You can remove or exclude content from the cache by adding a Cache Rule, or by Invalidating the Origin Cache.

Can I reorder my User Schema ?

The Zephr User Schema determines the information that can be stored against a user’s profile in Zephr.

The order of the User Schema also determines the order in which you see this information on an individual user profile, and within the broader user list.

You can reorder this within the Identity Management section of your Admin Console. More details are available here.