Transferring Resources
Transfer agents, knowledge bases, and content sources between your personal account and organization accounts — or between organizations. Seclai automatically resolves dependencies, previews the impact, and moves everything in a single transaction.
Overview
Resource transfers let you:
- Move agents to an organization — Share a personal agent with your team
- Consolidate resources — Combine content from multiple accounts into one
- Restructure ownership — Move resources between organizations as your team structure evolves
- Onboard new teams — Transfer a set of pre-built agents and knowledge bases to a new organization
Transfers are atomic — either everything succeeds, or nothing changes. This ensures your resources are never left in an inconsistent state.
What Can Be Transferred
Three resource types can be transferred:
| Resource Type | Description | Common Scenarios |
|---|---|---|
| Agent | AI workflow with steps, triggers, and configuration | Sharing a production agent with a team |
| Knowledge Base | Collection of indexed content with embeddings | Consolidating knowledge across organizations |
| Content Source | RSS feed, website, file upload, or custom index connection | Moving a source to a different team's knowledge base |
Resources are transferred with their full configuration, including all settings, steps, triggers, and connections.
Automatic Dependency Resolution
Resources in Seclai are interconnected:
Agent → Knowledge Base (via triggers) → Content Source (via connections)
When you transfer a resource, Seclai automatically identifies and includes its dependencies:
| You Transfer | Automatically Included |
|---|---|
| Agent | Knowledge bases referenced by triggers, and their content sources |
| Knowledge Base | Content sources connected to the knowledge base |
| Content Source | Just the content source (no upstream dependencies) |
Example: If you transfer an agent named "Daily Digest" that has a content trigger connected to a knowledge base "News Feed", which in turn has two RSS feed sources:
Selected: Agent "Daily Digest"
Included: Knowledge Base "News Feed" (dependency of agent trigger)
Included: Source "TechCrunch RSS" (dependency of knowledge base)
Included: Source "Hacker News RSS" (dependency of knowledge base)
All four resources are transferred together to maintain the agent's functionality.
Transfer Workflow
Transfers follow a three-step process, all within a modal dialog:
Step 1: Select Target Account
Choose the destination account from a dropdown of eligible targets.
Eligible targets include:
- Your personal account (if transferring from an organization)
- Organizations where you have admin or owner access
The dropdown is searchable — type to filter accounts by name.
Example target list:
| Account | Type |
|---|---|
| Kim's Personal Account | Personal |
| Acme Corp | Organization |
| Research Team | Organization |
| Client Project Alpha | Organization |
Step 2: Preview Transfer
After selecting a target, Seclai automatically generates a preview showing exactly what will happen. The preview loads immediately and updates if you change the target account.
The preview contains up to five sections:
| Section | Color | Description |
|---|---|---|
| Will be transferred | Default | Resources that will move to the target account |
| Dependencies included | Blue (info) | Auto-included items not originally selected |
| Access changes | Orange (warning) | Changes in who can access the resources |
| Side effects | Yellow | Impacts on resources that stay behind |
| Cannot transfer | Red (error) | Blockers that prevent the transfer |
Step 3: Execute Transfer
After reviewing the preview:
- Click Transfer to execute the transfer
- Click Cancel to abort without changes
The Transfer button is disabled if any blockers exist (see Transfer Blockers below).
During execution, a loading indicator shows the transfer is in progress. Once complete, the modal closes and the page updates to reflect the changes.
Preview Details
Will Be Transferred
Lists every resource that will move, grouped by type:
- Agents — Each agent with its name
- Knowledge Bases — Each knowledge base with its name
- Content Sources — Each source connection with its name
Items you explicitly selected show as "user-selected." Dependencies show with a reason explaining why they're included (e.g., "Referenced by trigger on agent 'Daily Digest'").
Dependencies Included
An informational alert lists resources that weren't originally selected but are automatically included to maintain functionality. Each entry explains the dependency chain:
Example:
ℹ️ Dependencies included
Knowledge Base "Product Docs"
→ Required by content trigger on Agent "FAQ Bot"
Content Source "Docs Website"
→ Connected to Knowledge Base "Product Docs"
Access Changes
A warning alert highlights changes in resource access:
Example:
⚠️ Access changes
Agent "Internal Reporter" will no longer be accessible to
members of "Engineering Team" organization.
Knowledge Base "Shared KB" will become accessible to all
members of "Marketing Team" organization.
Transfer Blockers
Blockers are issues that prevent the transfer from executing. The Transfer button is disabled until all blockers are resolved.
Common blockers:
| Blocker | Cause | Resolution |
|---|---|---|
| Name conflict | A resource with the same name already exists in the target account | Rename the resource in either account before transferring |
| Insufficient permissions | You don't have admin/owner access on the target account | Request elevated access or choose a different target |
Example blocker:
🚫 Cannot transfer
Agent "Daily Report"
→ An agent named "Daily Report" already exists in "Acme Corp"
→ Rename one of the agents before transferring
Side Effects
Side effects are impacts on resources that stay in the source account. They don't block the transfer but should be reviewed carefully.
Common side effects:
| Side Effect | Description |
|---|---|
| Severed knowledge base connection | A knowledge base in the source account loses a content source that's being transferred |
| Broken agent trigger | An agent in the source account has a trigger referencing a knowledge base that's being transferred |
| Reduced content | A knowledge base loses indexed content because its source moved to a different account |
Example side effects:
⚠️ Side effects
Knowledge Base "General Knowledge" (staying in source account)
→ Will lose connection to Content Source "Tech Blog RSS"
which is being transferred
Agent "Weekly Summary" (staying in source account)
→ Trigger references Knowledge Base "Research Papers"
which is being transferred — trigger will stop working
Each side effect includes a link to the affected resource so you can review and adjust after transfer.
Permissions
| Requirement | Details |
|---|---|
| Source account | You must have admin or owner role |
| Target account | You must have admin or owner role |
| Personal account | You are always the owner of your personal account |
Users with viewer or editor roles cannot initiate or execute transfers.
Examples
Sharing a Personal Agent with Your Team
You've built and tested an agent in your personal account and want to make it available to your organization.
Scenario:
- Agent: "Customer FAQ Bot" (personal account)
- Knowledge base: "Support Docs" (personal account)
- Content sources: "Help Center RSS", "Changelog Feed" (personal account)
- Target: "Acme Corp" organization
Steps:
- Open the agent and click Transfer
- Select "Acme Corp" as the target
- Preview shows:
Will be transferred: Agent "Customer FAQ Bot" (selected) Knowledge Base "Support Docs" (dependency) Source "Help Center RSS" (dependency) Source "Changelog Feed" (dependency) - Click Transfer
- All four resources now belong to "Acme Corp" and are accessible to team members
Moving a Content Source Between Organizations
Your marketing team no longer needs a content source, and the product team wants it.
Scenario:
- Source: "Industry News RSS" (Marketing Org)
- Target: "Product Team" organization
Steps:
-
Open the source → click Transfer
-
Select "Product Team"
-
Preview shows:
Will be transferred: Source "Industry News RSS" (selected) ⚠️ Side effects: Knowledge Base "Marketing Intel" (staying in Marketing Org) → Will lose connection to "Industry News RSS" -
Review the side effect — Marketing's knowledge base will no longer receive updates from this source
-
Click Transfer if acceptable
-
In "Product Team," add the source to the appropriate knowledge base
Consolidating Knowledge Bases
Multiple teams have built separate knowledge bases from the same domain. You want to bring them under one account.
Steps:
- Transfer each knowledge base one at a time to the target organization
- Each transfer automatically includes the knowledge base's content sources
- Review side effects for agents in the source accounts that reference the transferred knowledge bases
- Update or transfer those agents as needed
Handling Transfer Blockers
You try to transfer an agent named "Daily Report" to an organization that already has an agent with that name.
Steps:
- Open the agent → click Transfer
- Select the target organization
- Preview shows:
🚫 Cannot transfer: Agent "Daily Report" → Name conflict: an agent named "Daily Report" already exists in "Acme Corp" - The Transfer button is disabled
- Resolution: Rename your agent (e.g., "Daily Report - v2") or rename the existing agent in the target account
- Re-open the transfer dialog — the blocker is cleared and you can proceed
Best Practices
| Practice | Why |
|---|---|
| Always review the preview carefully | Side effects and access changes can impact production workflows |
| Transfer during low-traffic periods | Minimizes impact on running agents and active knowledge bases |
| Check agent triggers after transfer | Ensure triggers still reference the correct knowledge bases |
| Communicate with your team | Let team members know about ownership changes, especially for shared resources |
| Transfer dependencies together | While Seclai auto-includes dependencies, review the full set to ensure nothing is missing |
| Resolve blockers before attempting | Pre-check for name conflicts by reviewing resources in the target account |
| Test agents after transfer | Run a manual test to verify the agent works correctly in its new account |
Troubleshooting
| Issue | Cause | Solution |
|---|---|---|
| No eligible target accounts | You don't have admin/owner access to any other account | Request admin access to an organization, or create a new organization |
| Transfer button disabled | Blockers exist in the preview | Resolve all blockers (e.g., rename conflicting resources) |
| Agent doesn't work after transfer | Trigger references were not updated | Check agent triggers and reconnect knowledge bases if needed |
| Missing content after transfer | Content source was not included | Verify all content sources were transferred; re-add any missing connections |
| "Access denied" error | Insufficient permissions on source or target account | You need admin or owner role on both accounts |
| Side effects impacted production | A resource in the source account lost a dependency | Review side effects in the preview before executing; re-create connections as needed |
Next Steps
- Organizations — Manage organizations and team access
- Agents — Learn about creating and managing agents
- Knowledge Bases — Organize content for your agents
- Content Sources — Configure content sources for knowledge bases