Admin Access to Other User Views
Hey AYON Team, As an admin, I’d find it extremely useful to have the ability to temporarily view and use AYON as another user — without needing their credentials. This would help with: Troubleshooting user-specific issues (permissions, UI visibility, task access, etc.) Testing role-based workflows Supporting users during onboarding or training Basically, a “switch user” or “impersonate user” mode that lets admins see exactly what a specific user sees. Is something like this planned or already possible?
mahesh kyadari
Feature requests
Admin Access to Other User Views
Hey AYON Team, As an admin, I’d find it extremely useful to have the ability to temporarily view and use AYON as another user — without needing their credentials. This would help with: Troubleshooting user-specific issues (permissions, UI visibility, task access, etc.) Testing role-based workflows Supporting users during onboarding or training Basically, a “switch user” or “impersonate user” mode that lets admins see exactly what a specific user sees. Is something like this planned or already possible?
mahesh kyadari
Feature requests
Support Tags in settings filters
In many places in different addon settings, we can filter profiles by task names and types like in OCIO config profiles. Which can be intuitive as it expects naming the tasks in a particular way. In contrast, we already have tags that we can define for our project in the project anatomy. I think it’d be much easier to have tags in these profile filters. That way, we won’t need to worry about the task name or type, and it will also appear very explicitly on the overview page. Tags are colored, making them easy to identify visually in the overview page. Note this is a mockup to visualize the idea. Also, note the backend server doesn’t support tags_enum in compliance totask_types_enum. The example above shows the OCIO config profiles but this can be also used in application filters and tools. Disclaimer: I’m not sure if this request deviates from the original intended usage of Tags.
Mustafa Zaky Jafar
Pipeline
Feature requests
Support Tags in settings filters
In many places in different addon settings, we can filter profiles by task names and types like in OCIO config profiles. Which can be intuitive as it expects naming the tasks in a particular way. In contrast, we already have tags that we can define for our project in the project anatomy. I think it’d be much easier to have tags in these profile filters. That way, we won’t need to worry about the task name or type, and it will also appear very explicitly on the overview page. Tags are colored, making them easy to identify visually in the overview page. Note this is a mockup to visualize the idea. Also, note the backend server doesn’t support tags_enum in compliance totask_types_enum. The example above shows the OCIO config profiles but this can be also used in application filters and tools. Disclaimer: I’m not sure if this request deviates from the original intended usage of Tags.
Mustafa Zaky Jafar
Pipeline
Feature requests
Up Next
Add tasks and folders to existing review sessions
Currently you can only add versions to review sessions but this isn’t very intuitive. Because you can create a review session from a task or folder you should also be able to add task/folder versions to a session. As with creating new sessions, the version to be added would be the latest published version.
Luke Inderwick
Production
Feature requests
Up Next
Add tasks and folders to existing review sessions
Currently you can only add versions to review sessions but this isn’t very intuitive. Because you can create a review session from a task or folder you should also be able to add task/folder versions to a session. As with creating new sessions, the version to be added would be the latest published version.
Luke Inderwick
Production
Feature requests
Python API Access for AYON Lists
Users require the ability to programmatically access and manage AYON Lists via the AYON Python API. This includes functionalities such as creating, reading, updating, and deleting lists, as well as adding and removing items from existing lists. This feature would enable greater automation and integration capabilities for project organization and data management within AYON.
mahesh kyadari
Pipeline
Feature requests
Python API Access for AYON Lists
Users require the ability to programmatically access and manage AYON Lists via the AYON Python API. This includes functionalities such as creating, reading, updating, and deleting lists, as well as adding and removing items from existing lists. This feature would enable greater automation and integration capabilities for project organization and data management within AYON.
mahesh kyadari
Pipeline
Feature requests
Enhance Documentation for Command-Line Program Arguments and Post-Launch Commands
Provide comprehensive documentation on how to configure command-line program arguments within AYON, specifically including methods for executing additional commands or scripts immediately after the program launches. This would cover various scenarios and provide clear examples for users.
Quentin Roux
Pipeline
Feature requests
Enhance Documentation for Command-Line Program Arguments and Post-Launch Commands
Provide comprehensive documentation on how to configure command-line program arguments within AYON, specifically including methods for executing additional commands or scripts immediately after the program launches. This would cover various scenarios and provide clear examples for users.
Quentin Roux
Pipeline
Feature requests
Add Syntheyes DCC to list of supported applications.
I want to propose adding Syntheyes to the list of supported applications.
Fred Pienkos
Feature requests
Add Syntheyes DCC to list of supported applications.
I want to propose adding Syntheyes to the list of supported applications.
Fred Pienkos
Feature requests
Watch more entity changes
The ability to get notifications about more changes on an entity and the possibility to select which changes you want to get notified about. Tags Changes Attributes changes
Luke Inderwick
Production
Feature requests
Watch more entity changes
The ability to get notifications about more changes on an entity and the possibility to select which changes you want to get notified about. Tags Changes Attributes changes
Luke Inderwick
Production
Feature requests
In Progress
AYON workflow orchestration
We need a framework for creating larger automations across DCCs and pipeline tools, which is not dependent on third party tools like render managers, but can offload work to them when needed.
Milan Kolar
Feature requests
In Progress
AYON workflow orchestration
We need a framework for creating larger automations across DCCs and pipeline tools, which is not dependent on third party tools like render managers, but can offload work to them when needed.
Milan Kolar
Feature requests
Planned
Column highlighting for important fields
The ability in the table to specify important columns to highlight and show more prominently.
Luke Inderwick
Production
Feature requests
Planned
Column highlighting for important fields
The ability in the table to specify important columns to highlight and show more prominently.
Luke Inderwick
Production
Feature requests
Houdini: Register Custom HDAs as loaders
Loader HDAs are highly versatile and can be integrated as foundation for building custom Loader HDAs. Therefore, studios may extend them and come up with differnet loader HDAs that works for their pipeline. It’d be amazing to add another feature in Houdini addon where you can register your custom HDA as loader plugin so that artists can use it via this right menu.
Roy Nieterau
Pipeline
Feature requests
Houdini: Register Custom HDAs as loaders
Loader HDAs are highly versatile and can be integrated as foundation for building custom Loader HDAs. Therefore, studios may extend them and come up with differnet loader HDAs that works for their pipeline. It’d be amazing to add another feature in Houdini addon where you can register your custom HDA as loader plugin so that artists can use it via this right menu.
Roy Nieterau
Pipeline
Feature requests
Maya USD: Rig in USD Asset as MayaReference prim
Working within a USD Pipeline usually means you want your animation output for e.g. a rig to be overlaid on top of a loaded USD Asset to merge the animated point data with the model and look of the asset, usually for use by downstream lighting department. The USD reference usually provides: - asset (referenced usd asset) - geo - mtl The output data from a rig should then be overlaid over the /asset/geo path in the shot to move the character around. Currently, publishing an animation from a rig usually means completely separate Alembic or USD data that would need to somehow be identified to get overlaid over a particular USD asset structure in a shot. What if we could load an asset, and it itself, has a reference to the rig embedded? How would you imagine the implementation of the feature? Maya USD allows to embed maya scene files (mayaAscii or mayaBinary) to be included into USD as a MayaReference prim referencing the file. When a Maya USD Proxy finds such a prim it can enable the prim as a regular maya reference to load the native maya data, like for example a rig file. I'd like to propose to - whenever publishing a rig from Maya to write out a USD Asset Contribution where an extra layer gets added to the USD asset representing the rig as a reference. Basically someone (e.g. either in Maya or Houdini) lays out assets in a scene, by loading the asset USD. If that asset now contains the MayaReference prim (which can be loaded fine in Houdini; just the internal data of the maya scene couldn't be loaded) then in Maya one could now enable that reference inside the USD Asset to load the actual rig. So assets laid out in any USD supporting host could in Maya be switched to their rig for animating. Nice! In essence we'd need: On publishing a Maya rig, create a USD asset contribution that references in this rig version in a USD layer On Maya, when the Maya USD reference rig is loaded (and its detected its loaded within USD asset) then publish the animation cache as USD that gets added as a variant on the loaded asset in the shot's anim layer. That way, the animator in Maya can just read a USD Layout with loaded assets, enable the reference, animate and publish. Plus side to this would be, that when they've published their animation to the shot's layers they can also disable their reference and switch it over it to the published cache (since it's also a USD contribution). Meaning they can use the cached USD data as proxy in their scene whilst maybe e.g. continuing to animate on another character. Originally posted on GitHub: AY-6685_Maya USD: Rig in USD Asset as MayaReference prim #10
Roy Nieterau
Production
Feature requests
Maya USD: Rig in USD Asset as MayaReference prim
Working within a USD Pipeline usually means you want your animation output for e.g. a rig to be overlaid on top of a loaded USD Asset to merge the animated point data with the model and look of the asset, usually for use by downstream lighting department. The USD reference usually provides: - asset (referenced usd asset) - geo - mtl The output data from a rig should then be overlaid over the /asset/geo path in the shot to move the character around. Currently, publishing an animation from a rig usually means completely separate Alembic or USD data that would need to somehow be identified to get overlaid over a particular USD asset structure in a shot. What if we could load an asset, and it itself, has a reference to the rig embedded? How would you imagine the implementation of the feature? Maya USD allows to embed maya scene files (mayaAscii or mayaBinary) to be included into USD as a MayaReference prim referencing the file. When a Maya USD Proxy finds such a prim it can enable the prim as a regular maya reference to load the native maya data, like for example a rig file. I'd like to propose to - whenever publishing a rig from Maya to write out a USD Asset Contribution where an extra layer gets added to the USD asset representing the rig as a reference. Basically someone (e.g. either in Maya or Houdini) lays out assets in a scene, by loading the asset USD. If that asset now contains the MayaReference prim (which can be loaded fine in Houdini; just the internal data of the maya scene couldn't be loaded) then in Maya one could now enable that reference inside the USD Asset to load the actual rig. So assets laid out in any USD supporting host could in Maya be switched to their rig for animating. Nice! In essence we'd need: On publishing a Maya rig, create a USD asset contribution that references in this rig version in a USD layer On Maya, when the Maya USD reference rig is loaded (and its detected its loaded within USD asset) then publish the animation cache as USD that gets added as a variant on the loaded asset in the shot's anim layer. That way, the animator in Maya can just read a USD Layout with loaded assets, enable the reference, animate and publish. Plus side to this would be, that when they've published their animation to the shot's layers they can also disable their reference and switch it over it to the published cache (since it's also a USD contribution). Meaning they can use the cached USD data as proxy in their scene whilst maybe e.g. continuing to animate on another character. Originally posted on GitHub: AY-6685_Maya USD: Rig in USD Asset as MayaReference prim #10
Roy Nieterau
Production
Feature requests
Task Discription in the Launcher
It would be helpful to add a feature in the AYON Launcher that displays the task description. Ideally, users should be able to view a description for each individual task within the launcher interface. Use Case: This would improve task clarity for artists and developers by providing context directly in the launcher, without needing to switch to browser.
Alexey Volynets
Pipeline
Feature requests
Task Discription in the Launcher
It would be helpful to add a feature in the AYON Launcher that displays the task description. Ideally, users should be able to view a description for each individual task within the launcher interface. Use Case: This would improve task clarity for artists and developers by providing context directly in the launcher, without needing to switch to browser.
Alexey Volynets
Pipeline
Feature requests
Filter users by level and license
It would be nice to be able to click on various user level stats in the top bar of user management page and automatically prefill the filter by the value.
Lorenzo Basurto
Feature requests
Filter users by level and license
It would be nice to be able to click on various user level stats in the top bar of user management page and automatically prefill the filter by the value.
Lorenzo Basurto
Feature requests
New workfiles for softwares without addon
I really love the simplicity of the Tray publisher. Any file with any extension can be published and be a part of the pipeline. It would be great to add this simplicity to work files as well (but not using the tray publisher) * Creating addons for every software in every industry will be hard to manage and take very long time. * “Simple” softwares like Excel, Word, Powerpoint, Notepad etc is in need of a simpler approach than addons, since there is simply no way to develop addons for every single software *The simplicity of the tray publisher could be applied to workfiles as well and therefore open up possibilites to add any type of software to the AYON pipeline, also for workfiles. To solve this we need a new feature to create new work files based on pre-existing template files. Maybe this could be done with the interactive web action? Example User creates a new task in overview and with web action the user gets to choose if it wants to create a work file from pre-existing template (For example there might be 5 different Excel templates for different purposes) Once the template is chosen there will be a new workfile created on disk and also a new database entry. For publishing we could still use the tray publisher. This feature would open up a lot of freedom for the user to add softwares that does not have an addon and not necessarily need a fancy pipeline. Problems to solve * Versioning of the workfiles would need to be added somehow. Maybe as a right click feature on the current workfile.
Olle Rydberg
Pipeline
Feature requests
New workfiles for softwares without addon
I really love the simplicity of the Tray publisher. Any file with any extension can be published and be a part of the pipeline. It would be great to add this simplicity to work files as well (but not using the tray publisher) * Creating addons for every software in every industry will be hard to manage and take very long time. * “Simple” softwares like Excel, Word, Powerpoint, Notepad etc is in need of a simpler approach than addons, since there is simply no way to develop addons for every single software *The simplicity of the tray publisher could be applied to workfiles as well and therefore open up possibilites to add any type of software to the AYON pipeline, also for workfiles. To solve this we need a new feature to create new work files based on pre-existing template files. Maybe this could be done with the interactive web action? Example User creates a new task in overview and with web action the user gets to choose if it wants to create a work file from pre-existing template (For example there might be 5 different Excel templates for different purposes) Once the template is chosen there will be a new workfile created on disk and also a new database entry. For publishing we could still use the tray publisher. This feature would open up a lot of freedom for the user to add softwares that does not have an addon and not necessarily need a fancy pipeline. Problems to solve * Versioning of the workfiles would need to be added somehow. Maybe as a right click feature on the current workfile.
Olle Rydberg
Pipeline
Feature requests
Periodic Staging Directory Cleanup
A tool or AYON service to delete staging directories after a set period, such as a 90-day timeout. It can serve as an alternative to automatic deletions managed by cleanup plugins. This is idea was mentioned in some old discussion on discord. Just found it while I was cleaning up my notes.
Mustafa Zaky Jafar
Pipeline
Feature requests
Periodic Staging Directory Cleanup
A tool or AYON service to delete staging directories after a set period, such as a 90-day timeout. It can serve as an alternative to automatic deletions managed by cleanup plugins. This is idea was mentioned in some old discussion on discord. Just found it while I was cleaning up my notes.
Mustafa Zaky Jafar
Pipeline
Feature requests
Set Product Status on Publish
To make it easier for users to set statuses it would be super helpful if the status of a product version could be set when publishing - I am thinking along the lines of two per instance attributes, one to set the status of the new version and the second to change the status of the currently existing version(s). So I want my new version status to be Pending review and the previous versions to be set to Omitted. This will also help with the status filters in the loader which hide versions based on status, so if you want to make sure all previous versions are excluded when Omitted is set to be hidden, all versions have to have their statuses changed manually, which is very tedious :(
Shea
Community
Feature requests
Set Product Status on Publish
To make it easier for users to set statuses it would be super helpful if the status of a product version could be set when publishing - I am thinking along the lines of two per instance attributes, one to set the status of the new version and the second to change the status of the currently existing version(s). So I want my new version status to be Pending review and the previous versions to be set to Omitted. This will also help with the status filters in the loader which hide versions based on status, so if you want to make sure all previous versions are excluded when Omitted is set to be hidden, all versions have to have their statuses changed manually, which is very tedious :(
Shea
Community
Feature requests
Planned
Enable Partial Substring Matching in Overview Tab Search
Hi Ayon team, it would be great if the search functionality in the Overview tab supported partial substring matching—instead of only matching from the beginning of names. For example, if I type "ave" it should return results like "Waavel" where "ave" appears in the middle of the name. This would make searching more flexible and user-friendly, especially when users don’t remember the exact name start.
Marios Bikos
Production
Bugs
Planned
Enable Partial Substring Matching in Overview Tab Search
Hi Ayon team, it would be great if the search functionality in the Overview tab supported partial substring matching—instead of only matching from the beginning of names. For example, if I type "ave" it should return results like "Waavel" where "ave" appears in the middle of the name. This would make searching more flexible and user-friendly, especially when users don’t remember the exact name start.
Marios Bikos
Production
Bugs