You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an artist working on a project, I don't want to see attributes that are not relevant to it.
Problems
Our attributes are scope to the whole AYON instance making it currently impossible to hide or ignore some of them on projects where they might be irrelevant.
Proposal
We should find a way to add come kind of project scope to attributes. This doesn't need to affect their backend accessibility on project entities, but hiding some attributes on specific projects would be very useful.
Perhaps this could by a simple list in the project anatomy listing available attributes, that would show or hide them per project.
The text was updated successfully, but these errors were encountered:
Do you think this should be controlled on access group level (set in project permissions) or per project for all users regardless their permissions (set in the project anatomy)?
The later is probably easier to implement, but the first is really granular (but possibly confusing for admins)
Story
As an artist working on a project, I don't want to see attributes that are not relevant to it.
Problems
Our attributes are scope to the whole AYON instance making it currently impossible to hide or ignore some of them on projects where they might be irrelevant.
Proposal
We should find a way to add come kind of project scope to attributes. This doesn't need to affect their backend accessibility on project entities, but hiding some attributes on specific projects would be very useful.
Perhaps this could by a simple list in the project anatomy listing available attributes, that would show or hide them per project.
The text was updated successfully, but these errors were encountered: