Granting LexGrow Access to Your Law Firm's GitHub Repository

If your firm's website is built by developers (rather than on Wix, Squarespace, or WordPress), the website lives in something called a GitHub repository — a place where the code is stored and updates are made. To ship the SEO fixes, schema markup, and content updates we recommend, the LexGrow team needs to make changes there directly, without waiting in line behind your developer.

This takes about 2 minutes. You don't need to understand any of the technical bits — just follow the clicks below.

What you'll need

• Username to add:lexgrowdev
• Email (if it asks):mkashif@lexgrow.com
• Admin access to the repo. If you can see a Settings tab when you open the repo on GitHub, you have it. If you can't, forward this guide to whoever built your website.

The 3-minute steps

1. Go to github.com and sign in.
2. Open the repository for your law firm's website. (If you don't know which one, ask your developer or your concierge — we can help identify it.)
3. Click the Settings tab at the top of the repo.
4. In the left sidebar, click Collaborators (or Collaborators and teams if your repo is under an organization).
5. Click Add people / Invite a collaborator.
6. Type lexgrowdev and pick the matching account.
7. For the role, choose Maintain. (Why Maintain: it lets us push fixes straight to the live site's branch, which is what you're paying us to do. It does not let us delete the repo, change billing, or transfer ownership.)
8. Click Add lexgrowdev to this repository.

That's it. GitHub will send us an invitation; we'll accept within one business day.

Tell your concierge

Reply to your onboarding email with:

GitHub access invited for lexgrowdev — repository: [the repo name, e.g. yourfirm/firm-website]

If you have more than one repo (a marketing site, a client portal, etc.), include which one is for the public website.

If something goes wrong

• "You need admin access to invite collaborators" — you're not an Admin on this repo. Forward this guide to whoever set it up (usually your web developer).
• The invite has been "Pending" for more than a day — it may have landed in our spam. Send your concierge the repo link and we'll accept manually.
• You see a warning about "outside collaborators" or "SSO" — your IT team has extra rules in place. Tell your concierge and we'll work with whoever administers your GitHub to finish the setup.
• We tell you we can't push to your live branch — your developer set up a "branch protection" rule that's blocking us. Forward our message to your developer; they'll know exactly what to flip in 30 seconds.

Once we're in, your LexGrow engineer starts shipping fixes — typically within one business day.