# Feature request: Different levels for Maven Central tokens (deploy and publish)

**URL:** <https://community.sonatype.com/t/feature-request-different-levels-for-maven-central-tokens-deploy-and-publish/16472>\
**Category:** Central Repository\
**Created:** [July 16, 2026, 7:07pm UTC](https://community.sonatype.com/t/feature-request-different-levels-for-maven-central-tokens-deploy-and-publish/16472 "2026-07-16T19:07:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ivangsa](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/ivangsa/32/4206_2.png) [@ivangsa](https://community.sonatype.com/u/ivangsa)\
**Post date:** [July 16, 2026, 7:07pm UTC](https://community.sonatype.com/t/feature-request-different-levels-for-maven-central-tokens-deploy-and-publish/16472/1 "2026-07-16T19:07:24Z")

</div>

Hi,

I keep tokens in GitHub secrets to publish to Maven Central. **I am worried because these tokens can do everything.** I recently have seen a supply chain take over just because of bad configured GH pipelines that stealed GH secrets.

Right now one token can publish directly. Once something is published, we cannot delete it.

It would be good to have two types of tokens:

- One for deploy (only upload to staging)

- One for publish (to make it public)

This way even if a CI token is stolen, it cannot publish directly.

Is this something you can add?

Thanks!