App Management
This article covers day-to-day app management in LanSphere: viewing and filtering the app list, card more-actions, permission settings and ownership transfer, the full Project Folder rules, and the per-channel confirmation mechanism when deleting apps. It is for developers, admins, and owners who manage multiple apps.
App List
App modules like “Workflow” and “Agent” show the apps you can see as a card list. Each card contains:
| Item | Description |
|---|---|
| Avatar | The icon uploaded at creation; a system default style if none was uploaded |
| Name | The app name |
| Type | Workflow / Chatflow / Agent |
| Creator | Who created the app |
| Last edited | When the app was last edited and saved |
| Publish status icon | Marks the app’s current publish status |
Filtering and Search
The top of the list provides filtering and search, stackable:
- App type: Filter by Workflow, Chatflow, Agent;
- Publish status: Filter by “Published” / “Draft”;
- Online status: Filter by “Online” / “Offline”;
- Created by Me: Only apps you created;
- Name search: Fuzzy search by app name.
Card More Actions
Click the more-actions entry on an app card for:
- Edit Info: Modify the app’s basic info (name, description, avatar);
- Permissions: Set the app’s visible and editable scope — see “Permission Settings” below;
- Export YML: Export the app configuration as a YML file for backup or migration;
- Duplicate: Copy the app into a new one;
- Delete: Delete the app — see “Deleting Apps” below.
Note: Neither the exported YML nor the duplicate inherits the original app’s publish status or permission configuration. A new duplicate is a pure draft, visible only to you by default — reconfigure permissions and publish before it can serve externally.
Permission Settings
The entry for app permissions: card more-actions → “Permissions”:
- Default permission is “Only me” — only the creator can see and edit;
- Can be opened to “selected team members” — multi-select and select-all supported;
- Members without permission do not see the app in the list; directly visiting the app details page redirects to a 403 page.
Tip: Deleting an app, publishing to Lansenger, and permission settings are limited to resources you created yourself. Authorized members can view and edit the app but cannot perform those owner operations.
Transferring Ownership
When you need to hand an app over to a colleague, transfer ownership in the “Permissions” pop-up:
- Open card more-actions → “Permissions”;
- Choose transfer ownership in the pop-up and pick the recipient from the transferee list;
- Confirm again to complete the transfer.
Transfer rules:
- The transferee list shows only the Developer role and above, and automatically filters out the current user and the original Owner;
- After the secondary confirmation, the original Owner loses all permissions; collaborators and visible scope stay unchanged;
- Apps inside a Project Folder cannot be transferred individually — transfer the whole folder’s ownership instead;
- Ownership of a component published from a Workflow transfers together with the app;
- Transfers are recorded in audit logs.
Project Folder
When the team has many apps, organize them by project with “Project Folders.”
Basic Rules
- A Project Folder is a top-level directory — single level only, no nesting;
- Only the Admin role and above can create one;
- Name required (up to 50 characters); description optional (up to 300 characters);
- Logo uses the system default style;
- Newly created folders are visible only to the creator by default; collaborators can be added.
Collaborators
- Collaborators have edit rights over all apps in the folder, including flow orchestration and basic configuration;
- Collaborators cannot modify the folder’s name or intro.
Moving Existing Apps In
- The original creator moves the existing app into the folder;
- The system pops a secondary confirmation explaining the consequences;
- Confirm to complete the move.
Note: After the move, all folder collaborators can edit the app; the app’s visibility can no longer be modified separately — its permission-settings entry is hidden. Confirm before moving.
Creating Apps Inside a Folder
For an app created inside a folder, the folder’s creator is the owner, and the actual operator is marked as the resource creator.
Deletion, Removal, and Member Management
| Action | Rule |
|---|---|
| Delete an app in the folder | A resource creator can only delete apps they created; the folder owner can delete everything in the folder |
| Move an app out | Only the folder creator or the app’s owner |
| Remove a collaborator | Only the folder creator; the removed person keeps ownership of their own apps |
| Transfer the folder | Only the creator, to someone with the Admin role or above |
Deleting Apps
When deleting an app, the system pops different secondary confirmations by the app’s publishing channels — read carefully before confirming:
| Publish situation | Confirmation prompt and consequence |
|---|---|
| Published as a component | Pop-up: “This app has been published as a tool. Delete anyway?” — apps referencing the component will be affected |
| Published to the App Square | Deleting the app also deletes its data in the App Square |
| Published to Lansenger | Only platform-side data is deleted; Lansenger-side data must be handled separately |
| Published to multiple channels | The system strongly warns you to proceed with caution — confirm each channel’s impact one by one before deleting |
Note: Deletion can only be performed by the app’s creator. Back up the app configuration via “Export YML” before deleting.

