Skip to content

docs: add coverage for customer FAQ topics#4340

Merged
devalog merged 4 commits into
mainfrom
devin/1773803039-doc-coverage-customer-qa
Mar 18, 2026
Merged

docs: add coverage for customer FAQ topics#4340
devalog merged 4 commits into
mainfrom
devin/1773803039-doc-coverage-customer-qa

Conversation

@devin-ai-integration

Copy link
Copy Markdown
Contributor

Summary

Adds documentation coverage for five frequently asked customer questions identified from support conversations. Changes span five files across four topic areas:

  1. Self-service setup — repo ownership (self-service-setup.mdx): Clarifies that after the self-service setup flow, users have full ownership of the Git repo and can publish changes by pushing to main.

  2. OpenAPI sync — plan availability & spec storage (automation.mdx): Notes that the sync-openapi action and fern api update are available on all plans. Adds a new "Where to store your OpenAPI spec" section describing the three common approaches (sync from source repo, host at public URL, commit directly).

  3. Postman integration (postman.mdx, overview.mdx): Replaces the deprecated-only page with a new section documenting the Postman publish-to-Fern integration (available on all plans), including Postman free-tier and Fern org limits. Retains the deprecated Fern-to-Postman generator info below. Removes "(deprecated)" label from the integrations overview card.

  4. RBAC role limits (rbac.mdx): Adds a sentence clarifying there is no limit on the number of roles.

Review & Testing Checklist for Human

  • Postman integration accuracy: The Postman-to-Fern publish flow details (all plans, 5 sites per org, 1 custom domain on free tier, Team plan for more) come from internal Slack — verify these limits are still accurate and that the feature name/description matches the actual product.
  • Postman page completeness: The new Postman section describes what the integration does but doesn't include setup instructions or a link to the Postman-side flow. Decide if a link or steps should be added.
  • Link verification: Confirm the internal links in the new automation.mdx section resolve correctly: #setup, /cli-api-reference/cli-reference/commands#fern-api-update, /learn/sdks/reference/generators-yml#openapi.
  • Preview the changed pages on the deploy preview to verify rendering, especially the Note callout on the Postman page and the bullet list on the automation page.

Notes

  • Pre-existing Vale warnings on automation.mdx (lines 3, 8 — "latest") and rbac.mdx (line 65 — heading casing) were not introduced by this PR and were left as-is.
  • The SSO + RBAC distinction (SSO does not support RBAC) was already documented in sso.mdx and did not require changes.

Link to Devin session: https://app.devin.ai/sessions/91608547945b460c83f817b12c377b2c

- Clarify Git repo ownership after self-service setup
- Add plan availability and spec storage guidance to OpenAPI sync page
- Update Postman integration page with publish-to-Fern flow
- Document no limit on RBAC roles

Co-Authored-By: bot_apk <apk@cognition.ai>
@devin-ai-integration devin-ai-integration Bot requested a review from devalog as a code owner March 18, 2026 03:06
@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@fern-api

fern-api Bot commented Mar 18, 2026

Copy link
Copy Markdown
Contributor

Requested by: kapil
Slack thread: View conversation

<Markdown src="/snippets/agent-directive.mdx"/>

Automatically pull your latest OpenAPI spec from a publicly available URL into your fern folder using the [sync-openapi GitHub Action](https://github.com/fern-api/sync-openapi). This keeps your committed spec in sync with your live API without manual updates.
Automatically pull your latest OpenAPI spec from a publicly available URL into your fern folder using the [sync-openapi GitHub Action](https://github.com/fern-api/sync-openapi). This keeps your committed spec in sync with your live API without manual updates. The sync-openapi action and the `fern api update` CLI command are available on all [plans](https://buildwithfern.com/pricing).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[FernStyles.Current] Avoid time-relative terms like 'latest' that become outdated

@github-actions

github-actions Bot commented Mar 18, 2026

Copy link
Copy Markdown
Contributor

Fern's Postman integration is no longer actively maintained. To get your API endpoints into Postman, import your OpenAPI specification directly. See [Postman's OpenAPI import docs](https://learning.postman.com/docs/integrations/available-integrations/working-with-openAPI/) for instructions.
## Publish Postman collections to Fern

You can generate a Fern Docs site directly from your Postman collection. Fern automatically creates an API reference from your collection with request details, sample code, and an interactive API explorer. You can also add guides, tutorials, and other content alongside the reference, and customize branding such as your domain, logo, and colors.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[FernStyles.Reject] Use 'API Reference' instead of 'API reference'.

Fern's Postman integration is no longer actively maintained. To get your API endpoints into Postman, import your OpenAPI specification directly. See [Postman's OpenAPI import docs](https://learning.postman.com/docs/integrations/available-integrations/working-with-openAPI/) for instructions.
## Publish Postman collections to Fern

You can generate a Fern Docs site directly from your Postman collection. Fern automatically creates an API reference from your collection with request details, sample code, and an interactive API explorer. You can also add guides, tutorials, and other content alongside the reference, and customize branding such as your domain, logo, and colors.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[FernStyles.Reject] Use 'API Explorer' instead of 'API explorer'.

Fern's Postman integration is no longer actively maintained. To get your API endpoints into Postman, import your OpenAPI specification directly. See [Postman's OpenAPI import docs](https://learning.postman.com/docs/integrations/available-integrations/working-with-openAPI/) for instructions.
## Publish Postman collections to Fern

You can generate a Fern Docs site directly from your Postman collection. Fern automatically creates an API reference from your collection with request details, sample code, and an interactive API Explorer. You can also add guides, tutorials, and other content alongside the reference, and customize branding such as your domain, logo, and colors.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[FernStyles.Reject] Use 'API Reference' instead of 'API reference'.

@devalog devalog merged commit 6c86a82 into main Mar 18, 2026
2 checks passed
@devalog devalog deleted the devin/1773803039-doc-coverage-customer-qa branch March 18, 2026 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant