Configuration and administration
Organizations and projects
Manage team members, projects, and access permissions through organizations.
Guide · Module: organization · Administrators · Deployment: Not specified · Confirmed product versions: Not specified · Source: Existing documentation
An organization manages team members, projects, and enterprise login in one place. Each project belongs to exactly one organization and manages its own data sources, Agents, conversations, and analysis canvases. A Cloud account can join multiple organizations; a private deployment uses one fixed organization.
Cloud and private deployment
| Capability | Cloud | Private deployment |
|---|---|---|
| Number of organizations | Create or join multiple organizations | One default organization |
| Organization roles | Owner, Admin, Member, Guest, Billing Admin | Owner, Admin, Member |
| Organization switching | Supported | Not needed |
| Plans and usage | Manage Cloud plans and credits per organization | Authorized through an enterprise license; Cloud usage page is not shown |
| WeCom and WPS | Configured independently by each organization | Configured in the default organization |
On Cloud, the same account can own at most one Free organization at a time. Before creating another, follow the page's instructions to handle the existing organization's plan.
Open organization management
Open Profile from the personal card at the lower left, then use the Organization group in the personal settings sidebar:
- Organization settings: change the organization name and view the plan or private deployment license;
- Project management: create and manage projects, and control whether members can create projects;
- Member management: invite members, change organization roles, disable members, and transfer ownership;
- Enterprise integrations: connect WeCom or WPS and import members allowed to log in;
- Usage: view organization consumption on Cloud.
Owners and Admins can manage these organization resources. Billing Admins see only plan-related information and usage. See Members and roles for full permissions.
Cloud users can switch organizations from the personal card; the project list and current project change with the organization. If you have not joined an organization, follow the guide to create one, accept an in-app invitation, or open an invitation link. Private deployments have no organization switching menu but still use Profile to open organization management.
Public and private projects
- Public projects are accessible to active Owners, Admins, and Members in the current organization through the project's default Admin or Member permissions.
- Private projects require explicit project membership for access.
- Cloud Guests do not inherit public project permissions and must have an explicit project role. Billing Admins do not participate in project collaboration.
“Public” means open to regular members of this organization, not to the internet. Explicit project roles take precedence over defaults: they can promote someone to administrator or restrict them to member. After an explicit role is removed, access is evaluated using the public project's default permissions again.
Owners and Admins can create projects. Whether Members can do so depends on the “Allow members to create projects” switch in Organization → Project management.
Management rights and content access
Organization Owners/Admins can manage projects in their organization, but this does not automatically grant access to private project content. Viewing conversations and canvases still requires an effective project role: creators can access their own content, while project owners and administrators can access all content in the project. Sharing links control access separately and do not add visitors to an organization or project; they also stop working if the organization is suspended or deleted.
System administrator is a separate deployment management identity. Cloud system administrators have global governance and project content management capabilities. Private deployment system administrators retain global users, the project directory, and runtime configuration entries, but the project directory does not automatically grant access to project content. See Organizations, projects, and operations for the relevant entries.