Member permissions
Control what each team member can do in Fern by configuring roles in the Fern Dashboard.
Add a member
Only Admins can add members. Your plan determines how many members you can add.
Add a new member
Select Add member, then choose one of the following to invite a member to your organization:
- One-time link: Assign a role and configure CLI access for Editors. Then, select Generate invite link to create a one-time-use link you can share with anyone.
- Email: Enter an email address, assign a role, and configure CLI access for Editors. Then, select Send invitation.
The invitee receives an email with a link to join your organization in Fern.
To change a member’s role or remove a member, go to the Members page and select the options menu next to the member’s name.
Role types
Each team member has an Admin, Editor, or Viewer role. By default, all members have Admin permissions unless you assign a different role.
Roles control two types of permissions:
- Dashboard permissions: managing organization settings and members, adding or updating custom domains, viewing analytics, and using Fern Editor.
- CLI permissions: publishing SDKs and documentation to production. Local development and deploying previews don’t require CLI access.
Admin
Admins have full access to both the Dashboard and CLI, including editing organization settings, managing members, using Fern Editor, and publishing to production.
Editor
Editors can view analytics and use Fern Editor. Editors can’t manage organization settings or members. CLI access is configurable per Editor:
- Editors with CLI access can publish SDKs and documentation sites to production.
- Editors without CLI access can’t publish to production.
- All Editors can deploy previews via the CLI.
Viewer
Viewers have read-only access to the Dashboard (settings, analytics) and can deploy previews via the CLI. Viewers don’t have access to Fern Editor.
Permissions by role
Team members by plan
Your plan determines how many members you can add to your organization:
