When adding members to your organization, you can give them a default role. This role will apply to any content that inherits its permissions from the organization.
Understanding default roles is key to getting the most out of how GitBook handles permission management. Check out our documentation on permissions and inheritance for a full overview of how permissions cascade throughout content in GitBook.
Roles are how you define the level of access and control that members have over content (and the organization, in the case of admins).
Each role gets progressively higher levels of access as you move up the list. Let's start at the bottom:
The guest role is a very specific role in GitBook. Guests are members that have no default organization role. A guest acts as a standard user in every other regard, they just need to have their permissions set explicitly at a content level.
Inviting a guest to the organization means that they'll only ever see content they've been directly added to. This is great if you want to add external stakeholders or contractors to your organization, but don't want to worry about giving them access to any content by default.
Please note that guest members, as with all other members, count towards the total number of members in an organization for billing purposes.
Editors are able to read and comment, just like a commenter, but they're also able to edit content in a couple of ways. Firstly, for spaces that are open for live edits, editors can edit the content directly. Secondly, for spaces that have live edits locked, editors can create and submit change requests. Editors cannot merge change requests.