The State of Docs Report 2025 is live! Dive in and see why docs matter more than ever:
Read the report
LogoLogo
ProductPricingLog inSign up
  • Documentation
  • Developers
  • Guides
  • Changelog
  • Help Center
  • Getting Started
    • GitBook Documentation
    • Quickstart
    • Importing content
    • GitHub & GitLab Sync
      • Enabling GitHub Sync
      • Enabling GitLab Sync
      • Content configuration
      • GitHub pull request preview
      • Commit messages & Autolink
      • Monorepos
      • Troubleshooting
  • Creating Content
    • Formatting your content
      • Inline content
      • Markdown
    • Content structure
      • Spaces
      • Pages
      • Collections
    • Blocks
      • Paragraphs
      • Headings
      • Unordered lists
      • Ordered lists
      • Task lists
      • Hints
      • Quotes
      • Code blocks
      • Files
      • Images
      • Embedded URLs
      • Tables
      • Cards
      • Tabs
      • Expandable
      • Stepper
      • Drawings
      • Math & TeX
      • Page links
    • Reusable content
    • Broken links
    • Searching content
      • Search & Quick find
      • GitBook AI
    • Writing with GitBook AI
    • Version control
  • API References
    • OpenAPI
      • Add an OpenAPI specification
      • Insert API reference in your docs
    • Guides
      • Structuring your API reference
      • Adding custom code samples
      • Managing API operations
      • Describing enums
      • Integrating with CI/CD
  • Extensions reference
  • Publishing Documentation
    • Publish a docs site
      • Public publishing
      • Private publishing with share links
    • Site structure
      • Content variants
      • Site sections
    • Site customization
      • Icons, colors, and themes
      • Layout and structure
      • Extra configuration
    • Set a custom domain
    • Setting a custom subdirectory
      • Configuring a subdirectory with Cloudflare
      • Configuring a subdirectory with Vercel
    • Site settings
    • Site insights
    • Site redirects
    • Visitor authentication
      • Enabling visitor authentication
      • Setting up Auth0
      • Setting up Azure AD
      • Setting up AWS Cognito
      • Setting up Okta
      • Setting up OIDC
      • Setting up a custom backend
  • LLM-ready docs
  • Collaboration
    • Live edits
    • Change requests
    • PDF export
    • Inviting your team
    • Comments
    • Notifications
  • Integrations
    • Install and manage integrations
    • GitHub Copilot
  • Account management
    • Plans
      • Legacy pricing
      • Sponsored site plan
      • Non-profit plan
      • Billing policy
    • Subscription cancellations
    • Personal settings
    • Organization settings
    • Member management
      • Invite or remove members
      • Roles
      • Teams
      • Permissions and inheritance
    • SSO & SAML
      • SSO Members vs non-SSO
  • Resources
    • GitBook UI
    • Keyboard shortcuts
    • Glossary
Powered by GitBook
LogoLogo

Resources

  • Showcase
  • Enterprise
  • Status

Company

  • Careers
  • Blog
  • Community

Policies

  • Subprocessors
  • Terms of Service

LoadingFor you

Basing on your context...
On this page
  • Sharing a space or collection
  • Invite members

Was this helpful?

Edit on GitHub
  1. Collaboration

Inviting your team

Collaborate with your teammates on spaces, collections and more

Last updated 3 months ago

Was this helpful?

Sharing a space or collection

To share a space or collection, click the share button in the top-right corner. This will open the share modal.

Inside the share modal, you’ll see different sharing options along the top.

You can see everyone who access, and their level of access, in the share modal. You can also make changes to these settings here.

Invite members

Invite a person or team from your organization

Some people in your team may not have access to a specific space in your GitBook organization due to their role or specific permissions settings. To invite someone who’s already a member of your organization, simply type their name, choose their role for this space, and hit Invite.

Invite someone from outside your organization

To invite someone from outside your organization, simply add their email address, choose their role, and hit Invite. When you choose their role, you can also choose to leave the Invite as an organization member toggle switched on to make them a full member of your organization, with access to all your team’s content when they’re logged in.

Inviting someone either as a full member or a guest will make them a member of the organization that owns the space, which will increase your overall subscription charge.

Invite guests via link

If you don’t want to use email to invite someone to your content, or want to invite a number of people as guests quickly, you can create a secret link. You can also set the role of guests that join using the link, so you have control over who can do what to your content.

By default, every member of your organization can see all the content in your organization. However, their permissions are inherited from the assigned to them within your .

You can also add a by typing the team name and hitting Invite.

Alternatively, toggle this off to invite them as a . Guests only have access to the individual spaces that you invite them to, and can be given a specific role within that space — whether it’s to edit the content, or only view and comment on it.

The cost for this will depend on .

It is also possible to from within the Organization settings area.

When you share this link, anyone who clicks on it will be able to sign up, join your organization as a , and get access to just this single space and its content.

You can revoke the link at any time by opening the Actions menu next to the link and choosing Revoke.

role
Organization settings
team
your organization’s plan
invite members to the organization
guest
guest
Invite your team to GitBook to collaborate on pages, spaces, and published sites.