GitLaw How-To guides

Manage your organisation: roles, members and seats

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.

Create an organisation

Open your account menu and select New organisation.
Enter a name and confirm.
You are automatically assigned the Org Owner role.

Roles at a glance

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.

Invite members

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 - invite your whole team without worrying about per-seat charges. See How does billing work? for plan details.

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.

Shared AI credit pool

Every organisation has a single shared credit pool. All members draw from it - there is no per-person allocation. You can monitor usage and top up credits from your organisation settings.

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.

Members leaving voluntarily

Any member can leave an organisation at any time from their account settings. The same ownership rules apply as above.