Phonemos is a tool for collaboration and documentation of content. It offers wiki-like functions for collaborative page editing and document publishing.
Content can also be made accessible to partners or customers with fine-grained permissions, which enables cross-organisational collaboration. Tasks can be assigned to participants and deadlines set - without an additional tool.
All knowledge can be stored in one central location. This way, everyone involved always has the same level of knowledge and can access information without having to check with third parties.
Content can be edited simultaneously by several users, the changes are visible in real time for all editors.
Each page can be maintained in several language versions. Optimal for information accessible to customers.
Multiple adaptations to your CI/CD and to the specific application possible
The user-friendly, fast and powerful editor makes creating pages easy even for Office users.
Reactive support from linkyard, via chat, telephone or service portal.
Our software is operated and developed in Switzerland. All data is stored in encrypted form in Switzerland and can only be accessed by Swiss companies.
You can edit the pages in your Playground simply by clicking on the edit icon (or using the keyboard shortcut "e"):
This will take you into edit mode
The changes you make are automatically saved continuously, so you will not find a "Save" button. The changes are immediately visible to all editors (in edit mode), but only become visible to everyone when "Publish" is selected.
In other wiki systems, files often exist only as attachments to pages. While this makes sense for many files such as embedded images etc., in our opinion it does not do justice to the importance of documentation that can be provided as PDFs or Office documents.
For this reason, you can mix files and wiki pages interchangeably in your workspace tree.
The files can be uploaded simply by drag-and-drop. They are automatically versioned and stored in encrypted form.
Other cloud software providers charge extra for SSO integrations. We have decided to make SSO against a customer directory standard.
And why? It's more user-friendly, more convenient and controlling the user lifecycle in a well-managed central directory also adds an extra layer of security. And it actually costs us more to provide the functionality to build in-application user directories.
Multiple directories can also be combined for different user groups. For example, an Azure AD for employees and accounts managed in Phonemos for customers. Or Google social login for customers.
Among others, we support the integration of the following solutions:
For technicians: The integration of SAML 2.0 and OIDC is supported.
The user and authorisation management is not activated for you in the demo, but if you are interested we will be happy to show you. On the live instance you have full access and can also configure it yourself.