Skuid NLX: Quickstart

Register for Skuid NLX

To get started with an NLX site, you’ll need to request a developer account from the Skuid website.

After submitting this form, you’ll be contacted by a Skuid rep to continue your registration. When registering a Skuid site, you’ll need to provide some basic information for your first admin user and the site itself:

  • First Name: First name of the user.

  • Last Name: Last name of the user.

  • Email Address: Must be an email account you have access to. If not, then you will not be able to access your verification link!

  • Company Name: A name you will use to identify the site. This is not used to create the URL or domain for your site, so you can feel free to be more descriptive or creative with your site name.

    For example: Glacier Ice Cubes, Inc.

  • User Name: A name (does NOT have to be based on an email address format) that your users will remember and that meets your organization’s standards for a username.

  • Subdomain: A name that will be used to create a URL for your site. Choose something URL friendly! For example, if you choose ‘glacier’ for your subdomain, then the URL for your site would look like this:


    If your site is fully activated, the us-trial section may not be in your URL.

  • Region: Select the region you where you want to create your Skuid site. For more information, see What are regions, and what do they mean for my Skuid site?

Log in to Skuid

To log in to your Skuid NLX site, navigate to your site’s URL, which will be a combination of your subdomain with appended to it.

For example, if you registered your subdomain as glacier, then your login link would be:


General Questions

What are regions, and what do they mean for my Skuid site?

When you create a Skuid site, you can select the region in which the site will be hosted. Choosing the correct region can help reduce data latency―the time it takes for requested data to be returned―and decrease page load time.

Additionally, some companies (as well as some countries) have specific regulatory requirements about data storage and security; selecting the correct region for your site makes it easier adhere to these regulations.

How it works

When you create a Skuid site by selecting a subdomain and a region, Skuid creates the site only in the specified region. The site is not replicated in other regions. The Skuid site only exists on the specified region’s servers and will not be automatically deployed to other sites that you create in other regions.

One site cannot be served on more than one region, and sites cannot be moved from one region to another.

Best practices

  • When possible, choose the region closest to where your data source is hosted, even if the bulk of your end users will be in another region.
    • For example, if 30% of your users are in the US and 70% are in EMEA, it might seem logical to host your Skuid site from the European region. But if your data source is hosted in the US, choosing the US region will reduce overall data latency.
    • However, you may need to balance page load needs with security or regulatory requirements.


If the current regional options do not meet your location requirements, please talk to your Skuid account representative.

How is security enforced on Skuid NLX?

Security in Skuid NLX is enforced at a per-user level. There are permission set <permissions>` that can be given to an end user to limit / extend permissions to different functionality in Skuid NLX, such as access to data sources, apps, and more.

How does Skuid NLX allow users to access their data from other external systems?

Skuid NLX works with multiple external systems-we call them data sources. Some of the external systems supported include Microsoft Dynamics, Salesforce, Google Calendar, Google Drive, and others—as well as systems accessible through OData and REST APIs.

Skuid does not have its own database. So you must configure a data source to experience the power of Skuid’s custom UI. Here are some examples that may get you started:

Can I import themes created in Skuid SFX into Skuid NLX?

Yes, you can import themes created in Skuid SFX to Skuid NLX but cannot yet bulk-import pages or other asset types.

Can I use “static resources?”

Skuid NLX allows users to upload static file content (such as images, JavaScript or CSS resources, etc.) in the Files tab in the Site navigation. Files can be uploaded by clicking clicking Upload new File.

Within the App Composer, uploaded files can be selected as an image source for Image and Wrapper components, as well as a source for JavaScript and CSS resources. Internally, the Skuid NLX stores themes and component packs within Files.


Can I assign certain pages to specific site permission sets and end users in Skuid NLX? Does Skuid NLX recognize existing assignments from other systems?

While Skuid works with multiple external systems, there may be some features supported by the originating system that are not duplicated in Skuid NLX―but corresponding Skuid features that address the same issue.

For example, Skuid NLX doesn’t use Salesforce features such as page assignments, overrides, Salesforce apps, tabs, or communities. These features are replaced by apps and pages. Within Skuid NLX, an app is a collection of pages that share a base URL, called the App URL slug. This “shared” URL allows end users to view all the Skuid pages that comprise the app.

Data access permissions, however, are preserved on Skuid NLX. End users cannot circumvent data model permissions using Skuid.

Is it possible to use sandboxes with Skuid NLX?

Yes it is. See Sandbox Deployments.


What kind of support tools are available on Skuid NLX?

Currently, there are no support tools (such as “Login as”) available, but we plan to provide that in a future release.

I cannot access data from a Salesforce org within my Skuid site

If you are an international user, it may be necessary to relax the Salesforce Connected App’s IP Restrictions within its OAuth settings. To do so:

  1. In the Salesforce sidebar, navigate to Build > Create > Apps.
  2. Click Manage beside the Connected App used for the data source.
  3. Click Edit Policies.
    • Beside IP Relaxation, select Relax IP restrictions with second factor or Relax IP restrictions.
  4. The Salesforce data source type in Skuid NLX will not work for source orgs with versions of Skuid lower than 8.15.4. Consider updating the version of Skuid within your Salesforce org.

Known Limitations

This release includes the following incomplete features, which will be resolved in future Skuid releases.

  • New Page templates: Skuid NLX does not currently support creating a new page from a page template.
  • Per-Profile and Per-User credentials: Used for Basic HTTP Authentication in Skuid data sources, this credential source option will be available in a future Skuid NLX update.
    • The Shared by all Site Users and Per User, with optional shared Site-wide Defaults credential source options are available and work as intended.


Visit to ask questions, share ideas, and report problems.