> For the complete documentation index, see [llms.txt](https://help.lawlibrary.org.za/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.lawlibrary.org.za/subscription-management/organisations-and-chambers.md).

# Organisations and chambers

Understand how My LawLibrary works for organisations and chambers.

My LawLibrary for Organisations and Chambers lets a firm or chambers pay for several people's access in one place. Each person keeps their own account and private research space, while authorised administrators manage members, seats and billing.

## Understand the main terms

* A **seat** is one place on a plan that an organisation can assign to a member.
* An **assigned seat** provides a subscription to a member.
* A **reserved seat** is being held for a pending invitation.
* An **unused seat** is an active seat that the organisation has not assigned to a member.
* A **plan** determines the My LawLibrary features and limits available to the member using the seat.
* A **subscription** is the access provided to a person, whether they pay for it themselves or receive it through an organisation.

Using **seat** for the organisation's paid capacity avoids confusing it with a member's subscription.

## Organisation roles

Roles determine what people in an organisation can do.

A person's role and paid access are separate. For example, an administrator can manage the organisation without using a paid seat.

| Role          | What the person can do                                                                                                             |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| Owner         | Has all administrator rights, transfers ownership and requests organisation closure. An organisation has one owner.                |
| Administrator | Invites and removes members, assigns seats, changes plans and manages billing. An administrator cannot remove or demote the owner. |
| Member        | Uses their own LawLibrary account and can view their membership details. A member cannot manage the organisation or its billing.   |

## Understand the organisation billing cycle

An organisation uses one billing cycle for all its seats: monthly or annual. Individual members cannot choose a different cycle for an organisation-funded seat.

The organisation's billing cycle starts when its opening amount is settled. If the organisation has only free seats, this happens without a payment. New paid seats and upgrades can start during the cycle after the prorated amount is paid. All seats renew together. Contact LawLibrary to arrange a change between monthly and annual billing.

## Understand research privacy

Every member has a private account and research space. An organisation uses one of two privacy settings:

* **Billing only**: administrators can manage membership and billing but cannot see member usage.
* **Managed usage**: administrators can see whether an account has been activated, the last login date, and current counts for saved documents, folders, search alerts and followed topics.

Administrators can never see document titles, searches, annotations, chats, downloads or research history. A member's [**My Account**](https://lawlibrary.org.za/accounts/profile/) page tells each member which privacy setting applies and what administrators can see.

Contact LawLibrary to change your organisation's privacy setting.

## Managing an organisation

If you are the organisation owner or an administrator:

1. Log in to My LawLibrary.
2. Click your name in the top-right menu.
3. Click [**Manage \[organisation\]**](https://lawlibrary.org.za/accounts/organisation/).

Use [**Overview**](https://lawlibrary.org.za/accounts/organisation/) for a summary, [**Members**](https://lawlibrary.org.za/accounts/organisation/members/) for people and seats, [**Billing**](https://lawlibrary.org.za/accounts/organisation/billing/) for billing details, and [**Invoices**](https://lawlibrary.org.za/accounts/organisation/invoices/) for charges, payments and invoices.

All organisation members can see their role, membership and privacy information in the **Organisation** section of their [**My Account**](https://lawlibrary.org.za/accounts/profile/) page.

## Choose what you need to do

* [Join or leave an organisation](/subscription-management/organisations-and-chambers/join-or-leave-an-organisation.md).
* [Manage members and seats](/subscription-management/organisations-and-chambers/manage-organisation-members-and-seats.md).
* [Manage organisation billing](/subscription-management/organisations-and-chambers/manage-organisation-billing.md).
* [Manage an individual subscription](/subscription-management/upgrade-your-subscription.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.lawlibrary.org.za/subscription-management/organisations-and-chambers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
