Can we prevent creating assettypes which are not in our scope

Question

Hi, We would like to know if it’s possible to prevent creating assettypes that are not part of our scope. Does anyone has experience with this issue? Thanks, Ingrid

daniel · Answer

I haven’t tested this, but you could potentially create a workflow which runs on asset creation and does a check to ensure the type of asset was created by the right group / user? You could then move the asset to a “Quarantine” domain and email the creator / an admin to explain they aren’t supposed to create this asset.

It might cause a bit of a performance hit though, so you would likely want to restrict this to some domains / communities rather than the whole environment.
Otherwise you could also do this in a reactive way, where you manually run a workflow which does the logic to check who created an asset / if they are in the right group. Another reactive way could be to use reporting to discover these, either through the output module or with some global views. You can set up the filter logic to show any assets created by a given group / user that shouldn’t be created by them, and then move these or talk to the owner or review the assets for correctness etc.

Hope this helps!

Venkata Reddy Padala · Answer

Scopes, assignments would work only in UI. If the user improts with excel/ api’s they will not be stopped.
From Excel Import even if an asset type is not assigned to a specific domain type or an attribute type is not assigned to an asset they still will be created without any error.
They are all only controlled in UI.

1	Grant Rollerson SUNCORP CORPORATE SERVICES PTY LTD
2	Tom Friesen Algonquin College
3	SB S Benson Plus3 IT
4	S stefan_busch
5	Brian Lloyd USA TODAY Co.
6	D daverichard