VK WorkSpace Adds Guest Access Without Accounts, Password Protection, Polls, and File Uploads Up to 30 MB
VK Tech has released an update to the cloud version of VK WorkSpace Board, introducing several new capabilities aimed at simplifying collaboration with external users while strengthening access controls.
External participants such as clients, contractors, and other guests can now be invited to boards without the need to create a VK WorkSpace account. To prevent unauthorized changes, board owners can protect access with a password and define precise permissions for each guest, including view-only mode, commenting rights, or full editing capabilities. Guests remain restricted from creating new boards or accessing version history.
Domain administrators gain the ability to enforce password protection as a mandatory requirement for all boards that allow guest access, reducing risks if links are shared incorrectly.
The update also adds built-in polls with automatic result tallying, enabling teams to collect input on ideas, set priorities, or conduct retrospectives without manual counting of votes.
Users can now upload files up to 30 MB in size; these files are automatically scanned by antivirus software before being made available for download by other participants.
For improved navigation on large projects, a mini-map feature has been introduced. Completed boards can be copied or exported in multiple formats including SVG, PNG, JPG, PDF, and CSV.
Additionally, VK WorkSpace now offers a full English-language interface. According to Petr Shcheglov, head of productivity services at VK Tech, working with clients, contractors, and candidates has become one of the primary collaboration scenarios, and the new guest access options make inviting external users significantly easier.
Related articles
Why 99% Attack Detection Rules Generate 99.9% False Positives in Real SOC Environments
A detection rule claiming 99% attack coverage with only 1% false positive rate sounds effective on paper, yet in practice it produces roughly one thousand false alerts for every genuine incident. Using a realistic example of 200,000 daily logins containing just two real compromises, the article demonstrates that 1.98 true positives are buried among 2,000 false positives. Bayes' theorem explains why sensitivity improvements barely move the needle while reducing the false-positive rate or narrowing the population yields dramatic gains in precision. The piece outlines three practical levers—lowering FPR, scoping rules to high-risk accounts, and cascading cheap-then-expensive checks—that cut analyst workload by orders of magnitude without sacrificing meaningful coverage. It also warns that chronically low-precision rules train analysts to ignore alerts, eventually leading to the rule being disabled despite remaining in compliance matrices. The recommended metric pair is therefore confirmed detections alongside coverage, rather than coverage alone.
ChatGPT Knows Your Company but Google Doesn't: Step-by-Step Guide to Diagnosing AI Visibility Issues
The complaint that a brand is missing from AI answers often masks six distinct technical problems that require opposite fixes. The guide separates three visibility layers—model knowledge without search, pre-indexed search bots such as OAI-SearchBot, and on-demand agent bots such as ChatGPT-User—and explains how to measure each one. It details checks for robots.txt entries, nosnippet and max-snippet meta tags, Cloudflare AI bot toggles, and server logs that reveal 403, 429, and 404 responses from specific crawlers. Additional steps cover JavaScript-rendered content, repeated query testing across 20 prompts, official reports in Yandex Webmaster and Google Search Console, and hidden prompt-injection instructions that may have been planted in page metadata. The article stresses that aggregated “AI visibility” percentages are meaningless without layer separation and warns that blocking training can unintentionally harm ordinary search indexing.
redb.Identity Adds gRPC Transport for OpenID Server Alongside Existing HTTP Facade
redb.Identity has introduced a second transport layer using gRPC next to its existing HTTP interface, sharing the same core routes, client registry, token store, and authorization logic. The new facade exposes standard OAuth and OpenID Connect operations such as Token, Introspect, Revoke, UserInfo, Discovery, and Jwks through protobuf-defined methods under identity.v1.Identity. Both transports enforce identical verdicts based on a single centralized scope table located behind direct-vm addresses, ensuring that a client authorized via HTTP receives the same result when calling gRPC. Error handling on gRPC uses status codes and trailers to carry machine-readable OAuth error codes and retry-after values, preserving compatibility with existing interceptors and tracing. Browser-facing flows, DPoP proofs, and user self-service remain on HTTP, while administrative operations are available on a separate management port. The implementation was validated through 64 unit tests, cross-language interop with @grpc/grpc-js clients, and a conformance run against the official OpenID Foundation suite.
Nvidia to Cease Regular GeForce Driver Updates for Windows 10 After October 2026
Nvidia has announced the end of regular driver support for Windows 10 in its GeForce Game Ready and Nvidia Studio driver lines starting October 2026. The first driver package without Windows 10 support will arrive in November of that year. Microsoft ended the base lifecycle of Windows 10 on October 14, 2025, and Nvidia is extending support by one additional year. Existing games and applications will continue to function after the change, while quarterly security patches for critical vulnerabilities will remain available until October 2029. Users will no longer receive optimizations for new games, fixes for graphics issues, or new GPU features. Newer technologies such as DLSS may also skip Windows 10 compatibility. The transition is described as gradual rather than abrupt, allowing older titles to keep running while newer releases increasingly encourage migration to a supported Windows version.