JohnD
Khoros Alumni (Retired)
Joined 13 years ago
User Profile
User Widgets
Contributions
Personal Data Inventory for Khoros Subscription Services
This document captures a complete inventory of personal data points used throughout Khoros products. Khoros relies on performance of a contract and/or legitimate interests in order to process the personal data contained in this document. Please scroll down to the charts below or simply click on one of the following product links to be redirected to the corresponding chart: MARKETING Data Element Source Subprocessor Recipients (If blank, none) Country Locations of subprocessors can be found here Retention/Deletion Campaigns/Initiatives User ID User-created Aurora - indefinitely until 30 days post-contract Roles User ID User-created Aurora - indefinitely until 30 days post-contract Approvals User ID User-created Aurora - indefinitely until 30 days post-contract Labels User ID User-created Aurora - indefinitely until 30 days post-contract Credentials User ID User-created Aurora - indefinitely until 30 days post-contract Notifier Recipient Email User-created Aurora - indefinitely until 30 days post-contract User Profile ID first name last name email avatar image mobile phone User-created Aurora - indefinitely until 30 days post-contract Directory Service Customer/Company User ID Company Administrator-created Aurora - indefinitely until 30 days post-contract FINEX (Financial Industry Export) outgoing content (publishing posts and care replies) snapshots of company user profile details in the system user approvals Generated nightly by the marketing system. AWS filesystem - 1 day (deleted and regenerated nightly) Suite navigation data User ID Captured by Pendo as users navigate the product suite. Indefinitely at Pendo until 30 days post-contract) Promotion Accounts User ID User-created Aurora - indefinitely until 30 days post-contract Promotions User ID User-created Aurora - indefinitely until 30 days post-contract Care analytics data User ID Generated by the Marketing system as user actions occur. Aurora - indefinitely until 30 days post-contract Redshift - 30 days Care Rules User ID User-created Aurora - indefinitely until 30 days post-contract whodex profiles Social Handles Name Profile Image Location Coordinates Country Code Follower Count Following Count Sourced from supported social networks via API Aurora - indefinitely until 30 days post-contract whodex profile author notes user id author notes User-created Aurora - indefinitely until 30 days post-contract export logs User ID Generated by the Marketing system as user actions occur. Kibana - 30 days analytics dashboards User ID User-created Aurora - indefinitely until 30 days post-contract plans User ID User-created Aurora - indefinitely until 30 days post-contract messages User ID User-created Aurora - indefinitely until 30 days post-contract Content Center assets User ID User-created Aurora - indefinitely until 30 days post-contract auto-labeling rules User ID User-created Aurora - indefinitely until 30 days post-contract comments User ID User-created Aurora - indefinitely until 30 days post-contract replies User ID User-created Aurora - indefinitely until 30 days post-contract retweets User ID User-created Aurora - indefinitely until 30 days post-contract streams User ID User-created Aurora - indefinitely until 30 days post-contract Stream Entities Author Bio Full Name profile Picture: username social network user id Post Contents Sourced from supported social networks via API. Aurora - indefinitely until 30 days post-contract Cassandra - 7 days Memcached - 1 day User user id full name Company Administrator-created Aurora - indefinitely until 30 days post-contract visualizations User ID User-created Aurora - indefinitely until 30 days post-contract spaces User ID User-created Aurora - indefinitely until 30 days post-contract spotlight reports User ID User-created Aurora - indefinitely until 30 days post-contract post search results Author Bio Full Name profile Picture: username social network user id Post Contents Sourced from supported social networks via API Cassandra - indefinitely until 30 days post-contract Stream Items Author Bio Full Name profilePicture: username social network user id Post Contents Sourced from supported social networks via API Cassandra - indefinitely until 30days post-contract Influencers whodex profile id User-created Aurora - indefinitely until 30 days post-contract TeamQueue data Generated by the Marketing system as user actions occur. Cassandra- 30 days post contract CARE Data Element Source Third-Party Recipients Country Locations can be found here Retention/Deletion Id Name Picture First name Last name FACEBOOK: Consumer data is retrieved through Facebook APIs after the company authenticates their Facebook Page(s) with Response. All consumer data is subject to Facebook's Terms of Service. Yes Deleted within 30 days of end of customer contract. User comments deleted in Facebook will also be deleted in Care based on Facebook notification. Id Username INSTAGRAM: Consumer data is retrieved through Instagram APIs after the company authenticates their Instagram Handle(s) with Response. All consumer data is subject to Instagram's Terms of Use. Yes Deleted within 30 days of end of customer of contract. Id GOOGLE BUSINESS MANAGER: Consumer data is received through streaming updates after company authenticates Business messages with Care. All consumer data is subject to Google's Business Messages Terms of Service. Yes Deleted within 30 days of end of customer contract. Name Username GOOGLE MY BUSINESS: Consumer data is received through Google MyBusiness APIs after company authenticates with Care. All consumer data is subject to Google's Terms of Service. Yes Deleted within 30 days of end of customer contract. Name RSS: Consumer data is received through RSS APIs after company authenticates with Care. Yes Deleted within 30 days of end of customer contract. Id Display name Profile image url YOUTUBE: Consumer data is retrieved through YouTube APIs after the company authenticates their YouTube Channel(s) with Response. All consumer data is subject to YouTube's Terms of Service. Yes Deleted within 30 days of end of customer contract. Id APPLE BUSINESS CHAT:Consumer data is received through streaming updates after company authenticates Apple Business Chat with Care. All consumer data is subject to Apple's Terms of Service. Yes Deleted within 30 days of end of customer contract. Id First name Last name WEB MESSANGER (SMOOCH): Within a secure chat, provided by Sunshine Conversations, consumers will share unstructured PII (i.e. the information will be shared within a chat conversation). This data will be ingested into Care. Yes Deleted within 30 days of end of customer contract. Id Name WECHAT: Consumer data is retrieved through WeChat's APIs after the company authenticates their WeChat Account(s) with Response. All consumer data is subject to WeChat's Terms of Service. Yes Deleted within 30 days of end of customer contract. Phone number SMS: Consumer data is retrieved through Twilio APIs after the company authenticates their SMS numbers with Care. All consumer data is subject to Twilio's Terms of Service. Yes Deleted within 30 days of end of customer contract. Phone number First name Last name WHATSAPP: Consumer data is retrieved through Smooch APIs after the company authenticates their WhatsApp numbers with Care. All consumer data is subject to WhatsApp's Terms of Service. Yes Deleted within 30 days of end of customer contract. Name Device information GOOGLE PLAY STORE REVIEWS Yes Deleted within 30 days of end of customer contract. Id Name Profile image url NETBASE Yes Deleted within 30 days of end of customer contract. Name IOS APP STORE REVIEWS Yes Deleted within 30 days of end of customer contract. Id First name Last name Bio Profile image LINKEDIN: Consumer data is retrieved through LinkedIn APIs after the company authenticates their LinkedIn Page(s) with Response. All consumer data is subject to LinkedIn's Terms of Service. Yes Deleted within 30 days of end of customer contract. RADIAN 6: This is a general listening integration that can bring in content from all of the other networks listed. We should no longer be using this provider. Yes Deleted within 30 days of end of customer contract. Id Name Profile image url YELP: Consumer data is retrieved through LinkedIn APIs after the company authenticates their Yelp Location(s) with Response. All consumer data is subject to Yelps Terms of Service. Yes Deleted within 30 days of end of customer contract. Id Display name Email Profile image url KHOROS COMMUNITY Yes Deleted within 30 days of end of customer contract. KHOROS BOT Data Element Source Third-Party Recipients Country Locations can be found here Retention/Deletion Name Timezone Language Profile picture Chat related data that can include personal data (Specified by customer in custom DPA) Facebook messenger MongoDB Google cloud On project removal On applied data retention policy Phone number Name Chat related data that can include personal data (Specified by customer in custom DPA) WhatsApp MongoDB Google cloud On project removal On applied data retention policy IP address Browser version Browser language Chat related data that can include personal data (Specified by customer in custom DPA) Web Widget MongoDB Google cloud On project removal On applied data retention policy Any shared files are removed after 90 days Name Chat related data that can include personal data (Specified by customer in custom DPA) Khoros MongoDB Google cloud On project removal On applied data retention policy Phone number Chat related data that can include personal data (Specified by customer in custom DPA) Twilio MongoDB Google cloud On project removal On applied data retention policy Phone number in case of WhatsApp or SMS Analytics metadata Google cloud On project removal COMMUNITY Data Element Source Third-Party Recipients Country Locations can be found here Retention/Deletion Author login (username) email address (except privacy guide) salted password hash (except SSO) SSO - from SSO identity provider (usually customer's propitiatory identity system via SSO cookie). Local with migration - from PS team or Administrator importing the info Local without migration - from users through initial registration Yes Mysql, Elasticsearch, Cassendra - indefinitely. Redis - 24 hours Author userId Created during the first initial interaction to the system, may it be SSO or import or registration Yes Mysql, Elasticsearch, Cassendra - indefinitely. Redis - 24 hours Author ICQ (optional) AIM (optional) Skype (optional) MSN (optional) Yahoo (optional) Bio (optional) Custom personal data fields (customizable per community) Except required custom fields, all are optional not related to any feature supported Entered by user either through initial registration or sub-sequential interaction with the community. For custom personal data fields, it could also possible be from SSO cookie. Yes Mysql, Elasticsearch, Cassendra - indefinitely. Redis - 24 hours Author Facebook access token Supported Feature: Facebook connect and integration Entered by user either through initial registration or sub-sequential interaction with the community Yes Mysel - indefinitely. Supported Feature: Profile picture Author profilePicture Entered by user either through initial registration or sub-sequential interaction with the community Yes Mysql - indefinitely. Redis - 24 hours Author IP address browser cookie string user agent http referrer headers From the http requests to the community Yes Mysql - indefinitely. Redis - 24 hours Community User Metrics Total Messages Posted Total Page Views Total Messages Read Board Topics Started Board Replies Blog Articles Posted Blog Comments Posted Ideas Posted Idea Comments Posted Questions Posted Q&A Replies Posted Answers Posted Q&A Comments Posted Total Board Views Total Logins Total Minutes Online Created by the community Yes Mysql, Elasticsearch indefinitely. Redis - 24 hours CX INSIGHTS Data Element Source Third-Party Recipients Country Locations can be found here Retention/Deletion Audio Recordings: Name Phone number Email address Physical address Dates directly related to an individual (birth, death, admission, etc.) Gender Username Security code/PIN Security questions Account number IMEI number Audio files provided by Khoros clients Amazon Web Services Earlier of 24 months after the audio recording was created or Agreement termination date Audio Recordings: Name Phone number Email address Physical address Dates directly related to an individual (birth, death, admission, etc.) Gender Username Security code/PIN Security questions Account number IMEI number Audio files provided by Khoros clients Amazon Web Servies MongoDB Google Cloud Platform Earlier of 24 months after the audio recording was created or Agreement termination date Conversation transcripts: Name Phone number Email address Physical address Dates directly related to an individual (birth, death, admission, etc.) Gender Username Security code/PIN Security questions Account number IMEI number Text-based conversation transcripts provided by Khoros clients Google Cloud Platform Earlier of 24 months after the audio recording was created or Agreement termination date Product Reviews and Surveys: Name Phone number Email address Physical address Gender Age Username Account number IP address MAC address Text-based product/service review data provided by Khoros clients Amazon Web Services MongoDB Google Cloud Platform Earlier of 24 months after the audio recording was created or Agreement termination date Social Media Posts: Social network user ID Name Username Post contents From social networks via API, provided by Khoros clients, or third-party data aggregation sources Amazon Web Services MongoDB Google Cloud Platform Earlier of 24 months after the audio recording was created or Agreement termination date Web Session Data: Username IP address MAC address Email address Web session recording applications Amazon Web Services MongoDB Earlier of 24 months after the audio recording was created or Agreement termination date User Access Data: Email address IP address User created activity Okta Three (3) months from the date of the user session User Access Data: Name Email address User created activity Zendesk Indefinitely at Zendesk until 90 days post-contract termination User Access Data: Email address IP address User created activity Alienvault Sumo Logic Twelve (12) months from the date of the user session User Access Data: Name Email address User created activity Pendo.io Indefinitely at Pendo.io until 30 days post-contract termination25KViewsSign in to react to this post0CommentsAurora: Getting Started as a Community Administrator
Welcome to Aurora! Aurora is Khoros’ re-imagined Community experience that leverages more than 20 years of experience and learnings in the digital community space. This introduction guides you through the most commonly used community features and administration tasks and provides links to the best articles for these tasks. Tip: Take a tour of Aurora in this 1-hour video training course, which will help you familiarize yourself with key Aurora features and concepts. Tip: Complete self-paced training in the Khoros Academy Build Khoros Communities course. Note: Please check out the training video for new Admins, available within the Community Setting area below. Let's get started! As a Community Admin, your primary responsibilities include: Configuring and maintaining your community’s site structure Administering and managing feature areas of the community Maintaining member accounts and community content per your company's values and goals Upgrading the community to take advantage of new capabilities Before you begin, be sure to work with the Community Manager to have a thorough understanding of your community’s audience and goals. As a community admin, you’ll spend much of your time in the Community Settings area. Note: As Admin in the Khoros Community platform, you must have the Admin role. Learn more about Roles and Permissions. Community Settings The Community Settings area is where you’ll perform most of your administrative tasks. To open the settings area, go to Account Menu > Settings: Community Settings are grouped into themed areas: Structure Features Users The Settings Shortcuts page provides shortcuts to the most commonly used community settings pages. Click around and explore all the settings in these areas. Below, we’ve captured some of the most common tasks you’ll need to perform. (Depending on how roles on your team are distributed, you may not need to do all these tasks.) Build out the structure of your community Configure general and feature-specific settings Manage roles and permissions Set up, enable, and manage features that drive more community engagement Please watch the training video which guides new Admins through the most commonly used features within settings to help accomplish community administration tasks. Build out the structure of your community In the Community Structure area, you can build out and organize the topography of your site. You can decide the best way to group related content into categories and boards and which content types to provide in each area. Learn more about Community Site Structure and best practices when creating your site. Configure general and feature-specific settings From the Features area, you can configure general site settings as well as feature-specific settings that determine how things behave in your community. Manage user roles and permissions In the Users area, you can manage the roles and permissions for your community members and employees. To perform this task, you must: Define the set of default permissions for different community roles. Aurora includes some out-of-the-box roles. Tie together a permission sets to create the decided default community roles. Do this only if you want to provide a different level of access and experience for your members; for example, to access to a private area in the community. Other common member management tasks include: assign roles to members cloning roles Check out our best practices for implementing roles and permissions. Community Moderation As an Admin, you need to create a safe and vibrant place for your members to participate. Usually, you will have some moderators on your team to help you achieve these goals. In partnership with your moderators, you can: Maintain audit logs Set content filters Set abuse notifications Enable content archiving (coming soon)1.5KViewsSign in to react to this post0CommentsAurora: Manage image and video settings and permissions
Manage image settings Permissions Members must have the Add images to post permission to upload images. Members with this permission can add images to community content. To enable this permission for specific roles: Go to Settings > Users > Roles and permissions. Open the options menu (3 dots menu) for the role you want to grant this permission to. Select Media. Select the type of permission for the Add images to post permission as needed. To enable this permission for all members in the community: Go to Settings > Users > Roles and permissions. Scroll up the page and Edit for Community Permission Defaults. Select Media. Select the type of permission for the Add images to post permission as needed. Note: We recommend that you grant this permission only to trusted members to combat spam. Configure video settings To enable and configure image-related settings for your community: Go to Settings > Content Features. Select Media. Turn on Image uploads to enable members to add images to their content. In the Additional image settings section, select Edit to set the maximum file size (in MB) for uploaded images. Select Save. To override the setting to upload images lower-level categories or boards: Navigate to the desired place in the place picker. Scroll to the Media section under Content Features. Turn on or off Image uploads as needed. Supported file formats For Ranks, Aurora supports these image formats: .png and .svg For all other images, Aurora supports these image formats: .png, .jpg, .jpeg, .gif Manage video settings Note: Videos uploaded to a Khoros community are hosted by Brightcove. Learn more about the Brightcove video hosting service. Permissions Members must have the following permission to upload videos. Members with this permission can add videos to community content and messages. To enable this permission for specific roles: Go to Settings > Users > Roles and permissions. Open the options menu (3 dots menu) for the role you want to grant this permission to. Select Media. Select the type of permission for the Add videos permission as needed. To enable this permission for all members in the community: Go to Settings > Users > Roles and permissions. Scroll up the page and Edit for Community Permission Defaults. Select Media. Select the type of permission for the Add videos permission as needed. Note: We recommend that you grant this permission only to trusted members to combat spam. Configure video settings To enable and configure video-related settings for your community: Go to Settings > Content Features. Select Media. Turn on Video uploads to enable members to add images to their content. Select Edit to set the maximum file size (in MB) for uploaded videos. Turn on or off the ability to embed externally-hosted video content. Select Save. To override the setting to upload videos at lower-level categories or boards: Navigate to the desired place in the place picker. Scroll to the Media section under Content Features. Turn Video uploads and Embed external videos on or off as needed. Bypass media moderation You can grant trusted members or roles with trusted members the permission to bypass moderation for the media content they publish in the community. Learn more on how to grant this permission.696ViewsSign in to react to this post0CommentsHow to Use Atlas
Welcome to the Atlas Community. We've put together this guide to help you perform common tasks on the community, so you can get started participating sooner. Register with the community In order to get the most out of the Atlas community, you'll first need to register an account. Learn how to register and get started using Atlas here. Personalize your community experience Once you've created an account, you can personalize and customize your community experience in several ways. Most community members: Change their community avatar Set common viewing preferences Change your community avatar Changing your avatar is an easy way to personalize your community identity. You can change your avatar as often as you like. Your current avatar appears at the right side of the top navigation bar. To change your avatar: Go to your profile menu at the top right > My Settings. Click on the pencil icon next to your profile photo. Choose a new avatar in one of these ways: Choose a generic avatar from the Community collection on the right. Click the pencil icon on the new pop up to upload an image of yourself from your personal collection. Once you're done, click the Save button. Set your viewing preferences You can control display preferences, including your time zone, the date display format, and the date display style. To set your viewing preferences: Go to your profile menu at the top right > My Settings > Preferences. Click into each field and make the changes you want. Getting the most value out of Atlas Your role on the community A community is a place to search for information, read and post about topics of interest, and learn from each other. You are essential to keeping the community vibrant, even if all you ever do is read messages or articles that someone else has posted. We encourage you to visit often and participate. Ask your toughest questions. Chances are someone has a solution or can point you in the right direction. If you find a solution that works, let others know and pass on your own tips and insights. You might just have the answer someone else needs. Remember to thank community members who have helped you. Show your appreciation by giving kudos to helpful posts, accepting a solution that answers your question, or posting thank-you replies. We want the community to be appropriate, friendly, informative, and fun for everyone. Be sure to read the Community Terms of Service and the community's Rules and Guidelines so that you know what to expect and what is expected of you when you're here. Posting and replying on the community Posting on the community is easy. Simply go to any area you have permission to see and post in, and click the Start a discussion button - or if you are replying to another person’s post or comment, click the text box toward the bottom of the page. After that, type your text in the message editor and click Publish, Post, or Reply. When typing, you can even mention other community members if the community’s @mention feature is enabled. Just type “@” followed by the member’s user name. A pop-up menu appears as you type. Depending on how members have set up their notifications, they might be notified immediately, and you might get your answer super fast. Following the content you’re most interested in Never miss an update on the topics or the content that matters to you most. Use the Follow button at the top right of any area or post, and have the community notify you when someone posts to a board or replies to your question. You can follow forums, blogs, knowledge bases, or any other location in the community. You can even follow a specific post or a tag applied to a post. Note: When you follow a board or tag, you will be notified by email when a new post is created in that board or with the label. To follow a tag: From a particular post with a label, click on the label to filter by that label. Click the grey bell icon at the top right just underneath the navigation bar. Note: Following tags is only in effect for the post or area where you chose to follow content. For example, if you follow a tag named “contest” in board 1, it doesn’t automatically cause you to follow an identically named label in board 2. You must click the bell icon to follow content twice, once for each board. To view and manage your follows: Go to your profile menu at the top right > My Settings > Follows & Notifications. Scroll down till you see the specific area or content for which you want to unfollow. Click the three-dot menu at the right, and then Unfollow. Using images and videos Members can add images and videos while they author their content, depending on their posting permissions. To find this, check the formatting bar in any post or reply you create, then the camera icon and choose to upload the file. Tagging content A tag is a single keyword or phrase that describes the topic, theme, or subject of a post. Tagging is a way to help other users discover content. It's also a way to organize content in the community that you think is related. When you apply tags to a post, you add to the value by providing another way for people to find it. To add a tag: Go to an interesting post or comment. Scroll to the bottom to see the "Add a tag" option Type the keyword or phrase you want to use to tag Select from the options in the dropdown Please note you won't be able to create new tags. To request a new tag be made available in the community, please email [email protected]. Help community members find answers faster with Accepted Solutions An Accepted Solution is a way for you to choose the reply that best answers a question that you've posted. When you accept a solution, both the question and the solution get special icons and links that take you directly from the question to the answer. An Accepted Solutions icon also appears on boards and in search results so you can see which messages have solutions. You can mark a solution as accepted only for questions that you've posted (you started the thread). Community moderators can also mark one of the replies to a message as an accepted solution. To mark a reply as a solution, click Mark as Solution at the bottom left. If you change your mind or if another reply provides an even better answer, you can revoke the first selection and accept the second reply. To revoke an accepted solution, click Options > Not the Solution. You can choose another reply as a solution or leave the question unsolved. Notifications and Private Messages About Notifications Your Notification Feed can be found at the top right on the navigation bar next to your profile photo. It alerts signed-in members about new activity on their content or on their profile. If you have new notifications, you'll see a pink dot appear next to the bell icon. Your feed might include these notifications: Receiving likes on posts Getting your posts accepted as solutions Getting @mentioned in a thread Achieving a new community rank Achieving a new badge Receiving a reply to a message you started Receiving a reply to a message you're following New topics in a board you're following About Private Messenger Private Messenger enables you to send private messages to other community members. Private Messenger has two big advantages over email: You don't have to know the other member's email address or reveal yours to send the note. You can read and send private messages without leaving the community, making it easy to have a quick conversation with another community member. To use Private Messenger, you must be registered and signed in. Also, for increased security, we require all members to agree to a Terms of Use document. The Private Message indicator appears as an envelope at the top right of the navigation bar. When you have new messages, you'll see a pink icon appear above the envelope. To send a private message: Sign in to the community. Click the envelope icon to go to your Private Messages inbox. Click pencil icon to compose a new message. Enter the recipient's Username and fill out the Subject field. Type your message in the Message Body editor. Click Send Message. You can find messages you've sent in the Sent Messages tab. Commonly Asked Questions Why can’t I access certain content or areas of the community? Some content and areas of the community require you to have specific roles or permissions. So, from time to time, you might come across a link to content or an area you don’t have access to. If you believe that you should be able to access the content or area, email us. Where are the Khoros Developer Docs? Khoros Developer Documentation is hosted at https://developer.khoros.com/. How do I register if I’m a Khoros Marketing customer? First, visit the Atlas homepage, then choose Register at the top right and you'll see a Khoros One SSO option. This enables Khoros Marketing users to sign in or register on Atlas via Signal Sign On (SSO). If you use Khoros Marketing and another Khoros product, we recommend you sign in using Marketing SSO. For more FAQs about Marketing SSO, visit Atlas Single Sign-On (SSO) & Registration for Marketing Customers. How do I register if I’m a Khoros Care or Communities customer? Choose to Register on the community homepage and click the Atlas Sign In button to open the Sign In/Register options. Create a username, password, and enter your email, then read and agree to the Terms of Service. Once you've done all that, click Register. The next step is to verify your email. Check your inbox for an email from the Atlas Community ([email protected]), then click the link to verify your email. If you don’t see the email from the Atlas Community after a few minutes, check your spam and promotional folders. If you still don't see the email, please contact us. How can I get Customer access to Atlas? To request additional access to Atlas, customers/partners can email [email protected]. Be sure to include your name, company, and company email. Without customer/partner access, you’re missing out on exclusive forums, knowledge base articles, and much more. You can also use Maia to request customer access. Just open Maia (chat icon in lower-right corner of Atlas page) and type "Customer access to Atlas" to get started. How can I get Case Portal Access? To get Case Portal access, email Support and include this information: Full Name Email Address Atlas Username Company49KViewsSign in to react to this post0CommentsAurora: About images and video
Most communities enable members to add images and videos to their content. Rich media makes content more visually striking and drives member interest and engagement. Note: Image and video moderation is done in conjunction with content moderation so that inappropriate content is not published to your live site. Learn more about content moderation. Copying content from a Google Doc to Khoros Communities is unaffected by the document's ownership since these are separate applications. However, for images in the content, the community first stores them in its storage, requiring access to the original resource. If the Google Doc is not publicly accessible (i.e., permissions are not set to "Anyone with the link"), the image links will be blocked for users in the community. While writing content, members can add images and videos by: Clicking the Insert Media button in the Content Editor toolbar Dragging and dropping images or videos directly into the Content Editor Copying and pasting images and videos via the clipboard Inline image editing When writing or editing content with embedded images, you perform several quick editing actions. While editing your content, you can click an image to access the sizing controls. Click the small, medium, or large options to choose the image size that best fits your space. Note: You can use the Content Editor toolbar to indent or align the image within the column. Tip: Center-align images in the column to prevent text from wrapping around the image. You can also add a caption for your image, which displays below the image. Finally, you can click the person icon to add Alternative text that describes the image for the visually impaired. Image Viewer When viewing content in a piece of content, you can click any image to view it in the image preview pane. Use the left and right arrows to scroll through any other images in the post. Click the Download option in the top-right corner of the viewer to download a local copy of the image. Banner images for blogs Aurora communities enable you to add banner images to blog posts. You can create and upload your own image or find an image in an online library, powered by Unsplash. Learn more about creating a blog post. Related topics: Manage image and video settings and permissions747ViewsSign in to react to this post2CommentsTake a tour of Aurora
Welcome to Aurora. We've put together this video training course to help you get familiar with key features and concepts about Khoros' re-imagined Community Experience. This 12-video series is grouped by four community roles: Managers Moderators Developers Members The entire course takes about 1 hour to complete. Note: We will be updating these videos and adding new ones as we continue to roll out new Aurora features. Subscribe to this article to be notified when new videos are available. Community Managers Community Overview Building your community structure Designing your site Configuring feature settings Roles and permissions Gamification Measuring success Community overview (3:49) Building your community structure (6:03) Designing your site (7:54) Configuring feature settings (4:52) Roles and permissions (4:51) Gamification (4:23) Measuring success (3:08) Community Moderators Moderating your community (9:14) Community Developers Getting Started as a Developer Getting Started with Handlebars Creating Handlebars GraphQL API Getting Started as a Developer (4:58) Getting Started with Handlebars (6:56) Creating Handlebars (4:20) GraphQL API (3:54) Community Members Personalize your community experience Getting around and finding the content you want Contributing to the community Using your inbox Personalize your community experience (3:45) Getting around and finding the content you want (1:54) Contributing to the community (4:55) Using your inbox (2:46) What to read next: Getting Started as an Administrator Getting Started as a Community Manager Getting Started as a Site Designer4.4KViewsSign in to react to this post0CommentsAbout Khoros Community: Aurora
Aurora is Khoros’ re-imagined Community experience that leverages more than 20 years of experience and learnings in the digital community space. Aurora delivers a sleek, modern, high-performance UX framework that adheres to community best practices while still giving brands complete flexibility to make changes or updates to address their specific needs. While built on the same platform as Khoros Community Classic, Aurora includes significant changes in the new framework: New member experience: Aurora delivers both better performance (load times, mobile-friendly pages) and design (modern UX, beautiful layouts, and pre-configured community best practices). Aurora also provides more personalization, integration with other digital properties through syndication, and an overall better experience so that communities can more easily become the heart of any brand’s digital experience. New community manager experience: Aurora enables community managers and designers to build and customize pages easier with a visual Page Template designer and control the look and feel of the community with pre-defined and customizable themes to ensure that your community reflects the visual message and tone of your brand. Moreover, you no longer need to know how to code to build these pages. New developer experience: Aurora improves the developer experience so your developers can more easily find, use, test, and extend any integrations, custom objects, or data calls (in and out of the community) to extend the capabilities of your community to do something new and provide your members with a more customized experience. Backend and Platform changes: Aurora uses new front-end technologies like React and Storybook and leverages tools like Jest and Typescript for rapid iteration and robust design. On the data side, Aurora uses GraphQL (replacing LiQL) as the way to program API interactions and get data out of the platform. Finally, the entire architecture is completely built on modern cloud services from AWS and Docker. When you’re ready to dive in, we recommend starting with one of our Getting Started Guides: Getting Started as a Community Manager Getting Started as a Community Administrator Getting Started as a Site Designer New to communities? Check out our Community Basics and take a tour of Aurora in this 1-hour video training course, which will help you familiarize yourself with key Aurora features and concepts. Moving to Aurora Since Aurora is built on the same backend data architecture as Community Classic, existing customers do not need to do a full-scale migration to move to Aurora. However, most Community Classic customers do have some customization on the front end and UI. For these customers, some additional work is required to move to Aurora. Review the Aurora Upgrade Playbook and reach out to your account manager to learn more about what to expect when migrating to Aurora. Related topics What's changed in Aurora from Community Classic Glossary of common Community Aurora terms4.7KViewsSign in to react to this post0CommentsAurora: Enable a site-wide cookie usage notification banner
As part of the new data privacy regulation in the European Union (EU), websites are required to provide an explicit user consent for the usage of tracking cookies. Companies must also provide access to a description of the information collected/stored in those cookies. To enable the cookie banner for your community: Sign in to your community as an Admin. Open the Account menu and click Settings. Go to System > Account & Privacy. Under General, Select the Turn on cookie policy notification banner option and enter the URL for your cookie/privacy policy. Note: If you leave the URL field blank, the Learn more link in the banner goes to Khoros’ public Cookie Datasheet page. Click Save. When the cookie banner notification is enabled, every page on your community site displays the “this website uses cookies” banner: The banner is displayed on your community site for each visitor until that visitor clicks the Accept or Decline button. Visitors who click Preferences are presented with more granular cookie privacy options to manage. After visitors confirm their selections, these preferences are saved in their browser and the banner disappears. Users must click Accept in the cookie banner and explicitly confirm their consent to activate the community cookies. Once accepted, the cookie does not appear in subsequent sign-ins. If visitors click Decline, only the Type 1 cookies (“Strictly Necessary”) are set, and all other cookies are held back. Once rejected, the cookie banner does not appear in subsequent logins. If visitors do not accept or decline and continue to browse the community, only the Type 1 cookies (“Strictly Necessary”) are set, and all other cookies are held back. The banner continues to show in subsequent sign-ins. About the use of the cookie banner and its impact on visitor metrics As required by the ePrivacy Directive in EU, this banner also blocks tracking cookies until there is an affirmative action from the visitor. This is accomplished by rejecting (clicking the Reject button on the banner) or continuing to browse the site. Note that blocking tracking cookies until there is an affirmation from the member will have an impact on “Visits” and “Unique Visitors” metrics accuracy. Each new request of such member is considered a new, billable visit. Customers on billing visits will be affected. Learn more about Khoros cookies in our Khoros Cookies Data Sheet.646ViewsSign in to react to this post0CommentsGDPR “soft-delete” period for Aurora
As part of our support for GDPR, we have provided for a soft-delete period for all member account deletions. During this period of time, you can undo an account deletion and restore the deleted account. To request an account restore, open a Support ticket and include the user ID of the account you want restored. This soft-delete window provides a built-in safety feature to handle any accidental or malicious deletes. After the soft-delete window (default is set to 10 days) has passed, deleted accounts cannot be recovered. During the soft-delete period, the username is reserved and cannot be used when creating a new account. After the soft-delete period elapses, the deleted username is made available again for new members. Note: This 10-day period is subsumed in 30-day SLA for user deletes. Note: When querying for the number of deleted accounts via the API, the response does not include any accounts in a soft-delete state, only accounts that have been hard deleted. The soft-delete period set to 10 days by default but is configurable. The recommended maximum value is 10 days so as to not risk the GDPR-mandated 30-day SLA for account deletions. To request a change to the default value of 10 days, open a Support ticket. No action is required on your part to activate this feature and use the default configuration.446ViewsSign in to react to this post0CommentsGDPR and CPPA FAQs for Aurora
What is GDPR? GDPR stands for General Data Protection Regulation. GDPR went into effect on May 25, 2018 and is a regulation by which the European Parliament, the Council of the European Union, and the European Commission intend to strengthen data protection for all individuals in the European Union. What is CCPA? CCPA stands for the California Consumer Privacy Act of 2018. The CCPA went into effect on January 1, 2020 and grants California consumers certain rights over their personal information. Who has to comply with the GDPR and CCPA? Under GDPR, data controllers and Data Processors who are based in the EU and/or collect or process personal data of EU residents (regardless of where the Data Controller or Data Processor is located). Under CCPA, companies doing business in California, which such entity is defined under the act as a legal entity that collects personal information from consumers and it determines the means for processing that information. The CCPA also applies to service providers, which are defined under the CCPA as a company handling PII on behalf of a business for a business purpose. How do I get GDPR/CCPA enabled for my Aurora community? GDPR/CCPA is enabled by default for all Khoros Communities. Who's who under GDPR and CCPA? Under GDPR, a Data Controller is the entity that determines the purposes, conditions, and means of the processing of personal data, while the Data Processor is an entity which processes personal data on behalf of the controller (Learn more). A Data Subject is an individual person who is an EU resident. Under CCPA, a Business is the entity that determines the purposes, conditions, and means of the processing of personal data, while the Service Provider is an entity which processes personal data on behalf of the business. A consumer is an individual person who is a California resident. In the context of “Online Communities”, the business or brand running the Community is the Data Controller under GDPR or "business" under CCPA, and Khoros is the Data Processor under GDPR and "service provider" under CCPA. The Community end-user is the Data Subject under GDPR and "consumer" under CCPA. What constitutes PII in Online Communities? The list of PII fields are email, login, first name, last name, title, URL home page, biography, notes, location, signature, browsing history, search history, avatars, cover image, language, IP address, and device ID. What does Khoros do to provide GDPR/CCPA support? Khoros provides support for GDPR/CCPA compliance by offering ways to view, edit, obtain a machine-readable copy of, and delete members’ Personally Identifiable Information (PII). Enhancements will cover three areas: PII retrieval PII deletion Demonstrating Compliance PII deletion, when exercised, will permanently anonymize the PII of the members and attribute the content to an “Anonymous User”. The “Anonymous User” will have a standard username and a default avatar to distinguish it from other members. As a Data Processor/service provider, Khoros is only permitted to follow the instructions of the Data Controller/business. So, availability of a feature to the end-user will be dependent on the Data Controller/business (brand) enabling it. Note: The data that is deleted will only be the PII of the member, while the member's contributions (posts, comments, likes, etc.) will be maintained as and associated with an anonymous user. The delete triggers a downstream handling to purge PII data from Khoros Community Analytics as well. What happens to PII data when deleted? Member PII data is permanently anonymized and attributed to “Anonymous User”. The “Anonymous User” has a standard username and a default avatar to distinguish it from other users. Can the user see the PII data in Community? If yes, where? Yes, members can view, edit, obtain a machine-readable copy of, and delete the PII relevant to themselves, as described in Manage your community content and personal information. Will the member delete action also remove posts, replies, likes, etc.? No. A member's contribution (posts, comments) and engagement (likes, accepted solutions) is retained. They are disassociated from the original member account. Will PII data in posts, replies, etc., be removed? No. Members are advised not to share any personal data in posts or attachments, and the Community moderation policy is expected to enforce this. The member delete option does not systematically auto-clean any personal data inadvertently included in posts, attachments, messages, etc. This falls under the purview of Community moderation. What is the SLA for User deletes? The SLA for User Delete is 30 days. Can the user recover the Community account if he/she changes the decision later on? No, the deletion is permanent. If someone wants to rejoin the Community, they need to sign up again. What if the person wants to use the same user name again? If available, the people might be able to use the same user name in the Community. However, it will be treated as a new account with no association to the previous member. Where is a user's PII stored? PII data is not stored in user databases, caches, and file storage. As part of any delete operation, Khoros purges all these stores of the PII data. For more information on geographic data locations, see the Khoros Data Location and Sub Processor Guide or the summary located here. How will backups and logs be handled? According to the standard rotation policy, backups are rotated every 90 days, and all member deletes will flow through the system for a maximum of 90 days. The same time period is associated with Application logs. They are rotated in 90 days according to the retention policy and all user deletes will flow through the system in that time period. PII will be removed from Event Logs. Also, a one-time rewrite will be performed to remove all PII information stored historically. Our backups are encrypted and access-controlled. In the rare event of a restore from backup, any PII that was previously removed will be deleted again to ensure continued compliance. Will community metrics reflect the deleted user? Yes, Community Analytics remove the PII of the user from its systems. However, it does not modify the metrics retrospectively. In other words, after anonymizing a member, we do not show the member’s name or any other PII information in any of the reports. However, the member's anonymous statistics continue to be counted in historical aggregate metrics, for the relevant periods. It was mentioned that Khoros will support export of PII-related data; what about a user’s posts? Can a user's posts be exported as well? Yes, it will be possible to export a member's posts. How are PII-fields from the customizations handled? Contact Khoros Support and provide the list of custom, personal fields to be marked as PII. We flag them as PII. Once flagged, these fields are handled in the same way as any of the out-of-the-box PII fields with respect to viewing, deleting, and exporting. What is the level of support for demonstrating compliance? As part of GDPR/CCPA support, Khoros publishes a standard operating procedures. In these procedures, Khoros documents the processes and PII-related data handling by capturing where all PII is stored or processed; where it comes from, where it goes, and who has access to it. Khoros plans to document all the processes and steps taken to ensure GDPR/CCPA compliance. These are available to auditors to assess our processes with regard to GDPR/CCPA compliance. The Audit log does not contain any PII data that can be associated with the Data Subject. An Auditor can also validate a data subject’s controls and rights by mimicking member actions and exercising the ‘right to be forgotten’. What’s Khoros recommendation on cookie banners? We recommend that brands (the data collector) address site cookies (both Khoros' and your own) via a single, customizable pop-up banner to avoid the need for multiple cookie banners (one from the Khoros platform, the other from customer-specific cookies). Providing your own banner enables you to customize it for your brand's look and feel and any specific, legal content. Khoros Communities provide an out-of-the-box cookie banner solution. Learn how to enable the cookie banner for your community. LEGAL DISCLAIMER – NO LEGAL ADVICE The above content is provided for informational purposes only and does not constitute legal advice. You should seek the advice of your legal counsel regarding your GDPR compliance efforts. LEGAL DISCLAIMER ABOUT ROADMAP VOLATILITY This represents Khoros’ current view of its product roadmap. Khoros releases software monthly and adjusts its roadmap based on market conditions and updated requirements between releases. This document is intended for informational purposes only, and because of potential volatility, it should not be used to develop contractual commitments, make assumptions about product pricing or packaging, nor used for planning purposes. Khoros makes no warranties, express or implied, in this document.487ViewsSign in to react to this post0Comments
25KViews
0Comments
