Frequently Asked Questions (FAQs)
Does the other party need a GitLaw account to sign or negotiate?
No - for signing and viewing, the other party does not need a GitLaw account.
Here is a quick breakdown of what requires an account and what does not.
| Action | GitLaw account needed? |
|---|---|
| Sign a document via emailed link | No |
| View a document via a shared link (anyone-with-link) | No |
| Make tracked-change edits / submit a redline | Yes - requires an account to create a copy and submit a change request |
| Initiate or manage sharing | Yes |
Signing
When you send a document for signature, the other party receives an email with a link to sign in their browser. They do not need to create a GitLaw account to open the document and apply their signature. Once everyone has signed, all parties receive a copy of the executed PDF by email.
Viewing via a shared link
If you share a document using the "anyone with the link" setting, the recipient can open and read it without logging in. If you set the link to "invited only", the recipient must be authenticated and must already be a collaborator or pending invitee on the document - so in practice they will need an account.
Negotiating and making edits
This is where an account becomes necessary. To submit a redline or tracked-change proposal back to you, a counterparty must create a copy of the document and submit it as a change request. That workflow requires a GitLaw account. If you want a counterparty to collaborate this way, invite them directly by email from the document's sharing panel.
For more details, see how to get a document signed, share a document or invite a counterparty, who can see my documents, and how to negotiate and redline a contract.