Required permission for organizational secrets

I have standard Member role in an organization but would need access to the Secrets on the Organization Level. Obviously promoting me to Owner role would solve the problem but that’s not desired. What kind of permission would I need to get, to manage Secrets only? (Atm I don’t even see the Settings tab of the Organization)

@BernhardFuchs
You must authenticate using an access token with the admin:org scope to manage secret via API, similarly organization owner role for access via user interface.
This no delegation of secrets management to one, some or all organization secrets that I am aware.

You can restrict what repositoriea can access an organization secret.

The motivation is, that I’m responsible for CI/CD on a couple of Repos and have to duplicate Secrets atm.
What I’m looking for is a custom role, where I can manage Secrets on Org level but don’t see e.g. Billing information. Preferably done within the UI but that is not a hard requirement.

This no delegation of secrets management to one, some or all organization secrets that I am aware.

Does that mean there are no such custom roles on Github?

Maybe it is possible to create Teams with certain permissions, like a CI Team that can manage Organization Secrets?

@BernhardFuchs I have not read og and am not aware of any such features, if there are such things hopefully someone else will shout it here, but I think very unlikely