Hi Vani

The feature is one way of helping with initial creation of artifacts from an imported document embedded in an artifact - note that unless the document was very well structured/organised I would expect to have to do cleaning up after using this function. This might be simplest if you extract into a module and tidy up there.

There isn't a specific permission to control use of the Extract Requirements from Artifact function - if you don't want a group of users to create artifacts then create a role for them and remove the permission 'Save Artifact'-> 'Create an artifact' - and possibly some other permissions. Or give them a read-only role like the default Everyone role.

Getting initial requirements into a well-organised structure is an important step in getting started on any project, and there are other methods available such as CSV import, direct document import, etc. You need to work out which are the best methods for your situation and ensure your users understand the correct process to use. It's very common to have a sandbox project to allow experimentation away from the production project. Also you should evaluate the various methods in advance, i.e. before you are facing a deadline - that's the worst time to try something for the first time.

Using configuration management will allow you to e.g. try out importing and extracting requirements in a changeset so changes are easily discarded/retried before delivering to the stream you are working in. You should also take a baseline before doing the import (it doesn't cost you anything, and means you have a reference/reversion point if there is any question about the content after the import is delivered). NOTE that Configuration Management can be enabled within a DOORS Next Generation project even when not using Global Configurations.

HTH

Ian