---
title: "Release 10.0.46.51 (January 2026) - Security and Compliance Studio"
slug: "release-1004651-january-2026-scs"
description: "Explore Release 10.0.46.51 (January 2026) of Security and Compliance Studio, including improvements to the Security Request Execution Log and bug fixes."
tags: ["Release notes", "Security and Compliance Studio", "SCS"]
updated: 2026-07-10T10:20:36Z
published: 2026-07-10T10:21:01Z
canonical: "docs.staedean.com/release-1004651-january-2026-scs"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Release 10.0.46.51 (January 2026)

Find information on Release 10.0.46.51 (January 2026) of Security and Compliance Studio for Microsoft Dynamics 365 Finance & Supply Chain Management.

## What’s new

New or changed features in Release 10.0.46.51 (January 2026) – Security and Compliance Studio.

### 1. Security Request Execution Log

**Overview:** Adds visibility into security requests that are executed asynchronously via batch jobs. A new **Security Request Execution Log** button is available on the **Security Request** page.

#### 1.1 What’s included

- Navigation from *Security Request* → *Security Request Execution Log* page.
- Execution log page is organized into:
  - **General**: Request ID, Request Name, Request Type
  - **Started**: Batch jobs that initiated the request activity (for example, enabling a user from the “From date”)
  - **Ended**: Batch jobs that completed end-date actions (for example, revoke access on the “To date”)

#### 1.2 Value

- Improves transparency for batch-driven request processing.
- Enables monitoring of progress and completion status.
- Increases confidence when managing scheduled or delayed security actions.

See also:

- [Monitor security request execution](/data-management/docs/monitor-security-request-execution)
- [Manage security requests](/data-management/docs/manage-security-requests)

### 2. Manage Access on Roles to Multiple Organizations

**Overview:** Streamlines organization assignment for roles across multiple organizations via a guided flow from **System administrator → Users** page (Roles accordion).

#### 2.1 What’s changed / improved

- Displays roles currently assigned to the selected user in a grid.
- Admin must **select one or more roles** and move them to **Selected Roles**.
- **Assign Organization** becomes enabled only after at least one role is selected.
- Allows assigning **multiple selected roles** to the chosen organizations in one action.

#### 2.2 Fix to prior behavior

- Previously, **Assign Organization** was enabled by default and could be used without selecting roles.

See also: [Give user roles access to organizations](/data-management/docs/give-user-roles-access-to-organizations)

### 3. Form Access–Based Email Notifications

**Overview:** Introduces configurable email alerts when users/roles access specific application forms. A new setup option **Form Access Setup Notification** is added under **Security & Compliance Studio → Setup → Email Notification Setup**.

#### 3.1 Configuration capabilities

- Create/delete notification rules in a grid-based setup.
- Select **Form Name** to monitor.
- Choose **Access Type**:
  - **Role-based**, or
  - **User-based**
- Enable/disable notifications.
- Optionally **CC the accessing user**.
- Choose an **Email Notification Template** (from standard templates in System Administrator).
- Provide **Justification** for the setup.

#### 3.2 Targeting & recipients

- **Role-based:** Select roles using an available/selected roles dual-grid.
- **User-based:** Select users using an available/selected users dual-grid.
- **Recipients:** Configure recipients using an available/selected recipients dual-grid.

#### 3.3 When emails trigger

- If an active rule exists for a form,
- and the accessing user (or their role) matches the rule,
- SCS sends the email to configured recipients (and CCs the user if enabled).

See also: [Set up email notification for form access](/data-management/docs/set-up-email-notification-for-form-access)

### 4. Common Library Version 63 (TCL v63) and License Retrieval Requirement

**Overview:** This release includes **Common Library v63**, which introduces a new cloud-hosted code-signing certificate.

> [!NOTE]
> Important
> 
> After updating (because pipelines include TCL v63), customers must retrieve the **STAEDEAN product license** again — otherwise STAEDEAN products may disappear.

#### 4.1Required steps

1. Enable **maintenance mode** on the target environment.
2. Use **Retrieve Available Licenses** in the **STAEDEAN Solution Management** workspace.

See also: [STAEDEAN Common library](/pages/staedean-common-library)

## Bug fixes

Bug fixes in Release 10.0.46.51 (January 2026) – Security and Compliance Studio.

| Bug ID | Title | Description / Observation |
| --- | --- | --- |
| 230478 (CS00236623) | Error while generating report | For some customers with report-related customizations, the application prompted an error while generating reports. **Fix:** Users can now generate the report without issues. |
| 232096 (CS00238573) | DSM Queries often executed impacting performance | DSM queries were executed frequently, impacting performance in scenarios where no Security Compliance configuration was present. **Fix:** Application performance is no longer impacted when there is no Security Compliance configuration. |