Git Accounts
Link the git accounts committing into your repositories to the people in your workspace, so their edits carry their name.
What the screen is
Go to Settings → Members → Git accounts.
Every time documents arrive from a repository — through meldoc push or through a connected repository’s sync — Meldoc records the name and email address git reported for each file. The list is those accounts, with how many commits have been seen and when each was last active.
An account is just an email address as far as Meldoc is concerned. Linking one to a member is what turns it into a person: their name, their avatar, and their identity on every document that account has contributed to — past ones included, because the link is applied when the page is drawn rather than when the commit arrived.
A link grants nothing. It changes whose name is displayed and nothing else: no access, no seat, no notification. It is still an admin action, because it puts one person’s name under another’s edits across the whole workspace.
Filter the list
All, Not linked and Linked narrow the list; the search box matches on name, email or login. The badge next to the filters counts every unlinked account in the workspace, not just the ones on screen.
Not linked is the one to work through. Each row there is edits currently showing an email address instead of a colleague.
Link and unlink
You need to be a workspace admin.
- Find the account — Not linked is usually the fastest route.
- Pick the person in Link to member.
Unlink on a linked row undoes it.
Linking by hand outranks everything: Meldoc will not re-link an account you unlinked, and will not move a link you made. That is the point — a decision by a person is not something an automatic pass should undo the next morning.
One person can hold as many accounts as they have addresses: a work address, a personal one, the hidden users.noreply address GitHub can commit under, the laptop that was set up wrong. Link them all to the same member and they collapse into one name wherever contributors are shown.
An account can be linked to only one member. If two people really share a git account, no linking will separate their edits — that is a fact about the account, not about Meldoc.
Accounts Meldoc links on its own
Some rows are already linked when you get there. Two things do that, and both are conservative on purpose.
A verified address that matches a member. Only a verified one: an address a person has merely entered is a claim, and anyone can set any address in their local git config. That rule is the reason nobody can put their edits under your name by typing your email into git config.
A GitHub users.noreply address in its modern form — [email protected] — where the number identifies the account beyond doubt. It is matched to a member only if the GitHub account behind it is connected to a Meldoc user who is a member of this workspace. The older form without the number is never matched, because a login can be taken over after an account is deleted and a number cannot.
Anything else waits for you.
When someone leaves
Removing a member unlinks their git accounts in the same step, so nothing keeps showing a departed colleague as a current member.
The accounts stay in the list as unlinked. If that person is invited back and their address is verified, they are picked up again automatically — but any link you had made by hand is gone and has to be made again.
What’s next?
Contributors and Co-authors — Where these names appear on a document, and how to hide one.
Team Roles & Permissions — What admins can do that members cannot.
Version History — Read an earlier version, and see who is credited with it.