Ligantic
Knowledge Base
Tutorials
Updates
Search Articles
Login
Free Sign Up
Home
Get Started
Tutorials
How-to guides
Reference
Explanation
Spaces
Schemas
Flows
Experiences
Endpoints
SDK and CLI
Browse documentation
Home
Get Started
Spaces
Schemas
Flows
Experiences
Endpoints
SDK and CLI
Docs
/

How to Configure a Space for Public Access

This guide shows you how to configure a Ligantic Space so that its Experiences can be accessed by the public (unauthenticated users).

Prerequisites

  • Access to a Space with the ADMIN role

Configure a Space Name

The Space Name determines your public subdomain URL (https://<spaceName>.ligantic.app/).

  1. Open Space Settings (gear icon in the Space navigation)
  2. Find the Name field
  3. Enter a unique, URL-friendly name:

    • Use lowercase letters, numbers, and hyphens only
    • The name must be globally unique across all Ligantic Spaces
  4. Save the changes

Your Space will now be accessible at https://<spaceName>.ligantic.app/.

Tip: You can generate a random name for the Space using the button next to the Name field.

Create a Space Role for Public Visitors

Space Roles define what capabilities public users have. For every capability, action, and read filter, see Space Roles and Permissions.

  1. Open Space Settings → Auth
  2. In the Roles section, click Create Role
  3. Give the role a descriptive name (for example, "Public Visitor" or "Guest User")
  4. Configure capabilities for the role:

    • Experience — Grant read access to Experiences you want publicly accessible
    • Schema — Grant appropriate access if Experiences read or write data
    • Flow — Grant execute access if Experiences trigger any Flows
  5. Save the role

Tip: Start with minimal permissions and add more as needed. You can update the role's Experience access as you publish new Experiences.

Create a Guest Authentication Strategy

A Guest strategy allows unauthenticated access to your Space.

  1. Open Space Settings → Auth, then click Create Strategy
  2. Select Guest as the authentication type
  3. Configure the strategy:

    • Name — A descriptive name (for example, "Public Access")
    • Default Space Role — Select the role you created in Create a Space Role for Public Visitors
  4. Save the strategy

Result: Public users will now be automatically assigned the Guest role when accessing your Experiences. Once configured, any Experience granted to the public role can be accessed without authentication.

Configure a Custom Domain (Optional)

For a branded URL, such as https://app.example.com:

Configure DNS First

Before adding the domain in Ligantic, configure your DNS provider:

  • Option A (CNAME/ALIAS) — Point your domain to <spaceName>.ligantic.app
  • Option B (A Record) — Point your domain to the Ligantic IP address (shown on the create domain page)

Tip: Prefer using a CNAME/ALIAS so you won't need to update the Ligantic IP address in the future.

Add the Domain in Ligantic

  1. Open Space Settings → Domains
  2. Click Create Domain
  3. Enter your domain name (for example, app.example.com)
  4. Click Create Domain
  5. Wait for domain verification

Domain Verification

  • Ligantic automatically attempts to verify your domain
  • Verification may take a few minutes depending on DNS propagation
  • Check the domain status on the Domains settings page
  • If verification fails, check your DNS configuration and try again
  • DNS propagation can take up to 48 hours (typically much faster)

Result: Once verified, your Experiences will be accessible at https://app.example.com/<pathname>.

Troubleshooting

Public URLs Not Working

  • Verify the Space has a Name configured
  • Confirm a Guest authentication strategy exists
  • Check that the Space Role has read access to the Experience

Custom Domain Not Working

  • Verify DNS records are correctly configured
  • Check domain verification status in Space Settings → Domains
  • Ensure SSL certificate has been provisioned (automatic after verification)

Users Seeing "404"

  • Confirm the Guest strategy is using the correct Space Role
  • Verify the Space Role grants read access to the specific Experience
  • Check that any required Schema or Flow permissions are granted

Related pages

How to Publish an Experience to the Public
This guide shows you how to publish an Experience in Ligantic so that it's publicly accessible to end-users.
Page not found. It may have moved or may not be published.
Browse documentation