Document Admin role requirement for generating Fern API keys - #6934
Merged
nerminamiller-postman merged 1 commit intoSep 14, 2026
Merged
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
devin-ai-integration
Bot
requested review from
devalog,
jkonrath-postman and
nerminamiller-postman
as code owners
September 11, 2026 19:59
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Contributor
|
🌿 Preview your docs: https://fern-preview-devin-1789156737-api-key-admin-permissions.docs.buildwithfern.com/learn Here are the markdown pages you've updated: |
nerminamiller-postman
approved these changes
Sep 14, 2026
nerminamiller-postman
deleted the
devin/1789156737-api-key-admin-permissions
branch
September 14, 2026 14:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A user hit
Failed to create token because you do not have the required permissions in the <org> organizationfromfern tokenand neither the CLI reference nor the Ask Fern API overview said what permission was needed.Venus gates
generateRegistryTokens(whatfern tokencalls) andrevokeTokenon the org Admin role (resolve(["admin"], VenusAction.REGISTRY_GENERATE_TOKENS)inregistry_service.py); the Fern APIs themselves only need a valid key. The Dashboard API keys page already said Admins-only, but the two entry points people actually reach from the error didn't.snippets/fern-token.mdx(rendered in the CLI reference + everywherefern tokenis documented): states the Admin requirement and the exact error non-Admins see.ask-fern/api-get-started.mdxAuthentication: Admins generate keys; Editors/Viewers ask an Admin; using a key needs no extra role.dashboard/permissions.mdxtable: "Manage API keys" now notes it covers both the Dashboard andfern token.Not addressed here: the user's request for non-admin API key management (a product change, not docs).
Link to Devin session: https://app.devin.ai/sessions/bcdb7901fa6342979b4b558dde1f6554
Open in Devin Desktop: https://app.devin.ai/desktop/session/bcdb7901fa6342979b4b558dde1f6554?variant=devin