Ligantic
Knowledge Base
Tutorials
Updates
Search Articles
Login
Free Sign Up
Home
Get Started
Tutorials
How-to guides
Reference
Explanation
Spaces
Schemas
Flows
Experiences
Endpoints
SDK and CLI
Browse documentation
Home
Get Started
Spaces
Schemas
Flows
Experiences
Endpoints
SDK and CLI
Docs
/

Organisations

An organisation is an account that owns Spaces, members, Agents and billing. This page describes organisation membership types, the organisation pages in Studio, permissions, seats, invites, Space ownership and removal. For the Agents an organisation controls, see Agents.

Where Organisations Are Managed

In Studio, open the user menu and select Organisations. The Organisations page lists:

Item

Shows

Each organisation you belong to

Its display name, your membership type (owner or member), a Setup required badge while the organisation has no subscription, and a Leave action.

Pending Invites

Organisation invites sent to your email address, with Accept and Decline.

Create Organisation opens a form with one field, Display Name. Continue to billing creates the organisation, makes you its owner, and opens billing setup: a billing address, then a billing account with a plan and a number of seats. Until a subscription exists, the organisation shows Setup required and its owners can only set up billing and remove the organisation; members have no organisation permissions.

A display name that contains profanity is rejected with Display name contains profanity. Contact support if you believe this is an error.

Organisation Tabs

Selecting an organisation opens a page with these tabs. A tab appears only when you hold its permission.

Tab

Contents

Required permission

Spaces

The organisation's Spaces, your role in each (Space User Role), Join and Leave, and Create Space.

spaces:read

Members

Seat usage and every member, with Type (owner or member) and Actions.

spaces:read

Invites

Pending invites, seat usage, and Invite User, or Add seats when every seat is used.

members:invite:read

Agents

The organisation's Agents. See Agents.

agents:read

Billing

Addresses and Billing Accounts (plan, seats, status and monthly total).

billing:accounts:read and addresses:read

Config

Danger zone with Remove Organisation.

organisation:remove

Audit

Device lifecycle events. Shown only when device pairing is enabled. See Devices — Audit.

organisation:audit:read

Membership Types

Every member is either an owner or a member.

Type

Permissions

Owner

Every organisation permission. Until the organisation has a subscription, only the billing setup permissions and organisation:remove.

Member

spaces:read, spaces:create, spaces:transfer:to-org and spaces:join. Members cannot manage settings, billing, invites, other members or Agents.

An organisation always has at least one owner:

  • The last owner cannot leave. The request fails with Cannot leave the organisation as the last owner. The organisation must have at least one owner.
  • The last owner cannot become a member. The request fails with Cannot downgrade the last owner to member. The organisation must have at least one owner.
  • You cannot change your own type: You cannot change your own role.

Owners change another member's type with the Type select on the Members tab.

Organisation Permissions

Permission

Allows

organisation:remove

Removing the organisation

spaces:read

Listing the organisation's Spaces and members

spaces:create

Creating a Space owned by the organisation

spaces:join

Joining one of the organisation's Spaces

spaces:transfer:to-org

Transferring a Space into the organisation

spaces:transfer:from-org

Transferring one of the organisation's Spaces to yourself

members:remove

Removing other members

members:update-role

Changing a member's type

members:invite:read

Viewing invites

members:invite:create

Inviting users

members:invite:cancel

Cancelling invites

members:invite:resend

Resending invites

addresses:read, addresses:create

Viewing and adding billing addresses

billing:accounts:read, billing:accounts:create, billing:accounts:update

Viewing, creating and changing billing accounts

billing:credit:read, billing:credit:purchase, billing:credit:usage:read

Viewing, buying and viewing usage of credits

billing:subscription:manage

Managing the subscription

billing:space:set-billing-account

Setting a Space's billing account

agents:read, agents:create, agents:remove, agents:spaces:read, agents:spaces:join, agents:api-keys:read, agents:api-keys:create, agents:api-keys:remove

Managing Agents. See Agents — Permissions.

agents:devices:read, agents:devices:create, agents:devices:approve, agents:devices:update, agents:devices:disable, agents:devices:remove, agents:devices:policy:update, organisation:audit:read

Managing devices and viewing the audit log. See Devices — Permissions.

Seats

The plan sets how many seats the organisation has. Seat usage is shown on the Members and Invites tabs, in one of these forms:

Label

Meaning

Seats: <used> / <seats>

A limited number of seats.

Seats: <used> used (Unlimited)

Seats are not limited.

Each member uses a seat, and so does each pending invite. An Agent added as an organisation member also uses a seat. When every seat is used, the Invites tab shows Add seats, which opens billing, in place of Invite User, and invites fail with Seat limit reached (<used>/<limit>). Upgrade your plan or add seats to invite more members.

Invites

Invite User takes:

Field

Description

Email

The address to invite. Disposable email addresses are rejected.

Membership Type

Member or Owner.

The invited user receives an email and sees the invite under Pending Invites on the Organisations page. An invite expires 7 days after it is sent. Resending it sends the email again and restarts the 7 days. Cancelling it frees its seat.

Spaces

An organisation's Spaces are listed on its Spaces tab.

  • Join adds you to the Space as Admin - built-in. Leave removes you.
  • Create Space creates a Space owned by the organisation. It takes a Title and an optional Parent Space.
  • A Space you own can be moved into an organisation from Space Settings → Config → Transfers with Transfer to Organisation. Moving an organisation's Space back to you uses Transfer to User in the same place.

Removing Members and Organisations

Removing a member takes away their access to everything associated with the organisation. They keep access to resources they own or were granted by other means, such as Spaces they joined. Removal cannot be undone.

Remove Organisation removes, permanently:

  • the organisation's Spaces;
  • its members;
  • its addresses and billing accounts;
  • its Agents, together with their API keys.

API and CLI

Operation

REST

CLI

List your organisations

GET /api/v1/organisations

ligantic organisations list

Get an organisation

GET /api/v1/organisations/{organisationId}

ligantic organisations show

Create an organisation

POST /api/v1/organisations

ligantic organisations create

Remove an organisation

DELETE /api/v1/organisations/{organisationId}

ligantic organisations delete

Leave an organisation

POST …/leave

ligantic organisations leave

Change a member's type

PATCH …/members/{membershipId}/role

ligantic organisations members set-role

List your pending invites

GET /api/v1/organisations/invites/pending

ligantic organisations invites pending

Accept an invite

POST /api/v1/organisations/invites/{organisationInviteId}/accept

ligantic organisations invites accept

Decline an invite

POST /api/v1/organisations/invites/{organisationInviteId}/decline

ligantic organisations invites decline

List the organisation's Spaces

GET …/spaces

ligantic organisations spaces list

Join a Space

POST …/spaces/{spaceId}/join

ligantic organisations spaces join

Transfer a Space to the organisation

POST …/spaces/{spaceId}/transfer-to-organisation

ligantic organisations spaces transfer-to-organisation

Transfer a Space to yourself

POST …/spaces/{spaceId}/transfer-to-user

ligantic organisations spaces transfer-to-user

Set a Space's billing account

POST …/spaces/{spaceId}/set-billing-account

ligantic organisations spaces set-billing-account

Billing addresses, accounts and credits

…/billing/…

ligantic organisations billing …

… is /api/v1/organisations/{organisationId}. CLI commands that act on a Space use the current Space, or --space <id>. Inviting users and removing members are available in Studio only. For every option, see Generated CLI commands — ligantic organisations.

Related pages

Agents
An Agent is a non-human identity controlled by an organisation. It has no password and does not sign in to Studio. It acts through API keys, with the public API, the SDK or the CLI, and through paired devices, in a Space's App. This page describes Agent properties, limits, organisation membership, Space access, API keys, removal, permissions and the matching API and CLI operations. For a guided walkthrough, see Your First Agent and Paired Device.
Page not found. It may have moved or may not be published.
Browse documentation