**
Yes, this is expected behavior. Apsona uses a Base Package + Add-on Packages architecture, which is why you may notice objects that have the same label but different API names or namespace prefixes.
The difference comes from the namespace in the API name:
Objects with the apsona__ prefix belong to the Apsona for Salesforce base package. These provide the core framework required for all Apsona features.
Objects with prefixes such as apsona_grid__, apsona_msr__, or apsona_sched__ belong to specific add-on packages, such as:
Grids
Multi-Step Reporting
Scheduler
Both sets of objects appear together because:
The base package supplies the foundational structures.
Each add-on package installs its own objects to enable its specific functionality.
These objects are designed to coexist and work together, not replace each other.
Important points to consider:
From a permissions and setup perspective, users should have access to the objects related to the add-on features they actively use (for example, apsona_grid__ for Grids or apsona_msr__ for Multi-Step Reports).
Base package objects (apsona__) are used internally by Apsona and should generally remain enabled rather than being restricted or removed.
This architecture ensures modular functionality while keeping the core system stable and extensible.
**