Skip to Content
ConfigurationSystem Settings

Last Updated: 3/9/2026

System Settings

System Settings control application-wide configuration and affect all users. Only administrators can access and modify these settings.

Access: Username dropdown → System Settings

Update Checks

LinkAce automatically checks for new releases when you visit the System Settings page.

How it works:

  • Pulls the latest release information from GitHub
  • Compares it to your installed version
  • Displays an alert if a newer version is available

Action: Click the update alert to view the release notes  and upgrade guide.

System Cron

The cron job is required for automation features. Without it, the following will not work:

  • ❌ Wayback Machine archiving
  • ❌ Automated link health checks
  • ❌ Scheduled backups
  • ❌ Cleanup tasks (old logs, trashed items)

Cron Token

The cron token authenticates your cron script against LinkAce, preventing unauthorized access.

Location: System Settings → Cron section

What you’ll see:

  • Cron Token: A unique secret (e.g., WPvv4mxM6nr22Aq4rVf1qEKutsXLTgyw)
  • Pre-built Cron URL: The full URL to call (e.g., https://linkace.com/cron/WPvv4mxM6nr22Aq4rVf1qEKutsXLTgyw)

Setting Up the Cron

The cron must run every minute and call the provided URL.

For Docker Installations

Option 1: Host crontab

crontab -e

Add this line (replace with your URL):

* * * * * curl -s https://linkace.com/cron/WPvv4mxM6nr22Aq4rVf1qEKutsXLTgyw > /dev/null 2>&1

Option 2: Inside Docker container

* * * * * docker exec linkace-app-1 php artisan schedule:run > /dev/null 2>&1

For PHP Installations

crontab -e

Add this line (adjust path):

* * * * * cd /path/to/linkace && php artisan schedule:run > /dev/null 2>&1

Using a Cron Service

If your server doesn’t support cron, use a free service:

Configure the service to call your cron URL every minute.

Regenerating the Cron Token

If the token is compromised or you’re troubleshooting cron issues:

  1. Click “Generate Token” next to the token field
  2. Update your cron with the new URL
  3. Save changes

Warning: The old token will stop working immediately.

Verifying the Cron is Working

  1. Wait 2-3 minutes after setting up the cron
  2. Check System Logs: Username dropdown → System Logs
  3. Look for entries like: 
    [timestamp] Cron job executed successfully
[timestamp] Link checks scheduled: 5 links queued
[timestamp] Wayback Machine: 3 links submitted

If you don’t see cron logs:

  • Verify the cron URL is correct
  • Test the URL manually in your browser (should return “OK”)
  • Check your server’s cron logs
  • Ensure your server can reach the LinkAce URL

See Post-Installation for detailed troubleshooting.

General Settings

Page Title

Customize the browser tab title for your LinkAce instance.

Default: “LinkAce”
Example: “Acme Corp Bookmarks”, “Team Knowledge Base”

How to change:

  1. Enter your custom title in the “Page Title” field
  2. Click “Save”
  3. Refresh your browser to see the change

Custom Logo Text

Replace the LinkAce logo in the navigation bar with custom text (max 20 characters).

Use cases:

  • Company name: “Acme Corp”
  • Team name: “Engineering”
  • Personal branding: “John’s Links”

How to change:

  1. Enter your text in the “Custom Logo Text” field
  2. Click “Save”

Leave blank to show the default LinkAce logo.

Add a custom link to the footer (e.g., company website, privacy policy, contact page).

Requirements:

  • URL (must include http:// or https://)
  • Link text (max 20 characters)

Example:

  • URL: https://acme.com/privacy
  • Text: “Privacy Policy”

How to add:

  1. Enter the URL and text
  2. Click “Save”

The link will appear next to “LinkAce is a project by Kovah.de”.

Contact/About Page

Enable a custom contact or about page accessible from the footer.

Features:

  • Supports Markdown formatting
  • Max 10,000 characters
  • Accessible at /contact or via footer link

Use cases:

  • “About this bookmark collection”
  • “How to contribute”
  • “Contact the admin”

How to enable:

  1. Check “Enable Contact Page”
  2. Enter your content (Markdown supported)
  3. Click “Save”

The page will appear as “Contact” in the footer.

Custom Header Content

Inject custom HTML/JavaScript into the <head> tag of every page.

Use cases:

  • Analytics scripts (Google Analytics, Plausible)
  • Custom CSS for branding
  • Favicon overrides
  • Third-party integrations

Example:

<!-- Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'G-XXXXXXXXXX');
</script>
 
<!-- Custom CSS -->
<style>
  .navbar { background-color: #1e3a8a; }
</style>

Warning: Content is not escaped and may break your site if invalid. Test changes carefully.

Guest Access

Guest Access controls whether unauthenticated users can browse your LinkAce instance.

Enable Guest Access

When enabled, guests (not logged in) can:

  • View Public links, lists, and tags
  • Search Public content
  • Access Public RSS feeds
  • Browse the dashboard

When disabled, all pages require login.

What Guests Cannot Do

  • View Internal or Private content
  • Add, edit, or delete links
  • Access user settings or system settings
  • View other users’ private collections

Use Cases

Enable Guest Access:

  • Public bookmark collections
  • Open knowledge bases
  • Community resources
  • Portfolio or showcase sites

Disable Guest Access:

  • Private personal bookmarks
  • Internal team resources
  • Sensitive company data
  • Family-only collections

Guest Settings

When Guest Access is enabled, you can configure default settings for all guests:

Display Preferences:

  • Timezone: Default timezone for timestamps
  • Date format: YYYY-MM-DD, DD/MM/YYYY, MM/DD/YYYY
  • Time format: 12-hour or 24-hour
  • Language: Default interface language

Link Display:

  • Default view: Compact list, detailed list, or cards
  • Links per page: Pagination (default: 24)

Note: Individual logged-in users can override these in their User Settings.

Automated monitoring to detect broken or moved links.

When enabled, LinkAce will:

  • Regularly check all links (HTTP requests)
  • Mark links as OK, Moved, or Broken
  • Notify link owners of issues

When disabled, no health checks are performed.

Check Frequency

How often each link is checked:

  • Every day: High-frequency monitoring (resource-intensive)
  • Every 3 days: Balanced approach
  • Every 7 days: Low-frequency (recommended for most users)
  • Every 14 days: Minimal monitoring
  • Every 30 days: Very infrequent

Recommendation: Start with every 7 days and adjust based on your needs and server resources.

Notifications

Email Notifications:

  • Sent to link owners when their links break or move
  • Requires email configuration
  • Can be disabled per user in User Settings

In-App Notifications:

  • Dashboard alerts for broken links
  • Visible on the link detail page

Some sites (e.g., those with Cloudflare captchas) may fail health checks even when accessible.

To disable checks for a link:

  1. Open the link detail page
  2. Click “Disable Check”

The link will be excluded from future checks.

Requirements

  • Cron job must be configured (see above)
  • Email must be configured for notifications

Wayback Machine Archiving

Automatically archive links to the Internet Archive.

Enable Archiving

When enabled, LinkAce will:

  • Send newly added HTTP(S) links to the Wayback Machine
  • Schedule archiving (may take minutes to hours)
  • Display archive links on link detail pages

When disabled, no archiving is performed.

How It Works

  1. User saves a link
  2. LinkAce queues the link for archiving
  3. Cron job sends the URL to archive.org
  4. Wayback Machine crawls and archives the page
  5. Archived version becomes accessible at https://web.archive.org/web/*/[url]

Limitations

  • Some sites block archiving via robots.txt
  • Archiving is not instant (can take hours)
  • Only HTTP(S) links are supported (not FTP, SSH, etc.)

Requirements

  • Cron job must be configured (see above)

Application Backups

Schedule automated backups of your database and uploaded files to S3-compatible storage.

Enable Backups

When enabled, LinkAce will:

  • Create daily backups at a specified time
  • Upload to S3-compatible storage (AWS S3, Backblaze B2, DigitalOcean Spaces, MinIO)
  • Encrypt backups with a password
  • Clean up old backups based on retention settings

When disabled, no automated backups are performed.

Configuration

Backup Time:

  • Set the hour (0-23) when backups should run
  • Example: 2 = 2:00 AM in your server’s timezone

Retention:

  • How many days to keep backups
  • Example: 30 = keep backups for 30 days, then delete

Storage Configuration:

Notifications

Email Notifications:

  • Sent to administrators when backups fail
  • Can be disabled in System Settings

Requirements

  • Cron job must be configured (see above)
  • S3 credentials must be set in .env file
  • Email must be configured for failure notifications

Privacy Defaults

Set default visibility for newly created content.

Default Visibility

Choose the default visibility for new links, lists, and tags:

  • Public: Visible to everyone (including guests if enabled)
  • Internal: Visible only to logged-in users
  • Private: Visible only to the creator

Recommendation:

  • Public for open bookmark collections
  • Internal for team resources
  • Private for personal bookmarks

Note: Users can override this when creating content.

Guest Registration

Allow or disable self-registration for new users.

When enabled:

  • A “Register” link appears on the login page
  • Anyone can create an account
  • New users have regular user permissions (not admin)

When disabled:

  • Only administrators can invite users via User Management

Recommendation: Disable for private or team deployments, enable for public communities.

Advanced Settings

Some configuration options are only available via the .env file, including:

  • Database connection settings
  • Redis configuration
  • Email provider details
  • S3 backup credentials
  • OAuth/OIDC SSO providers
  • Performance tuning (cache, queue workers)
  • Security settings (session lifetime, rate limiting)

See Environment Variables for the complete reference.

Troubleshooting

Cron Not Working

  1. Test the cron URL manually: Visit it in your browser (should return “OK”)
  2. Check server cron logs: Look for errors
  3. Verify the token: Ensure it matches System Settings
  4. Check firewall: Ensure your server can reach the LinkAce URL

Guest Access Not Working

  1. Verify Guest Access is enabled in System Settings
  2. Check link visibility: Only Public links are visible to guests
  3. Clear cache: Restart Docker containers or run php artisan cache:clear

Backups Failing

  1. Check S3 credentials in .env file
  2. Verify bucket permissions: Ensure write access
  3. Check System Logs: Username dropdown → System Logs
  4. Test manually: Run php artisan backup:run (or via Docker)

For more help, see the Troubleshooting guide.

Next Steps

Single Sign On (SSO)Troubleshooting