Skip to main content
See a demo

Enterprise Rollout

The Enterprise plan changes two things compared to Basic and Business: the Owner becomes a dedicated compliance role, and IT admins get more options for deploying Lora at scale. This page covers both: what the plan unlocks for the Owner, and the ways IT can roll Lora out to a fleet of devices.

Owner as the compliance role

On Free, Basic, and Business, the Owner acts as the first Admin with one extra rule: only the Owner can delete the workspace. Enterprise tightens that by moving a cluster of compliance and security responsibilities to Owner-only.

Under Enterprise, only the Owner can:

  • Manage billing. Admins lose billing access. This separation is what most procurement and finance teams want, since the person paying isn’t necessarily the person running the workspace day-to-day.
  • Read the audit log. A timestamped record of who did what in the workspace.
  • Export the workspace. A full export of shortcuts, members, and audit-log data, for compliance reviews or contract exits.
  • Approve OAuth apps. Third-party apps that request access to the workspace come to the Owner for approval before they can connect.
  • Change security settings. Enforce two-factor authentication for every member and restrict sign-ins to an IP allowlist.

On every plan, the Owner is also the only role that can delete the workspace.

If the current Owner of a workspace upgrading to Enterprise isn’t the right Compliance Owner, transfer ownership before flipping the plan. Otherwise the wrong person ends up holding the keys.

Downgrading from Enterprise to Business gives Admins back their billing access. The other Enterprise-only capabilities (audit log, exports, OAuth approvals, security settings) become unavailable until you upgrade again. The records they produced aren’t deleted; they’re preserved against a future re-upgrade.

Deploying Lora at scale

The rest of this page is for IT admins rolling Lora out across an organization. Pick the deployment method that fits your policies and infrastructure. Most teams combine the browser extension with a DNS setup so shortcuts work in and out of the corporate network.

The recommended way to roll out Lora is by deploying the browser extension to all employees through Chrome Enterprise or Microsoft Edge.

With this approach, users automatically receive the Lora extension in their browser, with no manual steps required.

Custom search engine

If your company prefers not to install extensions, you can configure Lora as a custom search engine in Chrome, Edge, or Firefox.

Steps (Chrome)

  1. Open Settings → Search engine → Manage search engines and site search.
  2. Under Site search, click Add.
  3. Enter:
    • Name: Lora
    • Shortcut: short
    • URL: https://app.uselora.com/s/%s
  4. Save.

Now typing short handbook in the address bar will search directly in Lora.

Note: The same values (Name: Lora, Shortcut: short, URL: https://app.uselora.com/s/%s) work for Edge as well. In Edge, find settings under Settings → Privacy, search, and services → Address bar and search. Firefox does not offer a direct UI to add custom search engines. To use Lora in Firefox, you can install a browser add-on that supports custom search keywords, or use advanced configuration methods. See Mozilla’s documentation on search engines for more information.

Domain search allows users to type shortcuts without a prefix. With the search domain lora-searchdomain.com configured, typing handbook in the browser bar will resolve to handbook.lora-searchdomain.com and redirect through your Lora workspace.

Steps

  • macOS: Configure the search domain under System Settings → Network → DNS → Search Domains → add lora-searchdomain.com.
  • Windows: Add the DNS suffix under Network Adapter Properties → IPv4 → Advanced → DNS → add lora-searchdomain.com.
  • Managed devices: Push the setting with MDM (JAMF or Intune).

Internal DNS entry

Note: Internal DNS entry is only available on paid plans. Contact our team to enable this feature for your workspace.

An internal DNS entry allows employees to type shortcuts like http://short/handbook directly into their browser and resolve them through your company’s network — no browser extension required.

How it works

By creating an A record in your internal DNS, you point a short hostname (commonly short) to Lora’s infrastructure IP address. The IP address to use is shown in your workspace settings. When employees type http://short/slug, DNS resolves it directly to Lora, which routes the request to your workspace.

Steps

  1. Open your internal DNS settings.
  2. Create a new A record:
    • Name: short
    • IP Address: (provided by Lora in your workspace settings, e.g., 203.0.113.x)
  3. Save the record and apply changes to your DNS server.
  4. Have employees type http://short/ in their browser once to initialize resolution.
  5. After that, shortcuts like http://short/handbook will resolve automatically on your network.

Do I still need the extension?

  • With an internal DNS entry, shortcuts work seamlessly inside your corporate network.
  • We still recommend installing the Lora extension, because it enables:
    • Using shortcuts outside the corporate network (remote, mobile, travel).
    • Features like autocomplete, quick create, and advanced shortcut options.

Tailscale VPN

If your organization uses Tailscale, you can route shortcut resolution through your VPN.

  • Enable MagicDNS in Tailscale.
  • Configure it to resolve lora-searchdomain.com.
  • Push the settings to all devices connected to your tailnet.

Domain push via MDM (JAMF / Intune)

For enterprise customers, Lora supports rolling out search domain settings and browser configuration via Mobile Device Management (MDM). This allows IT admins to deploy Lora across all company devices without manual setup by end users.

Benefits

  • Seamless rollout of Lora to all managed devices
  • New employees get access to Lora immediately when their device is enrolled
  • Prevents workflow disruption — no need for users to configure settings manually
  • Works in incognito/private browsing windows
  • No VPN required — accessible from anywhere once deployed

Considerations

  • If a user accesses shortcuts in incognito mode, they may be prompted to sign in before continuing.
  • Device enrollment in JAMF or Intune is required for configuration to apply.

JAMF (macOS)

With JAMF, you can push configuration profiles to all managed macOS devices.

  • Search domain: Add lora-searchdomain.com to DNS Search Domains.
  • Browser extension: Push the Lora Chrome/Edge extension via the ExtensionInstallForcelist payload. Use extension IDs: Chrome: cacmbfiiigpjpiflidcnoclhlmonanoj (Chrome Web Store) or Edge: hkdichcogemmndpjbjchlbfacedihefc (Edge Add-ons).
  • Custom search engine (optional): Deploy a managed search engine configuration with keyword short and URL https://app.uselora.com/s/%s.

Steps

  1. Open JAMF Pro → Configuration Profiles → New.
  2. Select Wi-Fi or Network payload and add DNS Search Domains → lora-searchdomain.com.
  3. Add an Application & Custom Settings payload for Chrome or Edge to install the Lora extension.
  4. Save and assign the profile to your target devices or groups.

Intune (Windows)

With Microsoft Intune, you can push device configuration policies to all managed Windows clients.

  • Search domain: Add lora-searchdomain.com as a DNS suffix in device configuration.
  • Browser extension: Force-install the Lora extension in Chrome or Edge via settings catalog. Use extension IDs: Chrome: cacmbfiiigpjpiflidcnoclhlmonanoj (Chrome Web Store) or Edge: hkdichcogemmndpjbjchlbfacedihefc (Edge Add-ons).
  • Custom search engine (optional): Configure managed search engines with keyword short and URL https://app.uselora.com/s/%s.

Steps

  1. Open Intune admin center → Devices → Configuration profiles → Create profile.
  2. Select Windows 10/11 → Settings catalog.
  3. Add settings for:
    • DNS suffix → lora-searchdomain.com
    • Microsoft Edge / Chrome Extensions → Add the Lora extension ID: Chrome: cacmbfiiigpjpiflidcnoclhlmonanoj (Chrome Web Store) or Edge: hkdichcogemmndpjbjchlbfacedihefc (Edge Add-ons)
    • Managed search engine (optional)
  4. Assign the profile to device/user groups.
  5. Save and sync policy to apply.