GitBook user roles

Roles are how you define the level of access and control that members have over content (and the organization, in the case of admins). By default an ABB users will receive the Creator role. Creators are essentially content-level admins. They have all the same permissions as a reviewer, however they can also create and delete spaces, collections and sites, merge change requests and manage permissions at a content level.

Next to giving the new users the Creator role, a Gitbook admin will also add the newly created GitBook user to one or more team. By default the users gets added to the Digiteam ABB.

People who leave ABB will not have their user deleted but the role will be narrowed down to the lowest level role: Guest. 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.

The following embedded link provides an overview of all of the other user roles currently supported by GitBook

Roles | GitBook Documentationgitbook.com