If your firm's website is built by developers (rather than on Wix, Squarespace, or WordPress), the website lives in something called a GitLab project — 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:
@lexpair_cto - Email (if it asks):
mkashif@lexgrow.com - Maintainer or Owner access to the project. If you can open the project's Manage → Members page and see an Invite members button, you have it. If you can't, forward this guide to whoever built your website.
The 2-minute steps
- Go to gitlab.com (or your firm's GitLab URL, if your team hosts its own) and sign in.
- Open the project for your law firm's website. (If you don't know which one, ask your developer or your concierge — we can help identify it.)
- In the left sidebar, click Manage, then Members.
- Click Invite members in the top-right.
- In the username field, type
lexpair_ctoand pick the matching account. - For the role, choose Maintainer. (Why Maintainer: GitLab blocks lower roles from pushing to the live site's branch by default, and pushing fixes to that branch is what you're paying us to do. Maintainer does not let us delete the project or change ownership.)
- Click Invite.
That's it. Access is live immediately — no waiting for us to accept.
Tell your concierge
Reply to your onboarding email with:
GitLab access granted to
@lexpair_cto— project: [the project name, e.g.yourfirm/firm-website]
If your team hosts its own GitLab (not gitlab.com), include that URL so we know where to sign in.
If something goes wrong
- "Invite members" button is missing or greyed out — your account doesn't have permission to add members. Forward this guide to whoever set up the project.
- GitLab can't find the username — paste the email
mkashif@lexgrow.cominstead. - You see a warning about admin approval, SSO, or 2FA — your IT team has extra rules in place. Tell your concierge and we'll work with whoever administers your GitLab to finish the setup.
- We tell you we can't push to your live branch — your developer set up a "protected branch" 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.