GitLaw How-To guides
Manage your organisation: roles, members and seats
To create a GitLaw organisation, open your account menu, select New organisation, enter a name and confirm; you become the Org Owner automatically. Invite members from the organisation's Members settings by entering their email and choosing a role. Seats are unlimited on every plan, and all members share a single AI credit pool.
Before you start: a GitLaw account.
How do I create an organisation in GitLaw?
A GitLaw organisation is a shared workspace for your team. Documents created inside an organisation workspace are owned by the organisation, not the individual who created them, so your firm's work stays with the firm even when people move on.
- Open your account menu and select New organisation.
- Enter a name and confirm.
- You are automatically assigned the Org Owner role.
What can each organisation role do?
| Role | Sees all org files | Invites members | Removes members | Changes roles | Edits org settings |
|---|---|---|---|---|---|
| Owner | Yes | Yes | Yes | Owner / Admin / Member | Yes |
| Admin | No (unless shared) | Yes | Yes (not Owners) | Admin / Member only | No |
| Member | No (unless shared) | No | No | No | No |
There must always be at least one Owner. An Owner can only leave or remove their own Owner role if another Owner already exists. For full details on document-level access (Viewer, Editor, Owner), see File sharing permissions in personal and organisation accounts.
How do I invite members to my organisation?
- Go to your organisation's Members settings.
- Enter the person's email address and select a role.
- They receive an invitation to join. Once accepted, they can create and collaborate on organisation documents.
Seats are unlimited on every plan, so invite your whole team without worrying about per-seat charges. See How does billing work? for plan details.
How do I change a member's role?
- Open Members settings.
- Find the member and select a new role from the dropdown.
Owners can change any role. Admins can change Member and Admin roles but cannot grant or revoke the Owner role.
The shared AI credit pool
Every organisation has a single shared credit pool. All members draw from it, with no per-person allocation. You can monitor usage and top up credits from your organisation settings.
How do I remove a member (off-boarding)?
- Open Members settings.
- Select the member and choose Remove from organisation.
When a member leaves or is removed:
- Organisation-owned documents stay with the organisation and remain accessible to Owners and anyone they were shared with.
- Personally-owned documents stay with the departing user and are not accessible to the organisation.
- Access is revoked immediately.
To keep work within the organisation, make sure documents are created inside the organisation workspace, or transfer ownership before the person leaves. Any member can also leave an organisation at any time from their account settings; the same ownership rules apply.
Frequently asked questions
Are GitLaw organisation seats really unlimited?
Yes. Seats are unlimited on every plan, so you can invite your whole team without per-seat charges.
What happens to documents when someone leaves the organisation?
Organisation-owned documents stay with the organisation. Personally-owned documents stay with the departing user. Access is revoked immediately on removal.
Can there be no Owner?
No. There must always be at least one Owner. An Owner can only step down or leave if another Owner already exists.
Related articles
- File sharing permissions in personal and organisation accounts
- How does billing work?
- Share a document or invite a counterparty
Reviewed by the GitLaw team. Last updated 29 July 2026.