Orgzit has a multiple level access control system. Using the different access control features provided by Orgzit, you can set up an efficient and secure system in which every user can only access the data and workflows relevant to him.

Stage Transition Rules enable you to control who can make a particular stage change. You can set rules for every possible stage change within your table.

For instance, if you want that a user with the role of an HR should be able to change the stage of an employee payroll from Prepared to Sent for Approval, but it should move to the Approved stage only by the Accounts team user, you can set Stage Transition Rules to control the same.

To implement stage level permissions based on User Roles, the following steps need to be performed:

  • Go to Table Setting and Move to Table Fields.
  • Move to the Field in which you want to add this feature.
  • In the Field Attribute, add Stages.
  • To configure stages, enter the choices/list of stages that you want.
  • Add the Transition Rules.

    For a stage change from any stage, A to B, enter the roles to whom you want to grant the permission to make the stage change. Similarly, you can grant permissions for every possible stage change. Only the Transition Rules that you specify will decide which user can make a certain change.

    Also, for a stage change from A to B, if you leave the first stage(A) blank it means that the state change can happen from any stage to stage B and if you leave the second stage(B) blank it means that the state change can happen from A to any other stage.

    Remember: If you leave the Roles field blank, any role will be able to make that particular transition. You can choose to set the Roles for transitions on which you want to set access control and leave the rest in which you do not want to set any constraints.

You can assign Color Scheme to your stages as well. Assigning different colors to the different stages make your data more presentable and easy to read.


  • Click on Done once the configuration is complete.

Common Field Attributes Used with Stages

You can use the following attributes along with your Stages data field to make your process more efficient:

  • Default Value: You can set a default value for your data field using this attribute. For instance, if your first stage always has to be "New Bill", you can set it as the default value.
  • Detail Only: You can use this attribute if you do not want this data field to be present in the tabular view of your data, and only in the expanded view of the record.
    If you apply this attribute, you can still view the data field in the tabular view by using the show/hide fields feature, if required.
  • Required: If you want that the value for this field must be present in your record, you can set the required attribute to do so. While creating a record, if the value for a required field is not present, the system will give an error.
  • Hidden During Create: This attribute hides the data field from the record create form. If this field is not required at the time of record creation, you can use this attribute.

Check out this video to understand how to set up stage transition rules!

Did this answer your question?