.. _requirements:

Requirements
============

.. contents:: On this page
   :local:
   :depth: 2

Before you begin
----------------

Blocks is a hosted service, so there is no software to install or server to maintain. To use it
you need:

* A **Blocks workspace account** (see :ref:`account_registration`).
* An **LMS that supports LTI 1.3 / LTI Advantage**, such as Moodle, Open edX, Canvas,
  Blackboard, or D2L.
* **Administrator access to that LMS**, or the cooperation of someone who has it, to complete the
  one-time trust setup that connects the LMS to Blocks.
* A modern web browser (current versions of Chrome, Firefox, Edge, or Safari).

LMS requirements
----------------

To connect an LMS to Blocks you will need to be able to register an external LTI 1.3 tool. The
exact menus differ by platform:

* **Moodle** — supports LTI 1.3 *Dynamic Registration*, which automates most of the setup. See
  :ref:`moodle`.
* **Open edX** — uses the ``lti_consumer`` XBlock. See :ref:`openedx`.
* **Canvas, Blackboard, D2L** — register Blocks as an LTI 1.3 developer key / tool using the
  endpoints and keys shown on your platform's page in the Blocks workspace.

What you do *not* need
----------------------

* You do **not** need to host or operate an LTI tool server.
* You do **not** need to manage TLS certificates or signing keys — Blocks manages the keypairs
  used to sign launches.
* You do **not** need your own AI provider account. AI features run on the Blocks-managed
  backend and are metered with :ref:`credits <billing>`.

Account and plan limits
-----------------------

Each subscription plan sets limits on how many LMS platforms, registrations, deployments,
knowledge bases, knowledge base sources, and team members your workspace may have, along with a
monthly AI credit allowance. Review the current plans and limits in **Billing** within your
workspace. See :ref:`billing`.

`Back to Home <index.html>`_