Mike, good question. Assuming that the user has access to the Visualforce page that you’ve created to perform the override logic, and that you’re using “skuid.Redirects” as the extension class that performs the redirect logic, then by default, what would happen is that, if the user does not have a Skuid license, they’ll get an error — if they DO have a Skuid license, they’ll get redirected appropriately. This is an unavoidable consequence of the fact that the user is accessing code included in a managed package. However, fortunately, there is a way to avoid this. If you add a local version of this Redirects class, your users who do NOT have Skuid licenses (yet will be invisibly redirected to the appropriate Standard / Default Salesforce view, instead of the view that they would be served by Skuid. HOW TO DO THIS: 1. Add this Apex class into your org (either through Force.com IDE, a change set from a Sandbox, or Migration Tool). 2. Once the class is deployed, go to the Visualforce override page you created for the Opportunity object’s view action. Find extensions=“skuid.Redirects” and replace it with extensions=“Redirects” (that is, telling the page to use your local Redirects class instead of Skuid’s Redirects class. Save the Visualforce page. 3. Result → your users who don’t have Skuid licenses yet should be redirected to standard Salesforce pages. Once they have Skuid licenses, normal Skuid behavior will occur.

There’s now a new tutorial walking you through this process.

Update: In recent months we have updated skuid so that if you are using overrides to send Skuid users to skuid pages, users who do not have Skuid licenses will recieve the standard layouts associated with thier profile. No errors, no apex, no fuss.