Best Practice for making role changes in Cloud HCM

Summary:

Hi,

We are currently using copies of seeded roles which inherit Oracle functionality.

There are items that I am looking to remove from managers access such as the explore tab and create journey option.

I have viewed older posts which mention 'The explore tab is successfully removed by creating a custom duty role, removing the explore privilege and assigning the custom duty role to line manger abstract role'.

I wanted to check if this is best practice for making role changes going forward, what level of regression testing is required when such changes are made and what is the overall impact of these role changes (e.g will roles continue to inherit oracle seeded?).