KB: Author License Seat Unavailable or Stuck in Altium Designer Develop

Altium Designer Altium Designer
When Altium Designer Develop connects to a Workspace, it automatically claims an available author license seat and releases it when the user signs out properly. Interruptions such as network instability, crashes, system sleep, or session conflicts can prevent a clean release, causing the seat to appear in use or unavailable. This can result in losing access to an author seat during work or receiving messages that no seats are available. This article explains common symptoms, the underlying causes including connectivity validation behavior and session handling, and the actions users and Workspace administrators can take to recover the license safely. It also includes recommended practices such as autosave configuration, browser/session hygiene, and the use of roaming (reserved) seats to reduce the impact of recurring interruptions.

Solution Details

Author seat appears unavailable or lost

Users may see messages stating that no authoring seats are available, or Altium Designer Develop may lose its author license while the application remains open. In some cases, the Workspace web portal may show the user as Taken Online or with a Reserved Seat even though the client is not actively using it. Closing the program in this state can result in loss of unsaved work.

Interrupted validation and session inconsistencies

This issue occurs when the client cannot maintain a stable connection with the Workspace, preventing proper license validation and release. Causes can include network instability, blocked traffic, system sleep, or crashes. The Workspace periodically validates active sessions; if the client does not respond, the seat may eventually be released after prolonged inactivity (commonly several hours). Additionally, multiple concurrent sessions or stale authentication tokens may lead to inconsistent license state reporting.

Recovery paths and preventive options

  • Disconnect and reconnect to the Develop Workspace within the client.
  • Sign out and back into Altium using the user avatar.
  • Request that a Workspace administrator release or revoke the seat from the web portal.
  • Clear browser cache and cookies or try a different browser if Workspace data appears inconsistent.
  • Verify system time, date, and time zone, and ensure only one active session is in use.
  • Use autosave and local history features to protect work during interruptions.
  • Consider using the roaming (reserved) seat feature to ensure uninterrupted access when needed; reserved seats are intentionally locked to a user until manually released.

Step-by-step process to recover an author license

  1. If Altium Designer Develop appears to have lost its author seat, do not close the application if you have unsaved work.
  2. Click Active Server in the upper-right corner.
  3. Click Sign Out for the Workspace (arrow exiting a square bracket).

    Altium Designer workspace menu showing account flyout, with Sign Out option selected under shared workspaces.

  4. Click Active Server again; it should now indicate Not Connected.
  5. Select your Develop Workspace to reconnect.
  6. If the issue persists, click the user avatar in the upper-right corner and sign out of Altium, then sign back in.

    Altium Designer workspace account menu expanded with Profile and Extensions listed, showing the Sign Out action available for the current signed‑in workspace.

  7. If still unresolved, open the Workspace in a browser using Active Server » Open Workspace in Web Browser (globe icon).

    Altium Designer workspace menu with account flyout open, showing shared workspaces list and an “Open workspace in Web Browser” icon/action available for a selected workspace.

  8. Navigate to Admin » Usage and Billing.
  9. If the affected user is listed as Taken Online or Reserved Seat, click the Release button to free the seat or revoke the reservation.

    Altium 365 Design Portal Usage and Billing page showing Altium Develop subscription, 5 author seats with 1 in use, and a user listed with status Taken Online and option to release the seat.

  10. Return to the client, sign out of the Workspace if needed, and sign back in.
  11. If seat availability still appears incorrect, clear browser cache and cookies (use Ctrl+Shift+Del) or try a different browser.
  12. Confirm Windows system date, time, and time zone are correct.

Additional Notes

  • An intermittent Error loading subscription info may appear in Admin » Usage and Billing. This can often be resolved by signing out and back in, clearing browser cache and cookies, or using a different browser.
  • Network issues may block required traffic between the client and Workspace. Routers, providers, or power-saving network adapters may interrupt connectivity. Engage your network support team if needed.
  • Packet capture tools such as Progress Telerik Fiddler Web Debugger or Wireshark can help diagnose blocked or failing connections.
  • Autosave creates periodic backup files, and Local History maintains version history, allowing recovery after crashes or interruptions.
  • The roaming (reserved) seat feature locks a license to a specific user for uninterrupted access and must be manually released when no longer required.
  • The Development team is aware of reliability improvements needed in interrupted seat-handling scenarios; no ETA is provided.

References

If you find an issue, select the text/image and pressCtrl + Enterto send us your feedback.