GitLaw Email Assistant - User Guide

The GitLaw Email Assistant allows you to interact with GitLaw's AI-powered document generation and analysis tools directly from your email inbox. Simply send an email with your request, approve it, and receive AI-generated documents and responses via email.

Getting Started

Prerequisites

• You must have a GitLaw account
• Use the email address associated with your GitLaw account
• Send emails to: [email protected]

How It Works

Basic Workflow

1. Send your request via email to [email protected]
2. Receive an approval email with a preview of your request
3. Click the approval link to confirm
4. Get your response via email with AI-generated content and/or documents

Use Cases

Use Case 1: Generate Documents (e.g., Employment Agreement)

Step 1: Send your request

Compose an email to [email protected] with your request in the body:

Subject: Generate employment agreement

Hi, please generate a employment agreement for <person's name>. They are starting on <data> as a <position>. Salary is <salary>. Address is <address>. Anything else you need?


Step 2: Receive approval email

You'll receive an email from GitLaw Assistant with:

• A preview of your request
• An "Approve and continue" button
• Note: The approval link expires in 24 hours

Step 3: Approve the request

Click the "Approve and continue" button in the email. This will:

• Create a new chat session (you can view this by logging in to your account on the web)
• Process your request with AI
• Generate the requested document

Step 4: Receive your response

You'll receive an email containing:

• GitLaw's response to your request
• A link to view the generated document in GitLaw
• If a document was generated, it will be attached as a file
• A conversation ID in the subject line (e.g., Re: GitLaw AI Response [EF-ABC123])

Use Case 2: Analyze or Process Attached Files

Step 1: Send email with attachment

Compose an email to [email protected] and attach a file:

Subject: Review this contract

Please review this contract and identify any potential issues.


Attach a supported file (see Supported File Formats below).

Step 2-4: Same as Case 1

Follow the same approval and response process. The system will:

• Upload your attached file
• Convert it for processing
• Analyze it based on your request
• Generate a response and/or modified document

Use Case 3: Continue a Conversation

Step 1: Reply to a response email

When you receive a response email, you can continue the conversation by simply replying to it. The system automatically detects the conversation ID from the subject line.

Subject: Re: GitLaw AI Response [EF-ABC123]

Can you add a non-compete clause to this document?


Important:

• Keep the conversation ID [EF-ABC123] in the subject line when replying
• The system will automatically continue the same conversation thread
• No approval is needed for replies to existing conversations

Supported File Formats

You can attach the following file types:

• Documents: .docx, .doc, .odt
• Text files: .md, .txt
• Web formats: .html
• PDFs: .pdf

File Size Limits

• Maximum file size: 1 MB
• Currently only the first attachment is processed (additional files are ignored)

Email Format Guidelines

What to Include

Good examples:

Subject: Generate employment agreement

Please create an employment agreement for a software engineer position.


Subject: Review contract

I've attached a service agreement. Please review it and highlight any problematic clauses.


Subject: Add clause

Can you add a termination clause to the attached document?


What Happens to Your Email

• The system extracts the text from your email body
• Forwarded message sections are automatically removed
• Only the first 150 characters are shown in the approval preview
• The full message is used for processing

Response Email Contents

When you receive a response email, you'll see:

1. Your original question - What you asked
2. AI Response - The AI's answer or analysis
3. Document link - If a document was generated, a link to view it in GitLaw
4. Attachments - Generated documents (usually .docx format)
5. Conversation ID - In the subject line for continuing the conversation

Troubleshooting

I didn't receive an approval email

• Check your spam/junk folder
• Verify you're using the email address associated with your GitLaw account
• Make sure you sent the email to [email protected]
• Wait a few minutes and check again

The approval link expired

• Approval links expire after 24 hours
• Send a new email with your request to start over

My file wasn't processed

• Check that your file format is supported (see Supported File Formats above)
• Ensure the file size is under 1 MB
• Only the first attachment is processed - remove other attachments if needed

I got an error email

• Read the error message for details
• Common issues:
  • Email address not associated with a GitLaw account
  • File format not supported
  • File too large
• Try again with corrected information

I can't continue the conversation

• Make sure you're replying to the response email (don't start a new email)
• Keep the conversation ID in the subject line (e.g., [EF-ABC123])
• Use the same email address you used for the original request

Best Practices

1. Be specific in your requests - Clear instructions yield better results
2. Include context - Mention what type of document or analysis you need
3. Keep conversations organized - Reply to response emails to maintain context
4. Check file formats - Ensure attachments are in supported formats
5. Monitor file sizes - Keep attachments under 1 MB

Security & Privacy

• Only emails from registered GitLaw accounts are processed
• Approval links are unique and expire after 24 hours
• Files are securely stored and processed
• Each conversation is tied to your account
• If you didn't send an email, you can safely ignore approval requests

Examples

Example 1: Document Generation

Email sent:

To: [email protected]
Subject: Create partnership agreement

Please generate a partnership agreement for two partners starting a tech company.


Approval email received:

• Preview: "Please generate a partnership agreement for two partners…"
• Button: "Approve and continue"

Response email received:

• AI response with partnership agreement details
• Link to view document in GitLaw
• Attached .docx file with the agreement
• Subject: Re: GitLaw AI Response [EF-XYZ789]

Example 2: Document Analysis

Email sent:

To: [email protected]
Subject: Review lease agreement
Attachment: lease-agreement.pdf

Please review this lease agreement and identify any clauses that favor the landlord.


Response email received:

• AI analysis of the lease agreement
• List of identified clauses
• Suggestions for negotiation points

Example 3: Continuing Conversation

Reply sent:

To: [email protected]
Subject: Re: GitLaw AI Response [EF-XYZ789]

Can you modify the partnership agreement to include a buyout clause?


Response email received:

• Updated document with buyout clause
• Link to view changes
• Attached updated .docx file

Questions?

If you encounter issues or have questions:

1. Check this guide for common solutions
2. Verify your email address is registered with GitLaw
3. Ensure you're following the format guidelines
4. Contact GitLaw support if problems persist

Note: The Email Assistant is designed to help you work with GitLaw's AI tools directly from your email. For complex workflows or detailed document editing, consider using the GitLaw web application directly.

‍