Skip to content

Conversation

@devin-ai-integration
Copy link
Contributor

Summary

Updates the member permissions documentation page to reflect the current state of the user permissions feature, which is now live. Key changes:

  • Removed the "Coming soon" info box since the feature is now available
  • Added note that all users have Admin permissions by default unless a different role is assigned
  • Added information about preview deploy permissions for Admin and Editor roles
  • Added new "Publish preview deploys" row to the permissions table
  • Replaced emoji checkmarks with "Yes"/"No" text in the permissions table
  • Added new section on resource-level permissions explaining that users can be assigned access to specific docs sites

Review & Testing Checklist for Human

  • Verify preview deploy permissions accuracy: The Slack thread mentioned "In the future want to restrain viewers from being able to do this" for preview deploys, which implies Viewers CAN currently publish preview deploys. I interpreted this as Viewers cannot publish preview deploys - please verify this is correct with the product team.
  • Verify default Admin permissions: Confirm that "all users have Admin permissions by default unless a different role has been assigned" accurately describes the current behavior.
  • Verify resource-level permissions description: Confirm the description of docs site-level permissions is accurate and complete.

Notes

Based on information from this Slack thread shared by Alec about the user permissions feature rollout.

Link to Devin run: https://app.devin.ai/sessions/84fbc8deb9e5480ab597cb594ad17ba6
Requested by: Fern Support (info@buildwithfern.com)

Co-Authored-By: Fern Support <info@buildwithfern.com>
@devin-ai-integration
Copy link
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

@github-actions
Copy link
Contributor

Assignee Required

This PR was opened by Devin AI but the requester's email (info@buildwithfern.com) is not in the username mapping. Please add an assignee manually.

@github-actions
Copy link
Contributor

## Role types

Member roles control what actions someone can take in your organization, such as managing settings, viewing analytics, and publishing to production. [**CLI access**](/learn/cli-api-reference/cli-reference/overview) determines who can publish SDKs and documentation sites to production (local development doesn't require it).
When a user logs in via the Dashboard or CLI, they are assigned an Admin, Editor, or Viewer role. By default, all users have Admin permissions unless a different role has been assigned.
Copy link
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 🐶
[Microsoft.Contractions] Use 'they're' instead of 'they are'.

@github-actions
Copy link
Contributor

@github-actions
Copy link
Contributor

@github-actions
Copy link
Contributor

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.

3 participants