Skip to main content
Organizations are the top-level containers that hold your team, projects, and settings. Projects are isolated workspaces where you actually build and run your agents. This guide explains how to structure and manage both.

​
Organizations: Your Team Container

An Organization represents your team, company, or group. It’s the highest level in PLai Framework.

​
What Organizations Contain

  • Projects - Multiple isolated workspaces
  • Members - Team members with assigned roles
  • Settings - Organization-wide configuration
  • Billing - Usage tracking and payment management
  • Invitations - Pending team member invites

​
Organization Characteristics

Top-Level

Organizations are the highest container. Everything else lives inside them.

Team Container

All team members belong to an organization, not to individual projects.

Isolated

Organizations are completely separate. No data sharing between organizations.

One per Entity

Typically one organization per company, team, or entity.

​
Projects: Your Workspaces

A Project is an isolated workspace within an organization where you create and manage:
  • Agents
  • Tools
  • Datasources
  • Workflows
  • Jobs
  • Triggers
  • Monitoring

​
What Projects Provide

Resources in Project A are completely separate from Project B. No mixing of data or configurations.

​
Multiple Projects Scenario

Organization: Acme Corp
  • Project: Customer Support
    • Agent: Support Bot
    • Agent: FAQ Assistant
    • Tool: Help Desk API
  • Project: Data Processing
    • Agent: Data Validator
    • Agent: CSV Processor
    • Workflow: Nightly ETL
  • Project: Internal Tools
    • Agent: Document Summarizer
    • Tool: File Storage

​
Roles & Permissions

Roles define what members can do. They exist at both organization and project levels.

​
Organization Roles

Applied at the organization level:

​
Project Roles

Applied within individual projects:
A member can have different roles in different projects. Example: ADMIN in Project A but only VIEWER in Project B.

​
Member Management

​
Inviting Team Members

Only OWNER or ADMIN can send invitations.
1

Go to Organization Settings

Navigate to your organization settings page
2

Select Invitations

Find the Invitations section
3

Create Invitation

Enter the member’s email, select organization role, and (optionally) project and project role
4

Send

System sends invitation email to member
5

Member Accepts

Member receives email and accepts invitation to join

​
How Invitations Work

  1. OWNER/ADMIN creates invitation → Email sent
  2. Member receives email with unique link
  3. Member clicks link, signs up (if new) or signs in
  4. Member sees pending invitations in their account
  5. Member accepts or declines
  6. On accept: Member joins organization and project
🔗 More details: See Sign In & Sign Up

​
Viewing Organization Members

In Organization Settings:
  • See all members and their roles
  • Invite new members
  • Remove members (OWNER/ADMIN only)
  • Change member roles (OWNER/ADMIN only)

​
Project Creation & Management

​
Creating a Project

OWNER or ADMIN can create projects.
1

Go to Projects

Navigate to the Projects section of your organization
2

Create New

Click “Create Project” or “New Project”
3

Enter Details

Provide project name and description
4

Set Permissions

Choose which members can access this project and their roles
5

Create

Project is created and ready to use

​
Project Settings

Inside each project, you can configure:
  • Project Name & Description - Basic info
  • Members & Roles - Who has access and what they can do
  • Credentials - Store API keys and secrets used by agents/tools
  • Settings - Project-specific configuration

​
Understanding Access Control

​
Example: Three-Level Permission System

Organization level:
  • Alice: OWNER
    • Can: Manage all, create projects, invite members
    • Sees: Everything in the organization
  • Bob: ADMIN
    • Can: Manage projects, invite members
    • Sees: Everything in the organization
  • Charlie: VIEWER
    • Can: View resources only
    • Sees: Only projects they’re invited to
Project “Support” level:
  • Alice (inherited OWNER access)
    • Can: Edit, delete, manage project settings
  • Bob (inherited ADMIN access)
    • Can: Edit, delete, manage project settings
  • Charlie (inherited VIEWER)
    • Can: View agents and results only
  • Diana: MEMBER (added at project level)
    • Can: Create and edit agents, run workflows

​
Permission Inheritance

  • Organization OWNER has full access to all projects
  • Organization ADMIN has full access to all projects
  • Organization MEMBER has read-only access to projects they’re in
  • Organization VIEWER has read-only access to projects they’re in
  • Project OWNER has full access to all project features
  • Project ADMIN has full access to all project features
  • Project MEMBER can create and edit resources in that project
  • Project VIEWER can only read resources in that project

​
Best Practices

One Org Per Entity

Create one organization per company/team/client to keep everything organized

Multiple Projects by Use Case

Group related work into separate projects (e.g., Support, Analytics, Automations)

Principle of Least Privilege

Grant only the minimum role needed. Use VIEWER as default, MEMBER when needed.

Regular Audits

Periodically review who has access to what and remove unused members.

​
Scenario: Sales Team Structure

​
Troubleshooting

You may not be a member of those projects. Ask an OWNER or ADMIN to invite you.
Only OWNER or ADMIN roles can invite. Ask your organization OWNER or ADMIN.
Ask an OWNER or ADMIN to remove you from the project. They can do this in Project Settings.
Go to Organization Settings or Project Settings → Members → Select the member → Change role. Only OWNER/ADMIN can do this.
All agents, tools, datasources, and workflows in that project are permanently deleted. This cannot be undone. Only OWNER can delete projects.

​
Key Takeaways

✅ Organizations - Team containers (one per company/entity)
✅ Projects - Isolated workspaces (multiple per organization)
✅ Roles - Control access (OWNER, ADMIN, VIEWER at org level; MEMBER, VIEWER at project level)
✅ Invitations - How members join (email-based)
✅ Access Control - Hierarchical (org roles flow down to projects)

​
Next Steps