<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: Enhancement Request: Artifact-Level Segregation of Duties (Thread)</title><description>       Hello Inflectra Support Team,  We have a small user base, and user responsibilities frequently change between  Author  and  Reviewer  roles across different projects. Currently, ReverTO 2.0 allows only one role per user per project, which requires frequent role changes and creates additional administrative effort.  Would it be possible to control this at the  artifact level  rather than the  role level ?  For example, a user could be assigned a combined  Author/Reviewer  role, while the system automatically enforces segregation of duties based on the artifact owner:   Example:    User A authors Artifact 001.  The system records User A as the artifact author.  If User A attempts to review or approve the same artifact, the system prevents the action.  The review and approval must then be completed by another qualified user.   This approach would maintain compliance by preventing self-review while eliminating the need for frequent role changes. It would also allow the same user to act as an Author on one artifact and a Reviewer on artifacts created by other users.  For organizations with smaller teams, this would provide greater operational flexibility while still ensuring proper segregation of duties and audit compliance.  Could you please advise whether such a workflow-based restriction or configuration is currently available in Spira Test?  If this functionality is not currently available, could you consider it as a Next Release Enhancement? We believe this feature could be beneficial not only for our organization but also for other customers with smaller teams who face similar resource and role-management challenges.  Thanks &amp; Regards,  Rajesh Malwiya </description><language>en-US</language><copyright>(C) Copyright 2006-2026 Inflectra Corporation.</copyright><managingEditor>support@inflectra.com</managingEditor><category domain="http://www.dmoz.org">/Computers/Software/Project_Management/</category><category domain="http://www.dmoz.org">/Computers/Software/Quality_Assurance/</category><generator>KronoDesk</generator><a10:contributor><a10:email>support@inflectra.com</a10:email></a10:contributor><a10:id>http://www.inflectra.com/kronodesk/forums/threads</a10:id><ttl>120</ttl><link>/Support/Forum/spiratest/issues-questions/3259.aspx</link><item><guid isPermaLink="false">threadId=3259</guid><author>Rajesh Malwiya (rajesh.malwiya@xellia.com)</author><title>Enhancement Request: Artifact-Level Segregation of Duties</title><description>       Hello Inflectra Support Team,  We have a small user base, and user responsibilities frequently change between  Author  and  Reviewer  roles across different projects. Currently, ReverTO 2.0 allows only one role per user per project, which requires frequent role changes and creates additional administrative effort.  Would it be possible to control this at the  artifact level  rather than the  role level ?  For example, a user could be assigned a combined  Author/Reviewer  role, while the system automatically enforces segregation of duties based on the artifact owner:   Example:    User A authors Artifact 001.  The system records User A as the artifact author.  If User A attempts to review or approve the same artifact, the system prevents the action.  The review and approval must then be completed by another qualified user.   This approach would maintain compliance by preventing self-review while eliminating the need for frequent role changes. It would also allow the same user to act as an Author on one artifact and a Reviewer on artifacts created by other users.  For organizations with smaller teams, this would provide greater operational flexibility while still ensuring proper segregation of duties and audit compliance.  Could you please advise whether such a workflow-based restriction or configuration is currently available in Spira Test?  If this functionality is not currently available, could you consider it as a Next Release Enhancement? We believe this feature could be beneficial not only for our organization but also for other customers with smaller teams who face similar resource and role-management challenges.  Thanks &amp; Regards,  Rajesh Malwiya </description><pubDate>Mon, 19 Oct 2026 09:12:05 -0400</pubDate><a10:updated>2026-10-19T09:12:05-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/3259.aspx</link></item></channel></rss>