Hi GrantL01,
Out of the Box there is no explicit "Scope" object where this is defined. But you may want to explore how 'Requirements' and 'Release' function in the tool (should you be following this methodology).
There are some limits here though in that while you are able to define costs for requirements and then subsequently releases that are inclusive of the requirements, you can't build financial plans off the back of the numbers that you have assigned to the 'Releases' / 'Requirements'. This is the foundation for Product Based Planning methodologies such as PRINCE2.
In addition, you can't associate OOTB any 'Change Requests', 'Risks', or 'Issues' to either 'Releases' or 'Requirements'.
For me this is a bit of a gap in Clarity PPM (there are not many), as it greatly impedes being able to support the management of scope and subsequently quality (based on the definition of quality as did I get what I asked for to the correct specification).
On a related note, 'Change Requests' in Clarity PPM are basically a form - that is it. It is fairly basic, which is reflective of the fact that there is no consistency either in the project management methodologies / frameworks or in practice in how CRs are managed (either from a process point of view or what data is required).