Phonemos is a tool for content collaboration and documentation. It provides wiki-like features for collaboratively editing pages and publishing documents.
With fine-grained permissions, content can also be made available to partners or customers, which enables cross-organizational collaboration. Participants can be assigned tasks and deadlines set — without an additional tool.
All knowledge can be stored in a central location. This means that all participants always have the same level of knowledge and can access information without having to ask third parties.
Content can be edited by several users at the same time, and the changes are visible to all editors in real time.
Each page can be maintained in several language versions. Ideal for information that is accessible to customers.
Various adaptations to your CI/CD and specific use are possible
The user-friendly, fast and powerful editor makes it easy for Office users to create pages.
Reactive support from linkyard, via chat, telephone or service portal.
Our software is operated and developed in Switzerland. All data is stored in Switzerland in encrypted form and can only be accessed by Swiss companies.
You can easily edit the pages in your playground by clicking the edit icon (or using the keyboard shortcut “e”):
This will put you in edit mode
The changes you make are automatically saved continuously, so there is no “Save” button. The changes are immediately visible to all editors (in edit mode), but are only visible to everyone when “Publish” is selected.
In other wiki systems, files often only exist as attachments to pages. While this makes sense for many files such as embedded images, etc., we don't think it does justice to the importance of documentation that can be provided as PDFs or Office documents.
For this reason, you can interchangeably mix files and wiki pages in your workspace tree.
The files can simply be uploaded by dragging and dropping. They are automatically versioned and stored in encrypted form.
Other cloud software providers charge extra for SSO integrations. We have decided to make SSO the standard for a customer directory.
And why? It's easier to use, more convenient, and user lifecycle control 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 application-internal user directories.
It is also possible to combine several directories 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 other things, we support the integration of the following solutions:
For technicians: The integration of SAML 2.0 and OIDC is supported.
The user and permission management is not activated for you on the demo, but if you are interested, we will be happy to show it to you. You have full access to the live instance and can also configure it yourself.