# Running into basic access problem with new key created

**URL:** <https://forum.langchain.com/t/running-into-basic-access-problem-with-new-key-created/185>\
**Category:** Observability & Evals\
**Created:** [July 2, 2025, 1:13am UTC](https://forum.langchain.com/t/running-into-basic-access-problem-with-new-key-created/185 "2025-07-02T01:13:32Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![eric-burel](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.langchain.com/eric-burel/32/712_2.png) [@eric-burel](https://forum.langchain.com/u/eric-burel)\
**Post date:** [December 15, 2025, 1:32pm UTC](https://forum.langchain.com/t/running-into-basic-access-problem-with-new-key-created/185/3 "2025-12-15T13:32:06Z")

</div>

Hi @nhuang , my LangChain training participants sometimes hit this issue on newly created accounts and keys (personal key on the default workspace). Is there some security safeguard that kicks in somehow? I don’t hit this issue on my “older” key.

Related: [Langchain\_auth Client always return 403 even with valid Langsmith API key](https://forum.langchain.com/t/langchain-auth-client-always-return-403-even-with-valid-langsmith-api-key/1853)

Indirectly related (case of a service key) : [LangSmith API Error: 403 Forbidden - org\_scoped\_key\_requires\_workspace](https://forum.langchain.com/t/langsmith-api-error-403-forbidden-org-scoped-key-requires-workspace/1476)

---

_[View the full topic](https://forum.langchain.com/t/running-into-basic-access-problem-with-new-key-created/185)._