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 & Regards, Rajesh Malwiya en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spiratest/issues-questions/3259.aspxthreadId=3259Rajesh Malwiya (rajesh.malwiya@xellia.com) 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 & Regards, Rajesh Malwiya Mon, 19 Oct 2026 09:12:05 -04002026-10-27T10:19:40-04:00/Support/Forum/spiratest/issues-questions/3259.aspxmessageId=7732Victoria D (nino.diasamidze@inflectra.com) Dear Rajesh, What youre describing is a specific compliance pattern: a single combined Author/Reviewer role, with the system automatically blocking a user from reviewing/approving an artifact they authored (preventing self-review), based on recorded artifact ownership rather than per-project role assignment. Out of the box, SpiraPlans permission model is role-based per project, so the one role per user per project limitation you mention is accurate - self-review prevention based on the recorded author is not a standard toggle. I recommend you to contact support directly in a dedicated ticket , attach all required details so our specialist can review and communicate using a support portal. Regards, Victoria - Wed, 21 Oct 2026 10:27:06 -04002026-10-21T10:27:06-04:00/Support/Forum/spiratest/issues-questions/3259.aspx#reply7732