looking for the best practice when using linked assets
in dev tenant, i have one folder with my common assets
i link the relevant assets to new folder
when created and publishing a solution to next tenant, whats the best practice:
- not include the linked assets, and link them directly from new solution folder after deployment
- include the liked assets in the solution so they will appear as regular assets in the newly deployed solution folder
mind you i have three tenants so i want a standard approach
The best practice for a 3-tenant setup is to not include/link them from the shared folder, but rather create/include them directly as physical assets in the new solution folder.
Prevents broken references: Moving linked assets across independent environments (Dev $\rightarrow$ Test $\rightarrow$ Prod) often breaks folder links and parent-child dependencies.
Environment independence: Target environments (especially Prod) should be self-contained so your packages don’t rely on a shared structure that might differ across tenants.
Keep your common folder for local Dev testing, but let each tenant solution manage its own local assets upon deployment!
Create a Shared/Common Assets folder in each tenant (same folder name across DEV, UAT, PROD).
Keep common assets (credentials, API keys, URLs, etc.) in that shared folder.
Don’t include linked assets in the solution package. After deploying the solution, link the shared assets to the solution folder in the target tenant. This keeps a single source of truth and avoids duplicate assets.
Why this is the better approach:
No duplicate assets across folders.
Asset values remain environment-specific in each tenant.
Easier maintenance—update the shared asset once and all linked folders use it. UiPath officially supports asset linking for sharing common assets across folders.
Use linked asset when the same asset is required by multiple automations/solutions.
For example, a Client Secret ID, API configuration, application URL, or shared configuration used by several automations can be maintained as a common asset.
Keep these common assets in a dedicated Common/Shared Assets folder for each environment.
The Support/Operations team should own and maintain these assets.
Developers and automation users should have permission to use/read the asset as required, but not modify the value.
Maintain the same asset names across Dev, UAT and Prod, while the actual values can be environment-specific.
For an asset used by only one automation, it can be kept within the respective solution or folder instead of the Common Assets folder.
as per your case its better you do not include those assets in solution and link them later to the main folder or common folder which helps in reducing maintenance overhead
Since these are common assets used across solutions, I would keep one actual/common asset in each tenant and avoid creating duplicate physical assets inside every solution folder.
For DEV, UAT and PROD, maintain the same Common/Shared Assets structure, with the values specific to that environment. When deploying the Solution, include the asset as a component/dependency and use Customize → Link to existing to map it to the corresponding common asset in the target tenant.
This is better than deploying another copy of the asset or manually fixing the links after every deployment. UiPath Solutions supports linking an Asset component to an existing resource specifically to avoid duplication.
So the pattern would be: Common Asset in each tenant → Solution deployment → Link to existing asset.
For assets that belong only to one solution, I would keep them as normal assets within that solution.
One thing to keep in mind: normal Orchestrator asset sharing between folders supports assets with global values; assets with account-specific values cannot be shared between folders.
This gives you a consistent setup across all three tenants without maintaining duplicate common assets.