Currently, Linchpn Events cannot be found in the Confluence Search. Launchpad Apps can be found, but have no content type associated which could be used to filter the search results. It also seams that Launchpad Apps are treated differently in the ranking of search results. They always appear at the top of the result list. Our desired behavoir would be that Linchpin Events and Launchpad Apps are treated as additional content types and ranked according the the same rules as all the other content types.

In Cloud (Mantra) you have built in gadgets for social media feeds like X, Facebook etc. Could you build same for DC and Linchpin suite?

Many of our users don't enter the complete surname when searching vor user profiles. As a result they ofen get an error message, that the user was not found (see picture). It make sense and we are really thankful that this message already includes information about the fields, which are searched. Very nice feature :) Would be even nicer, if there would be an additional tipp or hint to end the search input with '*', when the name is NOT entered completely (which in effect will cause a contained-in-search). Friendly regards Michael Kniel (Uniklinikum Erlangen)

Not every Linchpin will be able to handle Emojis at all - the database it's running on has to meet certain criteria. But if it does - why not embellish your Content with Emojis? React with Emojis in your comments on news, use them in the microblog, basically wherever you want people to interact with each other. Emojis are common in so many apps, people are used to using them. Would you activate that feature in your Linchpin?

If I delete attachments on pages/blogs, everyone who is watching them will always be informed. Sometimes you just want to remove "old" attachments without notifying everyone. It would be better if you can choose here whether you want to send a notification. Also, it would be handy to mark and delete multiple attachments, which would be great for page history too.

A question & answer content type would be really useful for asynchronous and persistent knowledge sharing. Many intranet and community platforms have this feature, so it makes sense for Linchpin to include something similar in order to compete and provide a comprehensive communications product. The format could be built off of Microblogs; we essentially just need threaded conversations which can have a reply selected as the accepted answer. Similar to what Jive did, the answer could be featured at the top of the post, preventing visitors from having to scroll the entire thread to discover the answer to a question that was posted. Ideally this would also have a Q&A 'Hub' similar to the other hubs in Linchpin, which would contain filters for things like status (Answered and Unanswered ), categories, labels, or "topics" (to follow suit with the Microblogs template), and a data range, for starters. Macros for this could include a Timeline macro just like the one for Microblogs, which could have settings for Space, Topics, etc.

Today the Additional Filters are hidden and the user need to click on the button in order to display the filters. We would like to have the option to configure the Additional Filters button and display the filters per admin's choice to be displayed on People page.

The administration of authorized persons would be easier if they could be displayed in alphabetical order of the Rhine.

We would love to be able to give credits and rewards and badges to our users. Similar to the outdated Awards (Karma) app, where you get points based on activity and user events in Confluence (early/late login, creating, liking, commenting, receiving likes etc). Additionally users can credit other users with badges. There are scorecards and user profile related overviews of earned points and badges. The basic idea of this addon is great, but it is not updated for a while and it has to include Linchpin content obviously :)

As the creator of an event, I would like to issue a certificate to all registered participants after the event. The name of the participant, the title of the event and the date and creator of the event should be filled in automatically. Suggested text: [Event creator] [Participant] hereby confirms participation in [Event name] on [Event date].