> For clean Markdown content of this page, append .md to this URL. For the complete documentation index, see https://buildwithfern.com/learn/llms.txt. # Member permissions > Manage Dashboard and CLI access for your organization. Control what each team member can do in Fern by configuring roles in the [Fern Dashboard](https://dashboard.buildwithfern.com/members). #### Enterprise feature Every plan lets you add members up to its [member limit](#team-members-by-plan). Assigning Editor or Viewer roles requires the [Enterprise plan](https://buildwithfern.com/pricing). To get started, reach out to [support@buildwithfern.com](mailto:support@buildwithfern.com). ## Add a member Only [Admins](#admin) can add members. Your [plan](#team-members-by-plan) determines how many members you can add. #### Open the Members page Navigate to the [Fern Dashboard](https://dashboard.buildwithfern.com/members) and select **Members** from the sidebar. #### 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](#role-types) and configure [CLI access](#editor) 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](#role-types), and configure [CLI access](#editor) 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](https://dashboard.buildwithfern.com/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](/learn/docs/writing-content/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 | Permission | Admin | Editor | Viewer | | -------------------------------------------------------------------------------------- | ----- | -------------------- | ------ | | Manage organization settings | Yes | No | No | | Manage members | Yes | No | No | | Add or update a custom domain | Yes | No | No | | Manage password protection | Yes | No | No | | Manage [API keys](/learn/dashboard/configuration/api-keys) (Dashboard or `fern token`) | Yes | No | No | | Set [Ask Fern query log retention](/learn/docs/ai-features/ask-fern/overview#features) | Yes | No | No | | Delete production docs sites | Yes | No | No | | View dashboard and analytics | Yes | Yes | Yes | | Publish to production | Yes | Configure per Editor | No | | Deploy previews | Yes | Yes | Yes | | Delete preview docs sites | Yes | Yes | Yes | | Generate locally | Yes | Yes | Yes | | Use Fern Editor | Yes | Yes | No | ## Team members by plan Your [plan](https://buildwithfern.com/pricing) determines how many members you can add to your organization: | Plan | Team members | | ------------ | ------------ | | Free | 10 | | Postman Free | 25 | | Enterprise | Custom | > Manage Dashboard and CLI access for your organization.