Column

[Updated August 19, 2026] Regarding the Discontinuation Date of “Content Management (Legacy)” We have updated part of the content in this article. The discontinuation date for “Content Management (Legacy),” which was originally announced as “September 16, 2026 (Ver. 7.0),” is now undecided. We plan to discontinue this screen in the future. We will announce the discontinuation date at a later time. Please continue to make the necessary changes to the URL settings in the dashboard and side menu. We are officially relaunching “Course Management (β)” as “Content Management,” a new feature with improved performance and usability. Accordingly, we will switch to the new interface on March 18, 2026 (Ver. 5.0). At the same time, the previous “Content Management” will be designated as “Content Management (Legacy)” and will be available via a dedicated URL for a limited time before being discontinued. We will announce the discontinuation date at a later time. ■ Affected Feature: Course Management (β) *There is a page explaining this feature. Please refer to it here. ■ Changes (Overview): “Course Management (β)” will be renamed to “Content Management” and will henceforth be provided as the new “Content Management.” Please note that for a limited time, if you access the URL for the previous “Content Management” (old URL), you will be automatically redirected to the URL for the new “Content Management.” *The previous “Content Management” will be renamed to “Content Management (Legacy)” and will be available via a dedicated URL for a limited time only. (For compatibility and temporary verification purposes) ■Schedule 1. Switch to the new interface: Starting March 18, 2026 (Ver. 5.0) 2. Name change Before change After change Course Management (β) Content Management Content Management Content Management (Legacy) 3. Redirect (Automatic Redirection) Period Period: March 18, 2026 (Ver. 5.0) – Until “Content Management (Legacy)” is discontinued Details: If you access the URL for the legacy “Content Management” (old URL), you will be automatically redirected to the new “Content Management.” 4. Discontinuation of the Old Interface “Content Management (Legacy)” is scheduled to be discontinued in the future. We will announce the discontinuation date at a later time. Upon discontinuation, the redirect will be stopped and “Content Management (Legacy)” will be discontinued. ■ Actions Required by Customers (Important) Due to the transition to the new interface, we ask that some customers take the following actions regarding their settings. ① Changing the Dashboard URL Affected Users: All customers Action Period: March 18, 2026 (Ver. 5.0) and later; please take action as soon as possible After the discontinuation of “Content Management (Legacy),” access (redirects) via the previous “Content Management” URL (legacy URL) will be removed, so you will no longer be able to access the service using that URL. We apologize for the inconvenience, but customers who have registered the legacy “Content Management” URL (old URL) in their dashboard are requested to update the setting to the new “Content Management” URL starting with Version 5.0. ・ URL after changing “Content Management” settings: /courses/course-management Please refer to this page for detailed instructions. *As of the Ver. 5.0 release, attempting to access the previous “Content Management” URL (legacy URL) will automatically redirect you to the new “Content Management.” ② Side Menu Configuration Change Target: Customers using the Site Customizer Action Period: Starting March 18, 2026 (Ver. 5.0); please take action as soon as possible After “Content Management (Legacy)” is discontinued, the redirection process for the legacy “Content Management” URL will be removed, so you will no longer be able to access the service via that URL. We apologize for the inconvenience, but please make the following configuration changes starting with Version 5.0: ・Moving (Hiding) the “Course Management (β)” Menu *As of Version 5.0, the URL for the “Content Management” menu will automatically be updated to the new URL. Please refer to this page for detailed instructions. ③ Resetting the System Language Set in “Content Management (Legacy)” Who this applies to: Customers using the Site Customizer Even if you changed the system language in “Content Management (Legacy),” that setting may not be reflected when switching to “Content Management.” If the system language displayed after the switch is not the one you intended, please take the time to reconfigure the language settings. Note: System Language Settings Some users may need to review and update the content of their current user manuals and training materials. To ensure a smooth transition after the switch, please try out the new interface (currently displayed as “Course Management (β)”) in advance to familiarize yourself with its operation. * Please see below for an overview of the main changes and additions to the new screen (currently labeled “Course Management (β)”). ・ Course Management (β) Summary of Changes (PDF) ・ Course Management (β) Explanation (Video) If you have any questions, please contact us via the inquiry form.

Imagine if an important business message or a newsletter you put your heart into ended up in the recipient’s “Junk” folder. In fact, this issue is almost always caused by the sender domain authentication configured in the DNS (Domain Name System), rather than the content of the email itself. The DNS is a system that links domains to servers on the Internet, and it also serves as the foundation for determining the credibility of emails. In February 2024, Google significantly strengthened its sender guidelines. Businesses that send more than 5,000 emails per day are now required to implement all three of the following: SPF, DKIM, and DMARC. Furthermore, starting in January 2025, NTT Docomo will begin gradually displaying “spoofed email warnings” on emails that do not have sender domain authentication enabled. We are now entering an era where emails with incorrectly configured DNS settings simply won’t be delivered. However, there are likely many people who think, “SPF? DKIM? DMARC? What are those? I don’t really understand.” In this article, we’ll thoroughly explain how these three technologies work, their differences, and how to configure DNS—all in a way that’s easy to understand even for those with zero technical knowledge. Why is “sender domain authentication” necessary right now? Damage caused by phishing emails is increasing year by year, leading to financial losses for companies, data breaches, and even damage to their brand reputation. The technologies known as SPF, DKIM, and DMARC are designed to counter these threats. SPF (Send-From Policy Framework) is a mechanism that verifies whether the sending server is legitimate. DKIM (Digital Key Identification Message) applies a digital signature to emails to verify “whether the message has been spoofed” and whether the content has been tampered with. DMARC is a policy that determines how to handle emails that fail SPF or DKIM authentication based on the results of those checks. By configuring these technologies properly, you can significantly reduce the risk of spoofed emails. Let’s take a closer look at their importance. The Current State of Phishing Emails In recent years, damage caused by “phishing emails”—which impersonate real companies or individuals—has surged. There have been cases where emails posing as business partners have infected recipients with malware (a general term for software created for malicious purposes), leading to the leakage of personal information, or where emails instructing recipients to transfer funds to fake bank accounts have been used to defraud them of money. What makes spoofed emails so sophisticated is that, from a technical standpoint, the “From” address can be freely altered. Attackers impersonate legitimate company domains to send emails that appear completely legitimate at first glance. It is extremely difficult for humans to distinguish these from genuine emails, which is precisely why incidents continue to occur. Furthermore, phishing emails pose a direct risk of brand damage. If your company’s domain is misused to send a large volume of phishing emails, it could significantly erode recipients’ trust. Furthermore, this could cause even legitimate emails to be filtered into the spam folder, potentially disrupting important communications with customers. Impact of Gmail Sender Guidelines In February 2024, Google strengthened its “Sender Guidelines.” The guidelines are summarized as follows: Mandatory for all senders: Compliance with either SPF or DKIM. High-volume senders (5,000 or more emails per day): Compliance with all three—SPF, DKIM, and DMARC. Failure to comply may result in emails not reaching Gmail users. Furthermore, in practice, DKIM is becoming virtually mandatory even for non-high-volume senders, as emails without DKIM are highly likely to be flagged by Gmail’s spam filter. [Reference] Gmail, “Guidelines for Email Senders”; NTT Docomo’s “Phishing Email Warning” Starting in January 2025, NTT Docomo began gradually displaying “phishing email warnings” for emails that do not support sender domain authentication. For businesses that send emails to individual users, compliance has become an urgent priority. [Reference] NTT DOCOMO, “Spoofed Email Warning Display” Return to Table of Contents How Are Emails Sent? (Very Basic) To understand sender domain authentication, the first thing you need to know is the difference between the “envelope From” and the “header From.” The mechanism of email is easier to understand if you compare it to the relationship between an envelope and a letter. Envelope “From” (Sender) This is the sender for delivery purposes. In postal terms, it’s the name written on the envelope. It is not displayed on the recipient’s screen. Letter “From” (Sender) This is the sender displayed on the screen. The “sender information” we see on our email inbox screen refers to this one. Spammers exploit this. The Basic Structure of Email (Envelope From and Header From) Even if the sender on the envelope differs from the sender of the letter, the email will still be delivered. It’s also possible to change only the name that is displayed. For example, an email can be sent from one location while appearing to come from “info@大手銀行.co.jp.” This is the technique used in spoofed emails. SPF, DKIM, and DMARC are mechanisms designed to prevent this problem. For now, just remember that “there are two senders.” Back to Table of Contents What is SPF? (A Mechanism for Verifying the Sender’s IP) SPF is the first step in preventing spoofing. It’s a system where you register the servers authorized to send emails from a given domain in the DNS. When Gmail receives an email, it verifies whether the sender is legitimate. Let’s start by understanding this “sender verification” mechanism. Basic Concepts of SPF SPF (Sender Policy Framework) is a mechanism for pre-registering in DNS the servers that are authorized to send emails from a given domain. For example, you would pre-register information in the DNS such as, “Emails from example.com are sent only from the server with IP address 203.0.113.1 (*for illustrative purposes only).” The recipient checks whether the IP address of the server that actually sent the email is included in that registered list. If the email is sent from an IP address not on the list, it can be judged as a “potentially spoofed email.” How SPF Works The SPF verification process follows these steps: The sender sends the email. The receiving server records the IP address of the server from which the email arrived. It queries DNS using the domain in the “Envelope From” field (e.g., example.com). It compares the SPF record in the DNS TXT record with the actual sender’s IP address. If they match, the result is “SPF authentication passed (Pass)”; if there is a mismatch, it is judged as “Fail/SoftFail” How SPF Works: The receiving server references DNS to verify the IP address How to Read SPF Records (Reference) The actual SPF record is written in a DNS TXT record as follows: v=spf1 include:spf.google.com ip4:203.0.113.1 ~all Meaning of each element v=spf1: Declaration of SPF version 1 include:spf.google.com: Allow sending from Google’s mail servers as well (when using external services such as Gmail) ip4:203.0.113.1: Permits sending from this IP address ~all: Treats all other sources as “SoftFail” (a warning) (whereas -all results in a complete rejection) The difference between ~all and -all lies in the severity of the response to an SPF failure. While -all (HardFail) recommends complete rejection, it is often recommended to start with ~all and monitor the situation first, as there is a risk that legitimate emails may be falsely flagged when relayed. Limitations of SPF Reading this far, you might think, “If I configure SPF, I can prevent spoofing.” However, SPF alone is not sufficient. In fact, SPF has inherent weaknesses that are structurally unavoidable. SPF does not verify the “From” header; it verifies only the envelope “From” (the sender listed on the envelope). It does not verify the “From” header displayed in email clients (the sender of the message). In other words, SPF alone cannot prevent spoofing where the “Envelope From” is set to the legitimate domain, but the “From” header is forged. Cannot Handle Forwarding When an email is forwarded, the forwarding server’s IP address becomes the new “sender IP.” However, since the forwarding server’s IP is not registered in the SPF record, SPF authentication fails even though the email is legitimate. DKIM, which we’ll explain next, was introduced to address these weaknesses. Back to Table of Contents What is DKIM? (Digital Signatures to Prevent Tampering) If SPF is a mechanism for verifying the “sending server,” the next step is a mechanism to verify whether “the email itself is genuine.” This is where DKIM comes in. Basic Concept of DKIM If SPF is a “list of authorized sending servers,” then DKIM is a “seal of authenticity.” The concept of DKIM is similar to affixing a company seal to an important document. The sender applies an “electronic signature” to the email, and the recipient verifies that signature to confirm that “this email was created by the genuine sender and has not been tampered with in transit.” How DKIM Works DKIM is a mechanism for applying an “electronic signature” to emails. While SPF verifies the sender’s IP address, DKIM verifies whether “the email was sent from a legitimate source (not a spoof)” and whether “the email’s content has not been tampered with.” DKIM operates using digital signatures based on public-key cryptography. The sender’s process is carried out as follows: Calculate a hash value from the email’s contents (headers + body). Encrypt the hash value with a private key to create a “signature.” Attach the signature to the email as a DKIM-Signature header and send it. * A hash value is a fixed-length string generated by applying a special calculation (a hash function) to data; it is produced through a one-way (irreversible) transformation that cannot be reversed. The recipient’s process is carried out as follows: Retrieve the signing domain (d=) and selector (s=) from the DKIM-Signature header. Retrieve the public key from DNS. Decrypt the signature using the public key to extract the hash value. Verify that it matches the hash value of the received email body. * d= (signing domain) refers to the domain name that signed the email. This means “This domain is responsible.” *s= (selector) is the name (identifier) used to locate the public key. It allows a single domain to use multiple keys. How DKIM Works: Detects email tampering using digital signatures based on public-key cryptography. If there is a match, “DKIM authentication succeeds,” confirming that the email has not been tampered with and was created by the genuine sender. Contents of the DKIM-Signature (for reference): The DKIM-Signature actually added to the email header has the following structure: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=example.com; s=google; …omitted… bh=hash value; b=signature data Main parameters d= (domain): The domain that performed the signature. Important values used for DMARC alignment checks s= (selector): The key used to look up the public key in DNS a= (algorithm): The signing algorithm (rsa-sha256 is common) What is a selector? A selector is an identifier used to distinguish between multiple DKIM key pairs within a single domain. For example, if d=example.com and s=google, the receiving server retrieves the public key by referencing the DNS record google._domainkey.example.com. This allows you to manage multiple email services using separate selectors. Mechanism for Using Different Keys Across Multiple Services Limitations of DKIM People often assume that if SPF and DKIM are configured, “spoofing protection is foolproof.” However, DKIM also has vulnerabilities. Replay Attacks: DKIM cannot prevent “replay attacks,” in which a malicious third party intercepts an email with a valid DKIM signature and resends it to a different recipient. No Policy Control on Its Own: While DKIM verifies whether an email is “authentic,” it does not define a policy for how to handle emails that fail authentication. DMARC handles the response to authentication failures. DKIM is a mechanism for verifying “authenticity.” However, it cannot determine how to handle emails that fail authentication. That role is fulfilled by DMARC, which will be explained next. Back to Table of Contents What Is DMARC? (The Command Center That Makes the Final Decision) SPF and DKIM now allow us to verify the “sender” and “whether the message has been tampered with.” But what happens to an email if either verification fails? DMARC is responsible for making that final decision. The Role of DMARC DMARC (Domain-based Message Authentication, Reporting, and Conformance) acts as the command center that receives the “results” from SPF and DKIM and determines how to handle emails that fail authentication. DMARC has the following three roles: Final Determination: DMARC combines the authentication results from SPF and DKIM with alignment (discussed later) to make a comprehensive determination of the email’s authenticity. Policy Declaration: It specifies how the receiving server should handle emails when authentication fails. Receiving Reports: It allows you to receive aggregated reports showing who is sending emails from which domains. DMARC Policy: A DMARC record is a “rule for handling email” configured in DNS. It is displayed as follows: v=DMARC1; p=none; The “p” in the DMARC record stands for “policy” and specifies how to handle emails that fail authentication. Three Policy Levels DMARC allows you to set three policy levels. Policy Meaning Recommended Use none Monitoring only. Does not affect email processing. Initial investigation and monitoring phase quarantine Sorts emails that fail authentication into the spam folder. Intermediate stage reject Completely rejects emails that fail authentication. Full-scale operation Reasons for a Phased Implementation You should not set DMARC to “reject” right away. There are two reasons for this. First, if you set the policy to “reject” without fully understanding all legitimate email delivery paths, even legitimate emails sent from newsletter services, internal systems, and external applications will be rejected. Second, if you set the policy to “reject” while SPF and DKIM configurations are incomplete, a large number of legitimate emails may be rejected. Recommended Steps: Start monitoring with `p=none` (use DMARC reports to identify sending paths). Once SPF and DKIM are configured for all paths, transition to `p=quarantine`. If there are no issues, raise the setting to `p=reject`. An important concept called “alignment” is involved in DMARC evaluation. Next, let’s take a closer look at how it works. Return to Table of Contents What Is DMARC “Alignment”? So far, we’ve examined how SPF, DKIM, and DMARC work. However, there are instances where “authentication succeeds but DMARC fails.” The cause of this is alignment mismatch. Why Is Alignment Important? Alignment is a mechanism that verifies whether the domain used for authentication matches the sender (From) displayed on the screen. DMARC performs this check on both SPF and DKIM. SPF Alignment: SPF verifies the domain of the “envelope From” (the sender’s domain in the envelope). DMARC checks whether the domain that passed SPF authentication matches the domain in the displayed “From” header. DKIM Alignment: DKIM verifies the “d=domain” included in the signature. DMARC verifies that the DKIM signature is valid and that the “d=domain” matches the displayed “From” (header “From”) domain. The Difference Between “Relaxed” and “Strict” “Relaxed” and “Strict” are settings that determine the strictness of the alignment (domain match) check. They are specified within the DMARC record. “Relaxed” allows for subdomains, while “Strict” only permits exact matches. Unless there is a specific reason, using “Relaxed” is generally sufficient. DMARC is Valid If Either Passes: It is important to note that DMARC is considered a “PASS” (successful) if either the SPF alignment or the DKIM alignment passes. This means that even in cases where SPF authentication fails—such as when emails are relayed—DMARC still passes as long as DKIM alignment is successful. That is why it is crucial to “configure both SPF and DKIM.” Illustrated Explanation of How DMARC Works Return to Table of Contents Frequently Asked Questions Here, we address some frequently asked questions. Q. Why does it end up in the spam folder? A. If SPF or DKIM is not configured or is configured incorrectly, the recipient’s mail server will deem the sender “untrustworthy” and route the email to the spam folder. Gmail, in particular, takes a strict stance against emails without a DKIM signature. Q. Can “display name” spoofing be prevented? A. SPF, DKIM, and DMARC cannot prevent “display name” spoofing. For example, even if the actual sender is evil.com, as in “Taro Yamada attacker@evil.com,” the display name in the email client can be spoofed to appear as “Taro Yamada.” Implementing BIMI (Brand Indicators for Message Identification) is an effective measure against display name spoofing. Q. Why does SPF authentication fail when an email is forwarded? A. When an email is forwarded, the forwarding server becomes the new “sender IP address.” However, since the forwarding server’s IP address is not listed in the original sender’s SPF record, SPF authentication fails. To work around this, the “SRS (Sender Rewriting Scheme)” mechanism rewrites the envelope “From” field during forwarding to ensure SPF passes. DKIM is resistant to forwarding because the signature remains valid as long as the email body and headers are not altered during forwarding. Return to Table of Contents DNS Settings for learningBOX Users If you use learningBOX with the default settings, the domain of the sender’s email address will be ours (@learningbox.co.jp). In this case, SPF, DKIM, and DMARC are already configured, so no additional action is required. On the other hand, if you have set an email address from your own domain as the “From” address (for users who have changed the “From” email address using the customization option), you will need to configure your DNS settings. If these settings are insufficient, notification emails and other messages may be filtered into the spam folder. Here, we will first explain the SPF setup procedure. Overview of SPF Setup: learningBOX’s SPF settings must be configured through the management interface (DNS server) of the domain registrar with whom you have a contract, not through the learningBOX management interface. Your domain registrar is the company you used when you registered your domain. You can identify your domain registrar by checking the domain portion to the right of the “@” in your email address. Please note that learningBOX uses the “Amazon SES” mail server. Therefore, you must include “include:amazonses.com” in your SPF record. SPF Configuration Steps STEP 1: Request DNS Settings from Your Domain Registrar Log in to the control panel of your domain registrar and open the DNS settings page. DNS is the system used to manage and operate domain names. Please check your domain registrar’s support page for the specific request procedure. STEP 2: Configure the SPF record in the DNS settings screen. From your domain registrar’s control panel, configure the following TXT record: v=spf1 include:amazonses.com ~all *Note: Depending on your DNS service, the host field will be either blank or “@”. If an SPF record already exists for your domain, please add “include:amazonses.com” in the following format while retaining the existing settings: v=spf1 Existing settings: include:amazonses.com ~all Setup Instructions for Major Domain Registrars Setting Up with Onamae.com Configure DNS settings via the Onamae.com control panel. The setup procedure varies depending on the nameservers you use, so please refer to Onamae.com’s official support information for details. [Reference] Onamae.com, “Onamae.com Email Marketing Guide” Setting up with Xserver: Configure DNS settings via the Xserver server panel. [Reference] XServer, “SPF Settings” Return to Table of Contents Summary In this article, we explained the mechanism of “sender domain authentication,” which can cause emails to end up in the spam folder. SPF (Sender Policy Framework): A mechanism that declares the sender’s IP address via DNS to detect spoofed emails. While configuration is relatively simple, it has the limitation that it does not verify the “From” header, meaning emails may bypass authentication when forwarded. DKIM (DomainKeys Identified Mail): Uses digital signatures to verify the authenticity of emails and confirm they have not been tampered with. It is robust against forwarding and can also verify the “From” header domain. DMARC (Domain-based Message Authentication, Reporting, and Conformance): A mechanism that uses SPF and DKIM results to specify how to handle authentication failures (none/quarantine/reject) and receive reports. It is considered valid if either SPF or DKIM alignment is successful. These three work together as a set. Each one is insufficient on its own; only when combined do they form a robust sender domain authentication system. Start by “configuring SPF and DKIM” and “beginning DMARC monitoring with p=none.” Check out learningBOX’s feature list and pricing now! Download materials ▼ You might also like! Related articles

Thank you very much for your continued use of learningBOX. We will be updating our shared servers. This update will be performed without any downtime, so there will be no period during which the service will be unavailable. ■ Implementation Date: Wednesday, August 19, 2026 ■ To Customers Using “Customize”: In connection with this update, we would like to inform you of the following three points: 1. Changes to “Menu Management” Due to the Update 2. Changes to the API Specifications Due to the Update 3. Changes to the Kaonavi Integration Guide Due to the Update 1. Changes to “Menu Management” Due to the Update [Applies only to customers using the Site Customizer] As part of our ongoing feature development, the structure of the side menu and header menu in learningBOX may change. Customers using the Site Customizer will need to adjust the menu order and other settings on their end after the update. In Ver. 6.2, there are no changes to the structure of the side menu or header menu. Please visit this site to view the history of previous changes to the side menu and header menu. 2. Changes to the API Specifications Due to the Update [Applies Only to Customers Using API Integration] In learningBOX, API specifications may change as part of feature enhancements. We ask customers using API integration to review these changes in advance. Please share this information with your IT department and development staff. ・ API Specifications: Please stop referencing and storing legacy Excel data. 3. Changes to the Kaonavi Integration Guide Due to the Update [Applies only to customers using Kaonavi integration] learningBOX may modify the Kaonavi integration specifications as part of functional enhancements; we ask customers using Kaonavi integration to review these changes in advance. There are no changes to the Kaonavi Integration Guide in Ver. 6.2. We apologize for any inconvenience this may cause to our customers and appreciate your understanding.

Thank you very much for using learningBOX. Today, learningBOX has been updated to Version 6.1. We would like to introduce the various features that have been added or improved in this update. Enhanced Features: Smoother Configuration and Verification from the Content Management Screen With this update, you can now see at a glance whether “Content Assignments,” “Course Expiration Dates,” and “Publication Periods” have been set and how many entries exist in the Content Management screen. Additionally, the text color changes when a setting is present, making it visually easier to identify. Furthermore, text links next to the displayed counts now allow you to easily navigate to the Content Assignment management screen. *For details, please refer to “Content Management.” View Illustrated Guide (PDF): UI Improvements for Content Assignment Settings Clarify Scope of Impact With these UI improvements, checking a parent element now makes it visually clear which elements are affected. For content assignments, checking a parent folder automatically applies a “gray checkmark” to all directly subordinate content (immediate subfolders are excluded). On the other hand, for group assignments, selecting a parent group applies a check mark to all its child groups. In this way, affected and unaffected elements are clearly distinguished by color and other visual cues, helping to prevent unexpected configuration errors—such as “I thought I set it up, but it wasn’t assigned”—before they occur. *For details, please refer to “Bulk Settings (Content Assignment Management).” View illustrated guide (PDF) Email notifications for unread messages are now sent once a day! With this update, notifications for unread messages in all rooms have been changed to be sent once a day in a single batch. Even when numerous messages are exchanged across multiple rooms, you will no longer receive multiple notification emails, reducing the burden of checking your email. The new notification email includes the total number of unread messages across all rooms and the opening portion of the most recent message, allowing you to grasp the situation at a glance. *For details, please refer to “Unread Message Notifications.” View illustrated guide (PDF) Subtitle size for video lessons can now be adjusted in 7 levels With this update, you can now freely adjust the subtitle size directly in the video lesson player. You can choose from seven sizes ranging from 50% to a maximum of 400%. The size automatically adjusts relative to your screen width to ensure readability. Additionally, once set, the size is saved in your browser, so you can watch videos without having to reset it each time. *For details, please refer to “Display Settings on the Learning Screen (Video and Slide Settings).” View Illustrated Guide (PDF) Manage training reservations and attendance status all at once on a single overview screen! On the “Training Reservations and Attendance Management” screen, you can now view a list of registration statuses for all currently available training sessions on a single screen. Administrators can manage reservation and attendance statuses collectively via the “List” tab on this screen. Furthermore, a feature has been added that allows you to download reservation and attendance data for all training sessions in CSV format. *For details, please refer to “Training Reservation and Attendance Management.” View illustrated materials (PDF) List of New Features and Enhancements For detailed information on the new features and enhancements added in this update, including those mentioned above, please review the release notes below. ● Release Notes Announcement: Notice Regarding Certain Specification Changes In conjunction with this update, we have made changes to the specifications of certain features. ● Consolidation of Email Notification Frequency in the Messaging Feature Please review the details via the link below and take appropriate action as needed. ● [Advance Notice] Notice of Specification Changes Accompanying the Release of Ver. 6.1 Other For detailed operating instructions or if you have any questions, please contact us using the information below. ● Contact Form We will continue to do our utmost to provide products and services that satisfy our customers. We look forward to your continued support.

Thank you very much for your continued use of our services. In conjunction with the release of Version 6.1, scheduled for July 15, 2026, we will be making changes to the specifications of certain features. Accordingly, we would like to inform you of the main changes as follows. 〈Changes〉 Consolidation of Email Notification Frequency for the Messaging Feature ■ Affected Feature: Message Receipt Notifications ■Details of the Change: This change is intended to address the issue of receiving a large number of notification emails—such as when sending messages to large groups—and to optimize the convenience of email notifications. Comparison Before and After the Change Before the Change: A notification email was sent each time a message was sent. After the change: Notification emails, which were previously sent each time a message was received, will be consolidated into a single email per day. ・ The consolidated email will be sent once a day, around 12:00 p.m. (JST). ・ For each message, a notification will be sent only the first time (and only if there are unread messages).

Thank you very much for your continued use of learningBOX. We will be updating our shared server. Please note that the system will be unavailable during the period listed below. ■ Maintenance Period: Wednesday, July 15, 2026 1:00 a.m. – 5:00 a.m. *Please note that the end time may vary depending on the progress of the work. We appreciate your understanding. ■ To Customers Using “Customize”: In connection with this update, we would like to inform you of the following three points: 1. Changes to “Menu Management” Due to the Update 2. Changes to the API Specifications Due to the Update 3. Changes to the Kaonavi Integration Guide Due to the Update 1. Changes to “Menu Management” Due to the Update [Applies only to customers using the Site Customizer] In learningBOX, the structure of the side menu and header menu may change as a result of new feature development. Customers using the Site Customizer will need to adjust the menu order and other settings on their end after the update. Please refer to the following document for details on changes to the side menu and header menu. In Ver. 6.1, there are no changes to the structure of the side menu or header menu. For the history of previous changes to the side menu and header menu, please visit this site. 2. Changes to the API Specifications Due to the Update [Applies only to customers using API integration] learningBOX may change its API specifications as part of feature enhancements. We ask customers using API integration to review these changes in advance. Please share this information with your IT department and development staff. ・ API Specifications: Please stop referencing and storing legacy Excel data. 3. Changes to the Kaonavi Integration Guide Due to the Update [Applies only to customers using Kaonavi integration] learningBOX may modify the Kaonavi integration specifications as part of functional enhancements; we have already asked customers using Kaonavi integration to review these changes in advance. There are no changes to the Kaonavi Integration Guide in Ver. 6.1. We apologize for any inconvenience this may cause to our customers and appreciate your understanding.

Thank you very much for using learningBOX. Today, learningBOX has been updated to Version 6.0. We would like to introduce the various features that have been added or improved in this update. Enhanced Features: More Flexible Course Management with Per-Scene Permissions Previously, permissions were primarily granted at the course, folder, or group level. However, with this update, you can now grant “Content Management” “Grade Management,” and “Content Assignment” to specific scenes only. By granting scene-level permissions tailored to each company, administrators can reduce the effort required for course preparation and permission configuration. This minimizes the risk of configuration errors while allowing representatives from each company to quickly create and manage courses on their own. *For details, please refer to “Administrative Permissions.” View illustrated materials (PDF) Streamline Large-Scale Operations with Bulk CSV Configuration of Scene Permissions You can now configure the newly added scene-specific permission assignments in bulk using user CSV or group CSV files. In addition to configuring permissions individually on the screen, using CSV files allows you to easily add, remove, or overwrite existing permissions for multiple users or groups with a single upload. This helps prevent manual configuration oversights and errors, even when handling thousands of scenes or operating within large organizations with a vast number of learners. *For details, please refer to “Granting Permissions via CSV” and “Bulk Registration and Update of Groups.” View Illustrated Guide (PDF) Bulk Scene Configuration for Multiple Courses Now Possible! A new feature has been added that allows you to configure and modify “scenes” for multiple courses at once from the Content Management screen. Previously, you had to open the settings screen for each course individually, but now you can select multiple courses and assign scenes in bulk from a dedicated modal screen. A scene search function is also included, enabling smooth configuration even when multiple scenes are available. *For details, please refer to “Content Management.” View Illustrated Guide (PDF) The Group Record filtering feature has been further enhanced! Previously, it could be time-consuming to download all data and then process it manually, but now you can filter records directly on the screen based on “Account Creation Date,” “First Login Date,” and “Learning Rate” (e.g., 100%). These filter results are automatically reflected in Excel reports and CSV exports for individual courses or folders, as well as in the recipients of notification emails, eliminating the need for manual data processing. This makes it much easier to generate lists of “users who joined during a specific period and have completed their training” or to send bulk emails to those who have not yet completed their training. *For details, please refer to “Medical Records.” View Illustrated Guide (PDF) Batch Operations for Content Assignment, Course Expiration Dates, and Publication Periods Are Now Possible! Previously, you had to open individual screens for each course or folder to make settings. With this new feature, you can assign multiple courses or pieces of content to specific groups or users at once, and set course expiration dates and publication periods in a single operation. Additionally, since you can easily check the set completion deadlines and publication periods on the list screen, this helps prevent missed settings and errors. Furthermore, even if you want to set different periods for each learner, this significantly reduces the number of steps required. *For details, please refer to “Content Assignment Management.” View illustrated guide (PDF) Shortcut Creation Feature Added to Content List A new “Shortcut Creation” feature has been added to the Content List screen. This allows you to easily place existing videos, quizzes, and other content into other courses or folders as “shortcuts.” Since you can place multiple pieces of content together as a single shortcut, this reduces the effort required to manage them individually and allows for smoother management. Additionally, you can now preview content directly from the Content List screen, and the default setting now displays content sorted by registration date in “Newest First” order. *For details, please refer to “Content List (Across Courses and Folders).” View Illustrated Guide (PDF) “Sort by Oldest Due Date” Added to the Course List Panel on the Dashboard In the course list panel on the learner’s dashboard, “Sort by Oldest Due Date” has been added as a new sorting option. This makes it easier for learners to determine at a glance which courses they should prioritize, helping to prevent missed courses. Meanwhile, administrators can flexibly configure the panel to display only courses that meet specific criteria, such as “courses with a remaining number of days until the deadline within a specified range” or “courses that have passed their deadline.” In addition, the labeling of course deadlines has been improved, with phrases such as “○ days remaining” and “Expired” now displayed more clearly. This makes it easier for learners to reliably track their progress. *For details, please refer to “Dashboard.” View illustrated materials (PDF) Ability to filter by “Unfinished Only” on the “Select a Course” screen The usability of the “Select a Course” screen accessed by learners has been improved. A new sorting option, “By Oldest Expiration Date,” has been added to the search results, allowing learners to prioritize courses with upcoming expiration dates. Furthermore, a new toggle switch labeled “Incomplete Only” has been added next to the search bar. Simply turning this on allows learners to quickly filter and display only courses and content for which their completion rate has not reached 100% (e.g., in progress, not started, or failed). This enables learners to intuitively understand what they should study next and which tasks they have yet to complete. *For details, please refer to “Selecting a Course.” View illustrated materials (PDF) Adding enrollment expiration dates and other fields to report merge keys New merge keys will be added to the “Single Course/Folder Learning History” template in the Group Chart report generation feature. The three keys being added are “Login ID,” “Recommended Enrollment Date,” and “Enrollment Expiration Date.” Previously, when compiling annual training plans and performance data, staff had to manually cross-reference multiple data sets in Excel or similar software, which created a significant workload. With this update, you can easily export each participant’s course expiration date, actual learning progress, and login ID all at once to a single Excel file, significantly reducing the data processing required for performance aggregation and report generation. *For details, please refer to “Report Output.” View Illustrated Guide (PDF) Export Learning Histories for Multiple Courses in a Single Report! The report output feature in Group Records has been updated to be even more convenient. A new “Report Output” button has been added to the course list screen that appears after selecting a group, allowing you to export learning histories for multiple courses at once as an Excel report. A new template titled “Learning History for Multiple Courses” is now available, allowing you to extract data such as course expiration dates, start and completion dates, and login IDs all at once. Bulk export is possible as long as the total number of rows—calculated as “number of courses × number of users in the group”—does not exceed 5,000. *For details, please refer to “Report Output.” View Illustrated Guide (PDF) List of New Features/Functionality Improvements For detailed information on the new features and functionality improvements added in this release, including those mentioned above, please refer to the release notes below. ● Release Notes Announcement: Notice Regarding Certain Specification Changes In conjunction with this update, we have modified the specifications of certain features. ● Relaxation of access permissions for the “Content List” (across courses and folders) screen, and addition of a shortcut creation feature ● End of support for Mozilla Firefox Please review the details via the link below and take appropriate action as needed. ● [Advance Notice] Notice of Specification Changes Accompanying the Release of Ver. 6.0 Other For detailed instructions or if you have any questions, please contact us using the information below. ● Contact Form We will continue to do our utmost to provide products and services that satisfy our customers. We look forward to your continued support.

Thank you for using learningBOX. We will be updating the shared server. Please note that the system will be unavailable during the following period. The update will be implemented from 00:30 to 06:30 on June 17, 2026 (Wednesday). Please understand this in advance. Customers using "Customize" will be notified of the following three points in connection with the update. 1. 1. changes to "Menu Management" due to the update 2. changes to API specifications due to the update 3. changes to Kao Navi Linkage Guide due to the update 1. changes to "Menu Management" due to the update [For customers using the Site Customizer only] 2. changes to "Menu Management" due to the update [For customers using the Site Customizer only] 3. changes to "Menu Management" due to the update [For customers using the Site Customizer only The structure of the side menu/header menu may be changed in learningBOX due to the development of new functions. Customers using the Site Customizer will need to change the menu order, etc. after the update. Please refer to the following document for details on the changes to the side menu and header menu. Please refer to this site for the history of changes to the side menu and header menu. 2. 2. API specification changes due to updates [For customers using API integration only] The API specifications of learningBOX may be changed in accordance with functional improvements. Please share this information with your information system department and development staff. API Specification Starting with this version, the method of providing API information has been changed to URL distribution only. Please stop referring to and storing the existing Excel data. 3.3 Changes to Kao Navi Linkage Guide due to Update [For customers using Kao Navi Linkage only] The specifications for Kao Navi Linkage may change due to functional improvements in learningBOX, and customers using Kao Navi Linkage are asked to check in advance. There are no changes to the Kaonavi Linkage Guide in Ver. 6.0. We apologize for any inconvenience this may cause and ask for your understanding.

Thank you very much for your continued use of our service. The main changes are as follows. Change Point 1] Relaxation of access privileges on the content list (across courses and folders) screen and addition of shortcut creation functionality ■ Target Function Content Management Content List (across courses and folders) screen https://support.learningbox.online/how- to-use/content-list-across-course-folder/ ■Change DescriptionRelax access privileges to the content list (across courses and folders) screen and add the ability to create shortcuts within this screen. Comparison before and after change Item Before change After change Access to screen "Content Management Edit Authority (for all contents)" holders only "Content Management View Authority" and above are also allowed Shortcut creation is not allowed Even if you only have "View Authority" for the course/folder from which the content is created, if you have "Edit Authority" for the destination (storage destination), you can create shortcuts to the content. Even if you only have "viewing privileges" for the course/folder from which you are creating a shortcut, you can create a shortcut if you have "editing privileges" for the course/folder to which you are creating a shortcut (the destination folder). Request to Customers: With this easing of privileges, even users with "View" privileges will be able to create and use shortcuts to other courses for which they have "Edit" privileges. In order to prevent unintended placement and use of content, we ask that you please check and review whether the combination of viewing and editing privileges granted to each user or group is appropriate before updating. Change (2)] End of support for Mozilla Firefox ■Change DescriptionMozilla Firefox (hereafter referred to as "Firefox") is no longer a recommended browser and support for Firefox will be terminated. Handling after support ends: When using Firefox, there is a possibility that some functions may not work properly or display corruption or other problems may occur. Operation warranty and technical support for these issues will not be provided. Please switch to Google Chrome or Microsoft Edge. For the latest recommended environment, please check the following: https://learningbox.online/requirements/

Thank you for using learningBOX. Today, learningBOX has been updated to Ver. 5.2. We would like to introduce you to the various functions that have been added and improved with the update. Enhanced functions CSV import/export support! Easy management of large numbers of scenes Learners can now use the "Select Course" screen to filter and switch courses by pre-defined "scenes. In addition, "Scene Management," which was previously available in the "Basic Course Settings," is now available as an independent settings menu. This makes it easier to create, edit, and delete scenes from the list screen. In addition, a new function has been added to import scenes using CSV files and to output the current scene. Up to 5,000 scenes can be registered, allowing efficient management of many scenes. *For details, please refer to "Scene Management". If you have a customization contract before May 20, 2026, you can use the function by adding menu items in "Menu Management" of the Site Customizer. learningBOX 5.2 series side menu_header menu changes Illustration View Document (PDF) Stricter permissions for operation of detailed publication period settings! In the "Publication Period Settings," the operating privileges for "Advanced Settings," which are common settings for the entire environment, have been revised. Previously, some authority holders could change the settings, and unintended changes to the settings could cause sudden changes in the learner's screen display, leading to confusion. From now on, only the "administrator" and "authority holders who have the authority to assign content to all content and all groups" will be able to operate the system. This will allow for safer operation. *For details, please refer to "Setting the Scope of System Operation by Authority. View Illustrative Materials (PDF) AI generation and translation of video subtitles is now more intuitive! A step-by-step guide showing the process from AI subtitle generation to translation has been added to make subtitling from video audio data and translation into other languages more intuitive and easy to follow. Furthermore, by reviewing the size and placement of various buttons, the "Save Entire Video" button has been made more prominent, allowing the entire saving operation to be performed without leaving the translation screen open. *For details, please refer to "Creating Videos and Slides. View Illustrative Materials (PDF) Instant copy from the administration screen! New feature for faster acquisition of public URLs When content is set to "Public" on the content management screen, items such as "Copy URL for Public" and "Access URL for Public" will now appear in the existing "Content URL" field. Previously, it was not possible to retrieve or check the public URL directly from the "Content URL" field, which was a bit time-consuming. However, with this update, URLs for content set for public viewing can now be immediately retrieved and confirmed on the spot, making content sharing with external parties smoother than ever before. *For details, please refer to "Content URL". View Illustration (PDF) List of New Functions/Functional Changes For detailed information on the new functions/functional changes added this time, including the aforementioned functions, please refer to the following release notes. (This is for customers who have subscribed to the "Customize" paid option) The side menu and header menu have been changed in accordance with this update. Please check the contents from the link below and adjust as necessary. The side menu and header menu of learningBOX 5.2 series have been changed. Please check the following links for details and take necessary actions. Please refer to the following link for details and take necessary actions. We will do our best to continue to provide products and services that satisfy our customers. We appreciate your continued patronage and look forward to your continued support.