Hi @<1523701205467926528:profile|AgitatedDove14> - yes, that's great! It's much cleaner. I was thinking of tracking the input datasets as artifacts, but the alias method is better.

The user interface still only displays a GUID - it would be much preferrable if it displayed a clickable link which took me to the dataset details page -- particularly since the GUID doesn't search properly.

Fixing that would make this feature great.

Oh, I was more referring to having a clickable link for the dataset, rather than adding the dataset GUID to a search index.

Both fixes would improve things, but making the dataset clickable -- similar to how Input Model is clickable -- would be best.

I think the idea is that end-users should access artifacts via the web interface. And jobs should run with the ClearML agent. Only configure clearml.conf for the user account under which you are running your ClearML Agents, and only on the servers which are running your agents.