A role can own objects, receive privileges and belong to other roles. LOGIN allows authentication; a NOLOGIN role is useful for grouping permissions. Grant only the operations a service needs. A reporting service rarely needs schema ownership or the ability to create arbitrary functions.
Schema USAGE allows a role to resolve objects inside that schema, while table SELECT allows it to read rows. They are separate permissions. Existing tables and future tables also need separate consideration: default privileges apply to objects a specified owner creates later.
Ownership is stronger than an ordinary grant. Test with a nonowner role rather than the setup superuser, or a privilege check can report a misleading success. These exercises create local roles inside the disposable database. They don't configure production login credentials, network authentication or secret storage.
A permission-group role should not gain login or superuser powers.