Organization & Member Management
An RBAC-based permission management solution
What Is Organization and Member Management?
MaiAgent's organization and member management feature is like building a "digital office" for your enterprise. Through this feature, you can set up company structures, assign employee positions, configure who can do what, and make team collaboration more organized.
This system is based on RBAC (Role-Based Access Control), providing a complete organization management solution that enables enterprises to effectively organize teams, assign permissions, and monitor resource usage.
What is RBAC?
RBAC is a management approach that "defines positions first, then adds people to positions." For example, you first define what the "Customer Service Agent" role can do, then add Mr. Zhang and Ms. Li to that role. They automatically receive all customer service agent permissions without needing individual configuration for each person.
System Architecture
Three-Tier Structure
MaiAgent uses a clear three-tier architecture: Organization → Role → Member
Organization
└─ Your Company
│
├─ Role
│ └─ Position/Department (e.g., Customer Service, Marketing)
│ │
│ └─ Member
│ └─ Employee (e.g., Mr. Zhang, Ms. Li)Simple explanation:
Organization = Your company
Role = Departments or positions within the company (e.g., Customer Service, Marketing)
Member = Company employees (e.g., Mr. Zhang, Ms. Li)
How It Works
Setup Steps:
Create an organization: Set up your company in the system
Create roles: Create departments or positions within the organization (e.g., Customer Service, Marketing)
Set permissions: Configure what each role can do (determine feature permissions)
Assign members: Add employees to their corresponding roles
Automatically effective: Members automatically receive all permissions for their role
Core Concepts
Organization
The Organization is the top-level management unit, representing your company or team. Each organization has independent members, roles, permissions, and resources.
Simple explanation: An organization is like a "company." Each company has its own employees (members), departments (roles), and data (AI assistants, knowledge bases, etc.).
Role
A Role is a functional unit within the organization that defines a set of permissions and resources.
Three role types:
Owner Role: Highest permissions, can manage all settings
Default Role: Basic permissions automatically held by all members
Custom Role: Department or position roles created based on needs
Simple explanation: A role is like a company "department" or "position" (e.g., Customer Service, Marketing, Manager). Each role has different responsibilities and permissions.
Member
A Member is a user within the organization who gains permissions through roles.
Member types:
Owner
The organization creator or a member designated as owner
Has full access to all resources Can manage organization settings and role permissions
Regular Member
A member within a role
Has the permissions and resources of assigned roles, such as Q&A, conversation permissions, etc.
Simple explanation:
Owner = The company's general manager or system administrator who can manage everything
Regular Member = A company employee with different permissions based on their department (role)
Permission
Permissions control which features a member can use.
MaiAgent uses a hierarchical permission architecture:
What is a "hierarchical permission architecture"?
It is like a folder structure:
Main permission = Main folder (e.g., "AI Features")
Sub-permission = Subfolder (e.g., "AI Assistants," "Knowledge Bases," "Crawlers")
How it works:
Checking a main permission automatically includes all sub-permissions
You can also check only specific sub-permissions for more granular control
Resource
A Resource is a concrete item within the organization that can be assigned to specific roles.
Resource types:
AI Assistants: Specify which AI assistants a role can operate
Knowledge Bases: Specify which knowledge bases a role can access
Conversation Platforms: Specify which conversation platforms a role can use
Setup Workflow Guide
Recommended Setup Order
Follow this order to avoid confusion:
✅ Create an organization: Set up your company organization first
✅ Create roles: Create the necessary departments or positions within the organization
✅ Set permissions: Configure feature permissions for each role
✅ Assign resources: Specify which AI assistants, knowledge bases each role can use
✅ Add members: Add employees to the organization
✅ Assign roles: Assign members to their corresponding roles
Related Pages
Next, you can refer to the following detailed guides based on your needs:
Organization Management: How to create, switch, and manage organizations
Role Permission Management: How to create roles, set permissions, and assign resources
Member Management: How to add and remove members, and assign roles
Design Advantages
Only members within your organization can view and manage all AI assistant-related features under that organization.
This design provides:
Clear structure: Organization → Role → Member, a three-tier architecture that is easy to understand
Flexible permissions: Different permission combinations can be individually configured for each role
Centralized management: The organization owner manages all settings uniformly
Member flexibility: A single member can belong to multiple roles simultaneously, participating in different projects or teams
Real-time visibility: Provides real-time information on the organization's operational status
Resource control: Ensures effective management of resource usage
Last updated
Was this helpful?