Our goal is to redirect users who have Skuid permissions to custom Skuid pages for both the New and View actions for the standard Case object, while pointing users who don’t have Skuid permissions to the standard page layout.

We have active page assignments created for each page and have overridden the New and View actions on the Case object with our Visualforce pages. We have also cloned the managed Skuid permission sets, made local versions and assigned a Skuid Page Viewer permission set to a test user.

As we test, regardless of having the Skuid permission, the test user is redirected to the standard New Case page layout with this code:

<apex:page standardController=“Case” extensions=“skuid.Redirects” showHeader=“true” sidebar=“false” readonly=“true” docType=“html-5.0”

action=“{!IF(canUseSkuid,‘’,redirect)}” title=“New Case”>

<skuid:page objecttype=“Case” actiontype=“New”/>

</apex:page>

If we replace <skuid:page objecttype=“Case” actiontype=“New”/> with:

<skuid:page page=‘CRM-NewCasePage’/>

It loads the custom Skuid page regardless of having the Skuid permission set.

We’ve tried changing the org wide default for Page and Page Layout to Public Read Only, but it hasn’t had any effect.

What does canUseSkuid look at to determine access to Skuid?

Any help is appreciated!