How Organizations Get More from hubley Web Parts
An intranet stays usable only if the people who run it can configure a feature without leaving it to hunt for a manual, and if product gaps reach the team that builds the software. hubley places both inside the web part. Knowledge and Feedback, opened from the How To button, gives editors and administrators documentation and training for the feature they are working in, and a direct path to send product feedback to the hubley Product Team. Help and product comments stay in the same place as the configuration work.
What is Knowledge and Feedback in hubley?
Knowledge and Feedback is built into hubley web parts. It connects intranet managers and content owners with two resources.
| Path | What it opens | When to use it |
|---|---|---|
| Knowledge | Documentation and training resources for that hubley feature | You need to learn, configure, or maintain the web part you already have open |
| Feedback | A text box that sends ideas, suggestions, and product comments to the hubley Product Team | You have a product idea, a change to an existing feature, or a gap in the documentation |
The feature is opened from the How To button in web part settings. On select features, the button is also available directly on the web part. Most intranet visitors never see it. It is there for people who add content, edit pages, or handle other administrative work.
Why does in-context help matter as an intranet grows?
A small intranet can run on memory. A larger one cannot. Content owners move between news layouts, directories, policy pages, and personal dashboards, and each web part has its own settings. Searching a separate documentation site means leaving the page, guessing which article matches the feature, and coming back to apply the steps.
Knowledge and Feedback shortens that path. The manager starts from the web part already on the page, opens How To, and chooses Web Part How To for the documentation tied to that feature. The same area accepts product feedback, so an idea does not wait for a later email or a meeting note that never gets sent.
That matters for the employee experience even though employees do not see the button. Pages stay accurate when the people who maintain them can find the right steps in context. Features improve when the people who use them every week can tell the Product Team what is missing.
How do hubley web parts support the digital workplace?
SharePoint is the tenant. The intranet is the experience employees open. hubley adds more than 90 configurable, SPFx-based web parts on top of SharePoint so organizations stay inside Microsoft 365 instead of moving communications and collaboration to a separate system. Those web parts are grouped around four pillars. A public overview is on Unlocking the Power of SharePoint Intranets with hubley Web Parts, and the catalog is on the features page.
| Pillar | What employees get | Examples |
|---|---|---|
| Intelligence | Search, writing help, analytics, and agents inside the intranet | AI Writing Assistant, SearchHub, AnalyticsHub, hubley Agent and Bot Manager |
| Communication | News, alerts, and policy acknowledgment that can reach people beyond the homepage | NewsHub, NotificationsHub, banners, PolicyHub |
| Collaboration | Spaces, personal dashboards, documents, and Teams in the same workplace | hubley Spaces, MyHub, DocHub, Teams integration |
| Engagement | People, events, and mobile access so the intranet is not only a news site | StaffHub, EventHub and calendar, celebrations and photo feed, hubley Employee App, OnboardingHub |
A web part only pays off if someone in the organization can set it up and keep it current. Knowledge and Feedback is the in-product path for that work. It does not replace implementation or the hubley team. It gives the people who own pages a way to learn the feature in front of them and to send product comments back without opening a separate tool.
How does the How To button work?
Open the hubley web part you are configuring. In web part settings, select How To. On select features, How To is also on the web part itself.
If you need to learn the feature, choose Web Part How To. That opens documentation and training for that web part, so configuration starts from the feature rather than from a general search of the help library.
If you have a product comment, use the feedback text box in the same area and select Submit Feedback. The note can be an idea for new functionality, a change to the web part you are using, or a recommendation to update the documentation.
What feedback should intranet managers submit?
The feedback box is for the hubley product and for your experience using it.
Ideas for new features
If a task on the intranet still needs a workaround, send the idea. The Product Team uses submitted ideas to spot work worth considering in later releases. A submission is not a commitment to build the feature.
Changes to an existing feature
If a web part already does the job but a setting, label, or step gets in the way, describe the change against the feature you have open. Context from the web part you are in is more useful than a general note sent later.
Documentation gaps
If a How To article skips a setting, uses unclear steps, or does not match the screen, say so in Feedback. That comment is about the product documentation, not a request for someone to configure your page.
What should not go through Knowledge and Feedback?
Knowledge and Feedback does not replace support. Product comments improve hubley. Support handles your intranet. Use the Support Portal or your hubley team for anything that needs a person, a callback, or troubleshooting on your tenant.
| Request | Knowledge and Feedback | Support Portal or your hubley team |
|---|---|---|
| Documentation or training for the web part you have open | Yes. Choose Web Part How To. | Not required for self-serve steps. |
| Idea for a new hubley feature | Yes. Submit Feedback. | No. |
| Suggestion to change an existing hubley feature | Yes. Submit Feedback. | No. |
| Documentation that is missing, unclear, or out of date | Yes. Submit Feedback. | No, unless you also need someone to apply the steps on your intranet. |
| A question that needs a live person | No. | Yes. |
| Troubleshooting on your intranet | No. | Yes. |
| Feedback on your organization’s design or content | No. | Yes, or your internal intranet owners. |
| Demo request or callback request | No. | Yes. |
Sending a support issue through Feedback delays the response. The Product Team reviews product comments. It does not run the support queue.
Who can see the How To button?
The button is not part of the employee view. People who can add information, edit pages, or complete other administrative tasks can see it. Standard visitors do not. That split keeps help and product feedback with the owners of the intranet, and it keeps the page employees open free of management controls.
| Role | Sees How To? | What they should do |
|---|---|---|
| Intranet manager or content owner with edit rights | Yes | Open How To for documentation, or submit product feedback from the web part |
| Administrator who can change pages or features | Yes | Same path. Route tenant issues to support, not to Feedback |
| Standard employee | No | Use the intranet. Report page issues to the internal owner |
How does feedback stay inside hubley and reach the Product Team?
Submitted feedback goes to the hubley Product Team. The team reviews it on a regular cycle and uses it to find product and process changes. If a comment needs clarification, the team may contact the person who sent it. A reply is not sent for every note.
The information stays inside hubley. It is not shared outside the organization. The exception is kudos or praise, which may be used on the hubley website. Names are not used on the website without authorization. Follow-up happens only when the team needs more detail.
How can a company get more from the web parts it already has?
The web parts are already in the tenant. The unused value is usually configuration knowledge and a closed loop back to the product. Intranet owners can treat How To as part of the publishing routine.
| Step | What to do | What it changes |
|---|---|---|
| 1 | Before changing a web part, open How To and read Web Part How To for that feature. | Settings match the current documentation instead of an old screenshot or a remembered step. |
| 2 | If the article does not cover the setting, submit that gap as documentation feedback. | The next owner is less likely to hit the same missing step. |
| 3 | When a feature almost fits the communications, directory, or policy workflow, submit the product change from that web part. | The Product Team sees the request in the context of a real feature, not a detached inbox note. |
| 4 | Send tenant issues, design reviews, demos, and callbacks to the Support Portal or your hubley team. | Those requests reach the people who can act on your intranet. |
Organizations that already run NewsHub, PolicyHub, SearchHub, StaffHub, or MyHub do not need a new platform to get more from those features. They need the owners of those pages to use the documentation attached to the web part, and to send product comments to the team that ships the software.
Frequently asked questions
What is Knowledge and Feedback in hubley?
It is a feature in hubley web parts. Knowledge opens documentation and training for the feature you are using. Feedback sends product comments to the hubley Product Team. Both open from the How To button.
Where can I find the How To button?
It is in web part settings. On select features, it is also on the web part itself.
Who can see the How To button?
Users who can add information, edit pages, or perform other administrative actions. Most standard intranet users do not see it.
Can I use Knowledge and Feedback to ask for help?
No. Questions that need a person belong in the Support Portal or with your hubley team.
Can I submit feedback about my organization’s intranet?
No. Feedback is for the hubley product and your experience using it. Comments on your organization’s design or content go to your internal owners or your hubley team.
Will someone respond to my feedback?
The Product Team reviews submissions regularly and follows up when it needs more information. Not every submission gets a reply.
Is feedback shared outside hubley?
No. Submissions stay inside hubley. Kudos or praise may appear on the hubley website. Names are not used there without authorization.
How do hubley web parts support a digital workplace?
They extend SharePoint with more than 90 SPFx web parts for intelligence, communication, collaboration, and engagement, so employees stay in Microsoft 365. Knowledge and Feedback is how managers learn those features and send product comments without leaving the web part.
The next time you configure a hubley web part, open How To. Use Web Part How To for the documentation on that feature, or submit product feedback from the same panel.
To review the web parts with your team, start at hubley.com or the features catalog.
