Documentation
This is doc description
mconnect.ai supports the creation of the following entities, along with their associated knowledge, tools and resources:
Entities
| Entity | Description |
|---|---|
| Organization | An entity that represents a company, department, or group managing multiple teams and users within mconnect.ai. Organizations can exist at the top level or be created under another Organization as a Sub-Organization. |
| Team | A subgroup within an organization or another team, consisting of multiple users collaborating on shared agents, knowledge, and resources. |
| User | An individual account with assigned roles and permissions. Users can be part of an organization or team, but they can also manage their own agents, knowledge and resources independently for personal use. |
Entity Hierarchies
| Entity | Can be created under | Can have sub-entities | Can have knowledge |
|---|---|---|---|
| Organization | N/A (Top-level entity), Organization | Organizations (Sub-Organizations), Teams, Users (as members) | |
| Team | N/A (Top-level entity), Organization, Team | Teams(Sub-Teams), Users (as members) | |
| User | N/A (Standalone) | N/A |
Additional Notes
- Users are independent but can be members of Organizations or Teams
Authorization
By combining role-based permissions for users and teams with feature toggles at different levels of the hierarchy, you can establish a highly controlled and customizable workflow.
Roles & Permissions
| Hierarchy / Role | Admin | Member |
|---|---|---|
| Organization (assigned or inherited roles) | View organization Manage organization members Edit organization settings Delete organization Create organization teams Create organization knowledge Create sub-organizations | View organization Manage organization members Edit organization settings Delete organization Create organization teams Create organization knowledge Create sub-organizations |
| Team (assigned or inherited roles) | View team Manage team members Edit team settings Delete team Create team knowledge Create sub-teams | View team Manage team members Edit team settings Delete team Create team knowledge Create sub-teams |
| Knowledge (assigned or inherited roles) | View knowledge Manage knowledge members Edit knowledge settings Delete knowledge Create versions | View knowledge Manage knowledge members Edit knowledge settings Delete knowledge Create versions |
| Version (inherited roles) | View versions Edit version settings Delete version Manage resources | View versions Edit version settings Delete version Manage resources |
| Resources 1. Data 2. Collections 3. Configurations 4. Services (inherited roles) | Create Edit Delete | Create Edit Delete |
| Tools 1. Endpoints 2. LLMs 3. Skills 4. Agent Cards (inherited roles) | Create Edit Delete | Create Edit Delete |
Notes
- Authorization permissions granted at a higher level in the hierarchy are automatically inherited by all its child entities without requiring explicit assignment.
- mconnect.ai recommends assigning permissions based on necessity. Instead of granting all employees a role at the top level, it is better to assign roles at the appropriate sub-organization, team, or repository level.
- User permissions can be elevated at lower levels in the hierarchy (e.g., from Member → Admin), but downgrading (Admin → Member) at a lower level is not possible.
- In general, any organization, team, repository, or associated resources—such as versions, data, collections, configurations, services, or tools like endpoints, LLMs, skills, and agent cards—marked as public are accessible to all users. However, if a child resource is set to private, it is only visible to users with explicit permissions (e.g., Admin or Member) within the same hierarchy or its parent entities.
- Additionally, if a parent entity is set to private, all its child resources and tools will automatically inherit this visibility status.
Features
mconnect.ai allows enabling or disabling various features at different levels within the hierarchy. Admin can manage these settings from their respective settings pages.
Visibility
| Feature | Description |
|---|---|
| Public | Any organization, team, knowledge, or associated resources—such as versions, data, collections, configurations, services, and tools—marked as public can be accessed by anyone. |
| Private | A resource set to private is only accessible to users with explicit permissions (such as Admin or Member) within the same hierarchy or its parent entities. |
Organization
| Feature | Description |
|---|---|
| Sub-Organizations | Enable or disable sub-organization creation within this organization. |
| Teams | Enable or disable team creation within this organization. |
| Knowledge | Enable or disable knowledge creation within this organization. |
| Agents | Enable or disable agent creation within this organization. |
Team
| Feature | Description |
|---|---|
| Sub-Teams | Enable or disable sub-team creation within this Team. |
| Knowledge | Enable or disable knowledge creation within this Team. |
| Agents | Enable or disable agent creation within this Team. |
Knowledge
| Feature | Description |
|---|---|
| Dependency | Allow this knowledge to be added as dependency in other knowledge. |
Version
| Feature | Description |
|---|---|
| Dependency | Allow this version to be added as dependency in other knowledge. |
Agent
| Feature | Description |
|---|---|
| Anonymous Chat | Allow anonymous chat. |
| Sub Agent | Allow this agent to be added as sub-agent. |
| Auto Approval | Auto approve subscription request. |