Knowledge Base

Prerequisites

• Access to a Ligantic Space with ADMIN role

Overview

Making a Space publicly accessible involves:

1. Configure a Space Name (for the subdomain URL)
2. Create a Space Role for public visitors
3. Create a Guest authentication strategy
4. (Optional) Configure a custom domain

Once configured, any Experience granted to the public role can be accessed without authentication.

Step 1: Configure a Space Name

The Space Name determines your public subdomain URL (https://{space-name}.ligantic.app/).

1. Go to 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://{space-name}.ligantic.app/.

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

Step 2: Create a Space Role for Public Visitors

Space Roles define what capabilities public users have.

1. Go to Space Settings → Auth
2. In the Space Roles section, click to create a new role
3. Give the role a descriptive name (e.g., "Public Visitor" or "Guest User")
4. Configure capabilities for the role:
   • Experience: Grant read access to Experiences you want to be 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.

Step 3: Create a Guest Authentication Strategy

A Guest strategy allows unauthenticated access to your Space.

1. Go to Space Settings → Auth → Create Strategy
2. Choose Guest as the authentication type
3. Configure the strategy:
   • Name: A descriptive name (e.g., "Public Access")
   • Default Space Role: Select the role you created in Step 2
4. Save the strategy

Public users will now be automatically assigned the Guest role when accessing your Experiences.

Step 4: Configure a Custom Domain (Optional)

For a branded URL like https://app.yourcompany.com:

Configure DNS First

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

• Option A (CNAME/ALIAS): Point your domain to{space-name}.ligantic.app
• Option B (A Record): Point your domain to the Ligantic IP address (shown on the create domain page)

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

--------------

Add the Domain in Ligantic

1. Go to Space Settings → Domains
2. Click Create Domain
3. Enter your domain name (e.g.,app.yourcompany.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)

Once verified, your Experiences will be accessible at https://app.yourcompany.com/{pathname}.

Troubleshooting

Public URLs not working

• Verify that the Space has a Name configured
• Confirm 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