A role combines permissions with a subsidiary scope. Report access is different from journal-entry access, and access to US doesn't imply access to EU. Give a task the permissions it needs without treating a broader grant as an equivalent result.
The local role editor provides a disclosed permission list and explicit subsidiary IDs. Its context switch lets you practice as a chosen role; it isn't authentication or proof that a real user was assigned that role. Authorized configuration and identity administration belong in a production account. Test the requested work under the intended role and scope. A successful US report doesn't prove that journal posting or group consolidation is available. Approval also needs its own permission, assigned workflow role and amount limit, so the role name alone is insufficient evidence.