{ "id": "2d40497f-cc0d-4393-9783-03ff348ec971", "created_at": "2026-04-06T00:20:18.258279Z", "updated_at": "2026-04-10T03:23:52.406555Z", "deleted_at": null, "sha1_hash": "849de5089af920e56a45775aeb4c019d2d0e6fdc", "title": "Google Workspace Updates: New community features for Google Chat and an update on Currents", "llm_title": "", "authors": "", "file_creation_date": "0001-01-01T00:00:00Z", "file_modification_date": "0001-01-01T00:00:00Z", "file_size": 1338113, "plain_text": "Google Workspace Updates: New community features for Google\r\nChat and an update on Currents\r\nArchived: 2026-04-05 17:37:26 UTC\r\nApril 12, 2023\r\nCurrents\r\nGoogle Chat\r\nOther\r\nNote: This blog post outlines upcoming changes to Google Currents for Workspace users. For information on the\r\nprevious deprecation of Google+ for users with personal Google accounts, please see this post. \r\nWhat's Changing\r\nLast year, we announced plans to wind down Currents, to focus efforts on community experiences that are\r\nbetter integrated with the rest of Google Workspace. To help our customers manage this transition, we published\r\ndetailed guidance for Workspace administrators and enabled customers to opt-in for automated migration of\r\nCurrents data to spaces in Google Chat. \r\nWe are nearing the end of this transition. Beginning July 5, 2023, Currents will no longer be available. Workspace\r\nadministrators can export Currents data using Takeout before August 8, 2023. Beginning August 8th, Currents data\r\nwill no longer be available for download. \r\nAlthough we are saying goodbye to Currents, we continue to invest in new features for Google Chat, so teams can\r\nconnect and collaborate with a shared sense of belonging. Over the last year, we've delivered features designed to\r\nsupport community engagement at scale, and will continue to deliver more. Here is a summary of the features\r\nwith additional details below: \r\nhttps://plus.google.com/+AdrianLudwig/posts/GXzJ8vaAFsi\r\nPage 1 of 7\n\nhttps://plus.google.com/+AdrianLudwig/posts/GXzJ8vaAFsi\r\nPage 2 of 7\n\nThis month, we’re enabling new ways for organizations to share information across the enterprise with\r\nannouncements in Google Chat. This gives admin controls to limit permissions for posting in a space, while\r\nenabling all members to read and react, helping ensure that important updates stay visible and relevant. Later this\r\nyear, we plan to simplify membership management by integrating Google Groups with spaces in Chat, enable\r\npost-level metrics for announcements, and provide tools for Workspace administrators to manage spaces across\r\ntheir domain. \r\nAnnouncements in Google Chat\r\nhttps://plus.google.com/+AdrianLudwig/posts/GXzJ8vaAFsi\r\nPage 3 of 7\n\nManaging space membership with Google Groups\r\nWe’ve already rolled out new ways to make conversations more expressive and engaging such as in-line\r\nthreading to enable rich exploration of a specific topic without overtaking the main conversation and custom\r\nemojis to enable fun, personal expression.\r\nhttps://plus.google.com/+AdrianLudwig/posts/GXzJ8vaAFsi\r\nPage 4 of 7\n\nIn-line threaded conversations\r\nDiscover and join communities with up to 8,000 members\r\nWe’ve also made it easier for individuals to discover and join communities of shared interest. By searching in\r\nGmail, users can explore a directory of available spaces covering topics of personal or professional interest such\r\nas gardening, pets, career development, fitness, cultural identity, and more, with the ability to invite others to join\r\nvia link. Last year, we increased the size of communities supported by spaces in Chat to 8,000 members, and we\r\nare working to scale this in a meaningful way later this year. \r\nhttps://plus.google.com/+AdrianLudwig/posts/GXzJ8vaAFsi\r\nPage 5 of 7\n\nA directory of spaces in Google Chat for users to join.\r\nAs communities grow, it’s essential to provide tools for content moderation and data management. Last year,\r\nwe introduced space managers, a community lead with abilities to moderate conversation and manage\r\nmembership, and last year at NEXT, we rolled out data loss prevention (DLP) for Chat. We will continue to\r\nenhance community health and data security for Google Chat. \r\nOur partner community is extending the power of Chat through integrations with essential third-party apps\r\nsuch as Jira, GitHub, Asana, PagerDuty, Zendesk and Salesforce. Many organizations have built custom\r\nworkflow apps using low-code and no-code tools, and we anticipate that this number will continue to grow with\r\nthe GA releases of the Chat API and AppSheet’s Chat app building capabilities later this year.\r\nFor teams to thrive in this rapidly changing era of hybrid work, it’s essential to build authentic personal\r\nconnections and a strong sense of belonging, no matter when or where individuals work. We will continue to make\r\nGoogle Chat the best option for Workspace customers seeking to build a community and culture for hybrid teams,\r\nwith much more to come later this year. \r\nWho's impacted\r\nAdmins and end users\r\nDen här webbplatsen använder cookies från Google för att tillhandahålla tjänster och analysera trafik. Din IP-adress och användaragent delas med Google tillsammans med information om prestanda och säkerhet för att\r\nhttps://plus.google.com/+AdrianLudwig/posts/GXzJ8vaAFsi\r\nPage 6 of 7\n\ngarantera tjänstens kvalitet, generera användningsstatistik samt upptäcka och förhindra otillåten användning.Läs\r\nmerOK\r\nSource: https://plus.google.com/+AdrianLudwig/posts/GXzJ8vaAFsi\r\nhttps://plus.google.com/+AdrianLudwig/posts/GXzJ8vaAFsi\r\nPage 7 of 7", "extraction_quality": 1, "language": "EN", "sources": [ "MITRE" ], "references": [ "https://plus.google.com/+AdrianLudwig/posts/GXzJ8vaAFsi" ], "report_names": [ "GXzJ8vaAFsi" ], "threat_actors": [ { "id": "d90307b6-14a9-4d0b-9156-89e453d6eb13", "created_at": "2022-10-25T16:07:23.773944Z", "updated_at": "2026-04-10T02:00:04.746188Z", "deleted_at": null, "main_name": "Lead", "aliases": [ "Casper", "TG-3279" ], "source_name": "ETDA:Lead", "tools": [ "Agentemis", "BleDoor", "Cobalt Strike", "CobaltStrike", "RbDoor", "RibDoor", "Winnti", "cobeacon" ], "source_id": "ETDA", "reports": null } ], "ts_created_at": 1775434818, "ts_updated_at": 1775791432, "ts_creation_date": 0, "ts_modification_date": 0, "files": { "pdf": "https://archive.orkl.eu/849de5089af920e56a45775aeb4c019d2d0e6fdc.pdf", "text": "https://archive.orkl.eu/849de5089af920e56a45775aeb4c019d2d0e6fdc.txt", "img": "https://archive.orkl.eu/849de5089af920e56a45775aeb4c019d2d0e6fdc.jpg" } }