Join the conversation

Join the community of Machine Learners and AI enthusiasts.

Sign Up
NeoCodes-dev 
posted an update 1 day ago
Post
173
Hi all,

I am working on a project for the Pytorch/HF OpenEnv challenge, and part of the challenge is that a participant/team needs to write a blog post (an Article) on HuggingFace about their submission. However, when I try to create an Article, it says I need a "pro" account.. but I already am a HF Pro member and have been for almost a year!

Is anyone else having this issue? I have a bunch of ideas for blog posts/articles so I'd really like to be able to access this feature, even outside of the OpenEnv Challenge. Can someone let me know if there's a way to fix this or something I'm missing?

Thanks,
Neo

Oh, i see...


Why this happens

  • Personal “Articles / Community Blog” is a HF PRO feature, but access is also commonly gated via the blog-explorers org, so the UI may still say “need PRO” even when you’re subscribed. (Hugging Face)
  • Organization-published Articles are not covered by personal PRO; they require an org on Team/Enterprise and the right org permissions. (Hugging Face)

What to do (short, step-by-step)

  1. Confirm you’re logged into the correct HF account and that PRO is active

    • PRO includes “Articles: write and publish blog articles on your HF profile.” (Hugging Face)
  2. Request access to the Community Blog editor gate

    • Go to blog-explorers and click “Request to join this org”. This is the documented unlock path. (Hugging Face)
  3. Create the article from the official editor URL

    • Use https://huggingface.co/new-blog to start writing once your access is enabled. (Hugging Face)
  4. If you’re trying to publish under a team/org name (not your personal profile)

    • Make sure the organization is on Team/Enterprise, and your org role is write or admin. (Hugging Face)
  5. If it still says “need PRO” after #2–#3 (likely an entitlement/account sync issue)

That’s the shortest reliable path: (1) correct account + active PRO → (2) join blog-explorers → (3) use /new-blog → (4) handle org vs personal publishing → (5) billing support if still blocked.