Organizations and Projects Overview

This page explains the structure of “organizations” and “projects” — the basic units for managing resources and users in Lorel.ai — and the role each one plays.

Overview

Lorel.ai manages resources and users in two layers: “organizations” and “projects.”

• Organization: a grouping for a company, business, or department (a single user can belong to multiple organizations at the same time)
  • Project A: a grouping for a system environment or service
  • Project B
  • Project C

A user must first belong to an organization before they can join any project under it.

A user who does not belong to an organization cannot join any project under it.

• Multi-org membership: A single user can belong to multiple organizations at the same time. The combination of organization and user is unique — the same user cannot belong to the same organization more than once.
• Multiple projects: Multiple projects can be created under a single organization, split by system environment or service. The maximum number of projects you can create follows your subscription plan (see Change Your Contract Plan for how this limit is checked when downgrading).
• Independent role systems: Organization roles and project roles are independent. Actions inside a project require a project role in addition to (and separate from) an organization role. See Roles and Permissions for details.

Organization

An organization is the top-level layer that governs contract/billing information and all users and projects.

Basic information

• Organization name: the display name in Lorel.ai. 1–255 characters (a name of blank space only is not allowed; can be changed after creation).
• Organization ID: a unique identifier automatically assigned when the organization is created (cannot be changed). It can be checked on the Organization Settings screen.

Management

• Creating an organization: any authenticated user can create a new organization. Prior membership in an existing organization or an organization role is not required (the creating user is automatically granted the Owner role).
• Renaming an organization: only a user with the Owner or Manager role can rename an organization.
• Viewing and switching organizations: the sidebar lists the organizations you currently belong to; selecting one switches your active organization. Fully deleted organizations do not appear in the list. An organization whose contract has not yet started appears separately as “Pending contract.” An organization under cancellation (during the data export period) continues to appear until that period ends. See the billing and payment page for how to check your contract status.

Deleting (canceling) an organization

Users cannot delete an organization from the screen themselves. To cancel, follow the billing and payment procedure.

Project

A project is the layer that manages actual operations and incidents — Integration, Runbooks, AI Agents, trigger rule configuration, and more.

Basic information

• Project name: the display name in Lorel.ai. 1–255 characters (a name of blank space only is not allowed; can be changed after creation).
• Project ID: a unique identifier automatically assigned when the project is created (cannot be changed by users). It can be checked on the Project Settings screen.
• Type (join method): determines the procedure for a user to join the project. The default is invite-only, and it can be changed after creation.

Only a user with the project’s Administrator role can view and approve pending join requests.

Management

• Creating/adding a project: only a user with the organization’s Owner or Manager role can create a project (the creator is automatically added as that project’s Administrator).
• Editing a project: only a user with the organization’s Owner or Manager role can change the project’s name or type (this can be done even without being a member of that project). The project Administrator role alone does not permit editing or deleting the project itself.
• Viewing/switching joined projects: the sidebar lists the active projects you currently belong to, letting you switch your working target.
• Viewing all projects (Organization Settings > Projects): a user with the organization’s Owner or Manager role can view every project in the organization, including projects that were deleted and are still within the grace period before permanent deletion (currently 3 days). A project you have not joined shows “Not a member” in the role column. Owners/Managers can rename, change the type of, or delete projects they have not joined (member management is handled by that project’s Administrators), but accessing internal resources such as Incidents or Runbooks requires membership in that project. Deleted projects are shown grayed out and cannot be operated on. After the grace period they no longer appear in the list.

Deleting a project (restrictions)

• Permission: only a user with the organization’s Owner or Manager role can delete a project.
• After deletion: a deleted project cannot be restored, and no further configuration changes or operational actions can be performed on it. After a grace period (currently 3 days), the data that belongs to the project (incidents, tasks, Runbooks, AI agents, ingested data, and so on) is permanently deleted by the system. The Audit Log is not deleted when a project is deleted; it follows its own retention period.

What you can do

*For details on the role required for each operation, see Roles and Permissions.

Related pages

• Roles and Permissions