Manage the team and seats¶
The portal shows how much of your plan you are using — projects and seats — and who your members are. It also holds your company-wide policy defaults.
Projects and seats against your plan¶
Your company (Customer) has two limits, each of which may be unlimited (∞):
- Maximum projects — how many GitM-initialised repositories the company may have.
- Maximum seats — how many distinct members may have access across all projects.
The Overview shows current usage against those limits, for example Projects 3 / 10 · Seats 14 / 25. Use Refresh to recompute on demand; otherwise the numbers come from a cache that is at most a few minutes old and is re-tallied automatically once a day.
How a seat is counted¶
- A seat is one distinct person — a GitHub login — with access to any of the company's projects, whether an active collaborator or someone with a pending invitation.
- The same login on several projects is still one seat. Seats are de-duplicated across the whole company.
- A login that has access to two different companies counts as a seat in each — that is the intended billing behaviour.
The team roster¶
The Team tab lists every member across all projects. For each member you see their avatar and login, the projects they belong to with their role on each, and whether they are active or still invited (a pending invitation). The member count always agrees with the seat count on the Overview.
Roles are shown with GitM's role names — Viewer, Engineer, Manager, Administrator — not raw GitHub permission words. See Roles and permissions.
A connected account whose app install cannot read invitations will under-count pending members. If the roster looks short, re-check that Connection's app permissions (Connect GitHub).
When you are over a limit¶
If usage reaches or exceeds a limit, the portal shows an over-limit marker on the Overview and Team cards, and the people who add members feel it where the work happens:
- Adding a member at the seat limit is blocked in GitMCloud's Team tab — unless the person you are adding already holds a seat on another project (they add no new seat).
- Creating a new project past the project limit is blocked in the GitM desktop add-in.
To raise a limit, contact your Tandem operator to change the plan. Suspended companies keep working in the plain desktop Git workflow but lose the licensed portal and cloud actions.
Company policy defaults¶
The Policy tab holds defaults that apply across the company's projects — sharing, release control, security, and file-policy settings, plus a Projects group that controls whether members (not just repository admins) may create new projects.
These are defaults; an individual project can hold its own settings. Set them here so a new project starts from your company's conventions rather than the built-in ones.
Troubleshooting¶
| Symptom | Cause | Fix |
|---|---|---|
| Usage looks stale | The cached tally hasn't refreshed | Click Refresh on the Overview |
| Seats higher than expected | A login appears on projects you forgot about, or across two companies | Open the Team tab and review each member's projects |
| A member is missing | Their Connection isn't linked, or the app can't read that repo's invitations | Check Connections and the app's repo access |
| "Over limit" but you disagree | The tally counts pending invitations too | Cancel stale invitations on GitHub, then Refresh |
Known limitations¶
- The portal's team view is read-only. Adding, removing, and re-roling members happens in GitMCloud's Team tab or on GitHub — see Manage branches and team.
- Changing a plan or a limit is an operator action.