Curator role irt metamodel not fully described (and besides that is the current situation an issue)

[HenriHeijltjes]

The documentation states below "Prerequisites": "Data Curator role on the collection where the data asset is housed. ..." This is not the way it currently works...

To create and modify asset types --> You need Data Curator role on a collection. So this can be a collection of a (sub)department or (sub)domain.

To create and modify assets --> You need Data Curator role on the root collection (=Purview account level). When you create an asset it will be created in the root and you can't assign it to a (sub)collection. However when you edit the asset, there is an option to move it to a collection.

Note 1: It is strange that when you are curator for a subcollection, you can change the structure (asset types) of the metamodel of the whole Purview instance.

Note 2: It is strange that when you are curator for a subcollection, you can't add content (assets) to the metamodel for your collection. However if somebody with root curator rights does it for you and moves it to your collection, then you can modify it there.

So both the documentation about roles is not covering the current situation as that the current situation can't be how it is supposed to work.

Best regards, Henri Heijltjes

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 41ca0411-e2e8-2f7a-37c2-42039ba2d552
• Version Independent ID: 2f8c8cd7-c893-55a1-2355-66eaa5c926e1
• Content: Manage assets with metamodel - Microsoft Purview
• Content Source: articles/purview/how-to-metamodel.md
• Service: purview
• Sub-service: purview-data-map
• GitHub Login: @evangelinew
• Microsoft Alias: evwhite

[RamanathanChinnappan-MSFT]

@HenriHeijltjes

Thanks for your feedback! We will investigate and update as appropriate.

[whhender]

@HenriHeijltjes - Hmm, it's my understand that you should only need curator on one collection, but I'm going to investigate further and let you know. Thank you.

[whhender]

@HenriHeijltjes - Thanks for your patience-- I've had some time to investigate. The way you've described it is exactly the way it works right now, but isn't the way it's supposed to work in the end. Since this is a preview feature we're in an 'in-between' right now, that adds some functionality, but not all, and results in the permissions configuration you've explained.

We expect to update to the complete model this spring.

In the mean time, I'm updating the documentation to match the current scenario.

[whhender]

@HenriHeijltjes - I've got that updated! You should see it reflected in the docs by later this afternoon.

Thank you again for reaching out! Very much appreciated.

please-close