# Scoped access specifier

**URL:** <https://forums.unrealengine.com/t/scoped-access-specifier/2673922>\
**Category:** Verse\
**Tags:** unreal-editor-for-fortnite, fortnite-creative, question, fortnite\
**Created:** [November 11, 2025, 7:44pm UTC](https://forums.unrealengine.com/t/scoped-access-specifier/2673922 "2025-11-11T19:44:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![OVTSIDERZ](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/ovtsiderz/32/1168800_2.png) [@OVTSIDERZ](https://forums.unrealengine.com/u/OVTSIDERZ)\
**Post date:** [November 11, 2025, 7:44pm UTC](https://forums.unrealengine.com/t/scoped-access-specifier/2673922/1 "2025-11-11T19:44:22Z")

</div>

![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/7/4/b/74b3a5c8194b59091bf5876e612edf7300332fb2.png)

Is it intended that making **ModuleA** scoped to **ModuleB** allows **ModuleB** to access everything marked `<internal>` in **ModuleA?**  
Shouldn’t only `<public>` members of **ModuleA** be accessible instead?

In the provided image, everything marked `<internal>` inside **Data** and **Inventory** modules behaves as if it was `<public>` to **Persistence** module. This effect propagates to classes and their `<internal>` members as well.

---

<div class="post-metadata">

**Author:** ![AndrewScheidecker](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/andrewscheidecker/32/926976_2.png) [@AndrewScheidecker](https://forums.unrealengine.com/u/AndrewScheidecker)\
**Post date:** [November 13, 2025, 1:25pm UTC](https://forums.unrealengine.com/t/scoped-access-specifier/2673922/2 "2025-11-13T13:25:38Z")

</div>

No, that’s not intended. Thanks for the report.
