Manage branches and team¶
The Branch tab controls which branch GitMCloud reads, and the Team tab manages collaborators, their roles, and Supplier Exchange shares.
Switch which branch GitMCloud shows¶
This only changes what GitMCloud displays. It does not switch anyone's local Git branch — that's a GitM/local-git action.
- Open the Branch tab (or Settings → Connection).
- Select a branch and Switch.
- The Files, Snapshots, and BOM tabs now read that branch.
Manage the team¶
The Team tab lists collaborators with their roles and recent activity. Administrator-level users can manage membership.
Prerequisites¶
- Administrator role (GitHub
admin) on the repository.
What admins can do¶
- Invite a member: search a GitHub username, pick a role, send the invitation.
- Change a role inline (updates optimistically; reverts if GitHub rejects it).
- Remove a member (with confirmation).
- Resend or cancel pending invitations.
Notes: - Your own row shows your role and a Manage on GitHub link — you don't change your own role inside GitMCloud. - The repository Owner row is always locked — the owner can't be demoted or removed here.
Roles map to GitHub permissions — see Roles and permissions.
Manage Supplier Exchange shares¶
The Team tab → Shares section shows all shares created for this repository.
For the full workflow — setting up Exchange, creating and sending share links — see Share files with suppliers.
Reading the shares list¶
Each share row shows:
- Note — the label set when the share was created (e.g. "Rev B drawings for ACME").
- Created by and creation date.
- Status — active,
Expiredbadge, orRevokedbadge. - Expiry warning — a ⚠ badge appears when the share expires within 3 days
(e.g.
⚠ 2dor⚠ Today). - File count and a 🔒 icon if the share is password-protected.
Revoke a share¶
Click Revoke on any active share. The link stops working immediately. Revocation cannot be undone — create a new share if the recipient still needs access.
Copy a share link¶
Click the share link or copy button in the row to re-copy the URL to your clipboard.
Expected result¶
- Branch switch changes the data GitMCloud shows across all tabs.
- Team changes are written through the GitHub collaborator API and reflected on GitHub.
- Revoked shares return "This link is no longer available" to recipients immediately.
Troubleshooting¶
| Symptom | Cause | Fix |
|---|---|---|
| Team actions are missing/disabled | You're not an Administrator | Only admins manage the team |
| A role change reverted | GitHub rejected it (permissions) | Confirm you have admin rights; check the member's GitHub access |
| Invited user can't see the repo | Invitation still pending | They must accept the GitHub invitation |
| Shares section is empty | No shares created yet, or Exchange not set up | Create a share; if Exchange isn't set up, see Settings → Exchange tab |
Known limitations¶
- Team management is a thin layer over GitHub collaborators/invitations — it reflects GitHub's rules and limits.
- Branch switch affects GitMCloud's view only; it has no effect on any local working copy.
- Share revocation is permanent — there is no "un-revoke".