--- service: "Publicasta" schema_version: "1.0" article_id: 517 title: "Panel settings and access" language: "en" default_language: "en" canonical_url: "https://hosting-help.livegpstracks.com/settings?lang=en" json_url: "https://hosting-help.livegpstracks.com/settings.json?lang=en" api_url: "https://hosting-help.livegpstracks.com/api/public/v1/channels/hosting_livegpstracks/articles/settings?lang=en" channel_url: "https://hosting-help.livegpstracks.com/api/public/v1/channels/hosting_livegpstracks" channel_articles: "https://hosting-help.livegpstracks.com/api/public/v1/channels/hosting_livegpstracks/articles" search_url: "https://hosting-help.livegpstracks.com/api/public/v1/search" documentation_url: "https://publicasta.com/api-docs#reading-publicasta" openapi_url: "https://publicasta.com/api-docs/openapi.json" published_at: "2026-09-06T09:16:06+00:00" updated_at: "2026-09-06T09:16:06+00:00" translations: - language: "en" html_url: "https://hosting-help.livegpstracks.com/settings?lang=en" markdown_url: "https://hosting-help.livegpstracks.com/settings.md?lang=en" json_url: "https://hosting-help.livegpstracks.com/settings.json?lang=en" - language: "ru" html_url: "https://hosting-help.livegpstracks.com/settings?lang=ru" markdown_url: "https://hosting-help.livegpstracks.com/settings.md?lang=ru" json_url: "https://hosting-help.livegpstracks.com/settings.json?lang=ru" --- # Panel settings and access > Session lifetime, simultaneous logins, panel password and API key. Separate owner access from customer and website settings, and check the result after changing credentials. [Guide contents](./contents) **Settings** controls access to the hosting panel: session lifetime, simultaneous logins, password and API key. It does not configure trackers or the appearance of your customer website. ## Three separate areas - **Hosting panel:** your administrative access and the language used to manage companies, tariffs, customers and finances. - **Customer website:** its domain, name, language and registration availability, managed under [Websites and domains](./sites). - **Customer account:** its password, balance, tariff and assigned website, managed under [Customers and balances](./users). Changing the panel language does not translate your website's custom text or change tariff currencies. Use **Language** near the top of the page to change the panel language. ## Session lifetime The value is in **seconds**. For example, 1800 means 30 minutes. It limits inactivity; working in the panel refreshes activity time. It does not force a logout exactly 30 minutes after signing in. The supported range is 60 to 2,592,000 seconds. Avoid a long session on a shared or borrowed computer. Click **Logout** when finished rather than relying on closing the tab. ## Simultaneous logins The multi-login setting controls whether the same login can be used in several sessions. When multi-login is disabled, a new login replaces the access token, preventing the earlier session from continuing to use it. If you keep being signed out, check this setting and whether a colleague or your second browser is using the same login. This setting is not two-factor authentication or a system of separate staff roles. Click **Change** in this block after changing session settings. Password and API-key changes have their own separate buttons. ![Security settings with a 1800-second session lifetime and multi-login enabled](https://hosting-help.livegpstracks.com/storage/projects/45/pages/517/2026/09/cb42dbbe-8e85-41de-b1a4-ccce65bfe18c.webp) *The demonstration panel. Session settings have their own Change button.* ## Changing your password Enter a new password in the right-hand block and click **Change**. The current form accepts Latin letters and digits. Choose a long, unique password; a short example in a legacy hint is not a security recommendation. The field displays what you type. Do not change the password while sharing your screen or send a screenshot of the completed form to support. This changes the **hosting-panel password**. It does not change customer passwords or automatically synchronize the owner's main LiveGPSTracks account password. The two passwords can therefore differ after a separate change. ## API key The API key is for integrations. Our screenshot shows `DEMO-KEY-NOT-VALID`, not a working key. Never publish your real key, embed it in public browser JavaScript or include it in screenshots sent to others. **Change** in the API-key block generates a replacement after confirmation. The old key will no longer work, so prepare to update every integration that uses it. Replacing the key does not change your panel password. If no key appears on your first visit, refresh the page. Do not generate another key just to test the display. The “Hosting API” chapter explains authorization and a first request. One important legacy detail: API password verification uses the owner's main account, not a separately changed hosting-panel password. ![Separate password and API-key forms with a non-working demonstration key](https://hosting-help.livegpstracks.com/storage/projects/45/pages/517/2026/09/6078f108-3e24-47c7-be31-d79fdf49b2af.webp) *No password is entered and the API key is fictional. Keep real credentials out of screenshots.* ## Check after making changes 1. Make sure you saved the intended settings block. 2. After changing a password, store it in your password manager and check a new login. 3. After replacing an API key, update integrations and test a read-only request first. 4. Never send support a password, password MD5, session token or API key. A login, timestamp and sanitized error are usually enough to start investigating. [Back to contents](./contents)