Symphony

Symphony is a team communication platform that provides messaging, voice calls, a contact directory, and conversation analytics for organizations.

  • Communication
  • Tools & Utilities
Symphony is a team communication platform that provides messaging, voice calls, a contact directory, and conversation analytics for organizations.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

14/100 Low

Maintained
0last commit 1154 days ago
Popular
61 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
502 GB minimum RAM
GitHub stars
1
Open issues
0
Last commit
2023-09-24
Activity
stale

Checked 3 days ago - source: GitHub (symphony-collaboration/symphony)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 2 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set the Agent's serverFqdn at startup Before starting Symphony Agent, set serverFqdn (the full domain name the Agent is reachable at, like agent.example.com). If it is missing, the Agent's info won't be correct and tools that use that name may not connect. source
  • Keep your Symphony API tokens safe If your setup calls the Symphony API, keep the sessionToken and keyManagerToken (authentication tokens that prove your app is allowed to make calls) available and protected. Without them, requests fail authentication and actions like sending messages won't work. source
  • Use the rules for app settings keys When saving an app configuration property through /configuration, use a unique non-empty key and a non-null value within the stated character limits. If the format is invalid, Symphony returns a 400 error and the setting is not saved. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can users log in faster if my organization supports SSO?

An IT resource can enable single sign-on for Symphony. You can send IT the link from the downloads page to have it enabled.

What must I configure before starting Symphony Agent?

Set the Agent's serverFqdn to the full domain name where the Agent is reachable before starting it. If it is missing, the Agent's info may be incorrect and tools that use that name may not connect.

Why do Symphony API calls fail authentication?

Make sure the sessionToken and keyManagerToken are available and protected for any setup that calls the Symphony API. Without them, requests fail authentication and actions such as sending messages won't work.

What rules apply when saving an app configuration property?

Use a unique non-empty key and a non-null value within the stated character limits. If the format is invalid, Symphony returns a 400 error and the setting is not saved.

Answers sourced from rest-api.symphony.com, rest-api.symphony.com, rest-api.symphony.com, symphony.com

Community

Collected 48 days ago - public community threads