You are now changing the topic of the original question. Next time please create a new question for a new topic.
The duties you mentioned are part of the role Data Management Migration User. A person with this role usually has access to all data entities that is needed to perform data migration tasks.
In case your new data entities are intended to be part of migrations, I would create a new duty and add it to the role DataManagementMigrationIUser as menu extension. In case your entities are not related to data migration, you can skip this.
is it a good practice to add each privilege i create to the standard duties like
DataManagementApplicationMasterEntitiesView
DataManagementApplicationParametersEntitiesView
...etc
i mean if my "entity category" is Master, does that mean i should add it to this duty DataManagementApplicationMasterEntitiesView? and what would happen if i don't?
Without a privilege, normal business users will not be able to read the contents of the data entity. So yes, you need the read privilege.
There is no impact if you keep the maintain privilege. It might be only confusing for people who are not aware that the entity itself is read-only and they can't import data. Personally, I consider it an obsolete privilege.
If you have a read-only data entity, you will not need a privilege for 'Maintain'. The wizard is not aware of the properties you will set later. In this case, you can delete the maintain privilege. There is a best practice check that will check for at least one privilege, not a difference between read and maintain.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.