Help
Find what you need
Every page on this site in one place. In a LOGOS program, Help opens the user guide; Help → Report a bug reaches us with the log attached.
The software
- The LOGOS suite — the four programs
- Pricing and licensing
- Questions
- Report a bug or request a feature
- How to: connect a project to Slack; recover a lost server administrator
Updates
- Release notes — what changed in each release and how soon to install it
- Updating LOGOS — for your IT — the LOGOS Server and the PCs, step by step, and going back
- My Account → LOGOS licences & download — keys, activation, and the installer
For IT and assessors
- Security — reporting a vulnerability, advisories, how releases are checked
- Security advisories, by email too
- The individual licence’s two accounts (CMMC Level 2)
- Security & deployment at a glance
- Lost your only server administrator? — the two-party recovery
Us
- Consulting — engineering as a service; contact us
- About LOGOS Modular Systems
- Join the team
- Privacy and Terms
How to
Connect a project to Slack (a LOGOS Server, for its administrator)
Each new comment on the project’s items, and each Hodos card added or moved, is posted to a Slack channel; a reply in its thread comes back into LOGOS. Only Open data is posted unless you raise the project’s level.
- Choose how replies come in. Socket Mode (recommended): the server connects out to Slack, and nothing is opened to the internet. Events API: Slack calls the server’s address, so that one path is opened at your reverse proxy.
- In the web console: Projects & pools > 4. Chat: Slack and Microsoft Teams. Pick the project, tick Post to Slack, choose the way replies come in, and open Setting up the Slack app, step by step: it shows the app manifest to copy.
- Make the Slack app: at api.slack.com/apps, Create New App > From a manifest, pick the workspace, choose the JSON tab, replace the sample with the manifest, then Next > Create.
- Its tokens: Install App to the workspace, then copy the Bot User OAuth Token (
xoxb-…, OAuth & Permissions). For Socket Mode, also Basic Information > App-Level Tokens: a token with the scopeconnections:write(xapp-…). For the Events API, the Signing Secret (Basic Information) instead. - The channel: type
/invite @LOGOSin it, and copy its channel ID (the channel’s name > View channel details, at the bottom). - Back in the console card: paste the channel ID and the tokens. For the Events API, paste the card’s Request URL into the Slack app’s Event Subscriptions (it is shown after the first save).
- Who may reply: under People, for replies, one line per person: their Slack member ID = their LOGOS username, e.g.
U07ABC123XY = jsmith. A member ID is in Slack under the person’s profile > ⋮ (More) > Copy member ID. Without a line, Slack answers “Your Slack account is not linked to a LOGOS account”. A reply also needs a right in the project (a Stakeholder may comment) and clearance for the pool’s level. - Save, and Send a test message. The card says what Slack answered, in words. Then write a comment in a LOGOS program and reply to it in Slack: the reply shows in LOGOS, marked as written from Slack.
Microsoft Teams is on the same card: tick Post to Teams and paste the channel’s incoming webhook address (one way: replies stay in Teams). IT can turn chat off for the whole server; an air-gapped server has it off. The tokens are kept sealed on the server and never shown again.
Lost your only server administrator? (a LOGOS Server, for your IT)
If the only person who could sign in to your LOGOS Server’s web console as an administrator has left, can’t be reached, or has lost both the password and the phone, you can make an administrator again. There is no back door: no master password, no default account, and nothing we can do from outside. Getting back in always takes two parties:
- A Windows administrator on the server machine — the server’s data folder is open only to the machine’s administrators and the service itself; and
- A one-time recovery code from your organisation’s licence holder (the logosmodular.com account your seats are on), in My Account → LOGOS licences → LOGOS Server → Recover a server administrator. If the licence holder is the person who left, write to support@logosmodular.com from your organisation’s address: before we issue a code we check who is asking and their authority — we call back a telephone number we already have on record for your organisation (never one given in the request), or ask for the request on your organisation’s letterhead, signed by an officer — and we may ask for both.
- See what the code is checked against. On the server machine, in an administrator PowerShell:
& "C:\Program Files\LOGOS Server\logos_server.exe" --config "C:\ProgramData\LOGOS Server\server.json" --recover-admin NAME— NAME is the account to recover (the old administrator’s, or a new name, which is made). It changes nothing; it shows your organisation, whether the server is enrolled online or air-gapped, and its administrator accounts. - Get the code. The licence holder types NAME in My Account (ticking The server is air-gapped if step 1 said “licensed by file”) and gets the code — 23 groups of 6 letters and digits, shown once and downloadable as a file.
- Recover. On the server machine: the same command with
--codeand the code, or the file it is in. No internet is needed. It prints a one-time set-up link; if it refuses, it says what is wrong and changes nothing. - Set it up. Open the link: choose the new password and set up two-step sign-in with an authenticator app. Then sign in to the console, remove the old administrator if their person has left, and add a second administrator.
The code is signed by us and checked by the server offline, so it works on air-gapped servers too. It works once, for 24 hours, only on your organisation’s server and only for the account it names.
What is recorded, and who is told. The server’s audit and the Windows Event Log record the recovery (and every refused attempt) by the code’s id, never the code; every administrator sees a notice of it in the console for 30 days. We record each code issued — who asked, when, for which account — and email the licence holder each time.
Keep at least two administrators (web console: People & rights > Administrators). The console shows a notice while only one can sign in.
The honest limit. The code gives back control of the console; it never opens your data. Your data files are protected by who holds Windows administrator rights on the server machine, its disk encryption (BitLocker) and the data folder’s access list — a Windows administrator there can read them, code or no code. The full steps are in Updating LOGOS — for your IT, section 9.
Write to us
- support@logosmodular.com — using LOGOS, bugs, and questions
- licensing@logosmodular.com — keys, activation, moving a seat, air-gapped activation
- sales@logosmodular.com — quotes, purchase orders, evaluations
- security@logosmodular.com — a security problem in LOGOS or this site