Invite Your Team

Invite users only after your folder structure is stable enough to reflect real ownership boundaries.

Minimum-safe rollout

1. Invite core owners to top-level operational folders.
2. Invite contributors only to folders where they actively work.
3. Add guests only to explicitly scoped collaboration folders.

Permission strategy

• Default to least privilege.
• Expand access only when a workflow actually requires it.
• Prefer folder-scoped access over repo-wide access.

If your deployment is Enterprise-mode, avoid broad root-level sharing unless truly required.

Before sending invites

Check these first:

• Folder names are clear and durable.
• Sensitive folders are isolated.
• You know which role each invitee should get.

After sending invites

Validate with one recipient per role:

• can they open the intended folder?
• can they edit only where expected?
• are they blocked where they should be blocked?

Fix access drift immediately, before scaling to larger teams.

For deeper mechanics, see ../core-concepts/permissions-and-roles.md.