Announcements
- Khoros is now part of the IgniteTech family. Learn More.
Featured Content
Four weeks ago, we acquired Khoros.
Since then, there’s been speculation—about what changed, what we’re doing and where this platform is headed. Some focused on staffing. Others asked about continu...
Monthly digest to provide all users a reliable snapshot of product updates, as well as any other resources that can provide inspiration or guidance.
The mission of this online community is to provide a peer-to-peer and direct support channel for people cultivating enterprise communities on the Khoros platform. It is a central for educati...
Recent Content
Handlebars custom component not executing GraphQL query
I have been following along with the directions on this page to try to create a custom Handlebars component that executes a graphQL query and displays the results in simple HTML. My .hbs file references the query like this: {{#gql "privateUserStats" variables=(hash id=user.id)}} ... {{/gql}} I also have a .graphql query defined in queries/privateUserStats.query.graphql: query privateUserStats($id: ID!) { user(id: $id) { id login email firstName lastName email ... } topicsStarted: messages(constraints: {authorId: {eq: $id}, depth: {eq: 0}}) { totalCount }... } and I reference it in my component.json under the "graphql" block: "graphql": { "privateUserStats": "./queries/privateUserStats.query.graphql" } Despite this setup: The Handlebars rendered correctly user.id was available But the GraphQL query never fired — no network activity, no data returned, and no console errors Can someone help? I'm all out of ideas.
Custom component for group hubs
Hello, I built couple of custom components for connect.hyland.com, but until now I didn't need to know the current category id. I need to build a new component to improve the layout of our Group Hubs (default components are either "too much" or "not enough" or don't exist). I would need to get only the Group Hub description (not the one in admin, but the one that owners can edit) and the list of Group Hub owners. I searched the API documentation but I struggle with the start: in my component, how I can get the node id, or the group hub id in which this component will work?Aurora: Create community experience surveys
Admins can enable community experience surveys surveys, which prompt members to provide feedback about their experience in the community. Survey responses and scores can be collected via an export (see View community experience survey results). Create a survey Creating a survey requires several configuration steps, including designing the branding, designing its behavior, selecting its questions, and finally, turning it on for visitors. To access survey configuration options: Open the Account menu. Select Settings. Select Content Features. In the left column, select Community Experience Survey. Set up your survey: Design survey branding Design survey behaviors Select your questions Turn on the survey for visitors Design survey branding In the Branding area, select Edit. In the window, update the following as needed: Community name: The community name used in survey questions Brand name: The brand name used in survey questions Survey logo: Use a PNG or SVG logo; horizontal preferred. Text color Header background color: Used in the background of the survey header Select Submit. Design survey behaviors In the Survey Behaviors section, select Edit. Select whether you want to Present To: Signed-in members Anonymous users Both members and anonymous users (Optional) Select the role(s) you want to survey. (Optional) Select the role(s) you don’t want to survey. (Optional) Select the place(s) where you want the survey to be triggered. In the Frequency area, enter the number of Maximum responses to collect per month. This field sets the maximum number of surveys to collect for a given calendar month. After collecting this number of responses, no users will be prompted to take the survey until the first day of the following month. Enter a number of visits in the Present survey after this many visits field. This field sets the number of visits (0-500) to wait before prompting a viewer to take the survey. For example, if set to 3, the viewer isn’t prompted to take the survey until their fourth visit. Default = 0, which is the first visit. Enter a number of minutes in the Present the survey after this many minutes field. This field sets the number of minutes (1-60) to wait before prompting a viewer to take the survey after the defined number of visits have occurred. Default = 2. In the Conditions area, enter a number of days in the If declined/abandoned, repeat after this many days field. This field sets the number of days (1-365) to wait before prompting a viewer to take the survey after they’ve declined to take the survey. Default = 30. Enter a number of days in the If completed, repeat after this many days field. This field sets the number of days (1-365) to wait before prompting a viewer to take the survey again after they have already completed it. Default = 90. Select Save. Select your questions In the Questions and Answers section, select Edit. Use the toggles to turn on or off the questions you want to include or exclude on your survey, respectively. Some questions have follow-up questions based on the selected responses. Note: Because this survey is intended to gather important metrics and feedback, including CSAT (Customer Satisfaction Score), updating question titles and the order of questions is not permitted. Use the checkboxes by responses under your selected questions to designate which responses will be available for those taking the survey. Select Save. Turn on the survey for visitors After you have designed your survey the way you want it, you can enable it for your visitors by turning on the Community Experience Survey toggle at the top of the Community Experience Survey section.IgniteTech acquired Khoros to rebuild it. Here’s what that looks like.
4 MIN READ Four weeks ago, we acquired Khoros. Since then, there’s been speculation—about what changed, what we’re doing and where this platform is headed. Some focused on staffing. Others asked about continuity and direction. We’ve seen all of it. This post is here to clarify the facts—and, more importantly, to show where we’re headed next.
Using css in widget or styling out of the box components
I was wondering if it is possible to add a css file to a widget created in the designer. I know that this is possible when creating a handlebars component but when changing a widget in the code you can't add the css file as far as I can tell. I'm trying to create a component that is easily editable by our administrator, that's why I was thinking of using a widget created in designer. I don't know how easy or possible it is to add editable content in a handlebars or react component. If this is possible than that would also be an option. Anybody knows how to tackle this or where to find the correct information?Khoros Customer Data Retention and Destruction Policy
Data Retention Customer data is generally retained for the duration of the customer’s contract with Khoros. Exceptions to this include: Khoros Marketing: Data imported from various social media platforms is retained for a rolling twenty four (24) months before it is automatically purged. Khoros Care: Data imported from various social media platforms is stored for the life of the agreement but can be viewed directly in the platform only for 24 months. Data can be exported from the Service via API for a period of 18 months. Khoros Community: Data processed within Khoros Community will be retained for the life of the agreement. While being retained, all customer data must be retrievable and maintained per applicable legal, contractual and regulatory requirements. Customer's data will be available for 30 days from the date of termination or expiration of the agreement. Once the agreement ends, the data will be returned to the customer, provided however Customer provides timely written request. If Data is declined by Customer, Customer agrees Khoros has no further obligation to retain Customer’s data. Deletion of the data occurs thirty (30) days after the expiration or termination of the agreement with the following exceptions: (a) as otherwise required by applicable law; (b) data on backup systems or media is maintained for 90 days in order to maintain sound business continuity practices and then deleted; and (c) log files are maintained for up to twelve months for security reasons and then automatically deleted. During and after the life of the agreement, Khoros can use aggregated and anonymized data for metrics and reporting purpose. This data does not include any personal information and does not include any information about the customer or the end user. Data Backup and Restoration Backups are taken at least every day and every week and are encrypted using AES 256-bit information and are over written every ninety (90) days. Access to the backups is restricted to authorized individuals. Offsite backups are kept in a secure facility. Backups are made daily and weekly. We conduct backup restoration testing every twelve (12) months. Data Destruction At the expiration or termination of the agreement, if the customer wishes to have a copy of its data, we securely provide the information to the customer for: (i) Khoros Community content, at one time and at no charge, in a machine-readable format, and at Khoros' option, either in a single data extraction or multiple data extractions; and (ii) all other Khoros Services, customer may download the content itself in a comma separated value (.csv) format. Khoros may provide additional reasonable assistance for data extractions at Khoros’s standard Professional Services rates. The availability of Content for extraction or downloading from certain Services will be limited as described above within the Data Retention section. The data is made available for 30 days from the agreement expiration or termination, after which time it is deleted in accordance with the above 'Data Retention' Section. The active data bases are also dropped from the production servers as well after the data extraction is transferred to the customer. Once the media used for storage is retired it is scrubbed or destroyed using NIST SP 800-88 guidelines.Khoros Care: Direct Data Access Update
1 MIN READ Following our recent efforts to better protect the Khoros Care platform from abnormally high loads and to provide consistency across Care for historical data access directly available, data in Agent View and Manage View will be limited to 2 years. As always, for customers requiring routine access to data beyond that range, we encourage the implementation of local data store using our available export APIs. You may notice this change in effect already. Otherwise, the change will be pushed to your system within the next 10 days.
Featured Places
Education & Training
Self-service first product education experiences to maximize Khoros product adoptionHelp & Support
Find solutions and support for Khoros products
