This page describes various workflows specific to the Kodex Enterprise Edition.
Change Request Workflow
The change request workflow ensures that any changes to a given project are properly reviewed before being merged. The flow is similar to a "pull request" workflow in software development:
- When working on a change, a user creates a change request within the relevant project. All change requests start in the draft state, indicating that they are actively being worked on and that they are not ready for review yet.
- All changes the user makes get automatically documented in the change request and can be previewed in the Kodex web UI, without affecting the existing project configuration in any way.
- Once the user is happy with the changes they made, the change request can be marked as ready for review.
- A reviewer can open the change request, inspect the changes and test them. If everything is satisfactory, the change request can be marked as approved. If not, the reviewer can leave comments and ask for changes. The change request can also be rejected.
- Once reviewed, the change request can be merged into the project.
Kodex uses role-based access control mechanisms to govern permissions and access rights for projects. The enterprise edition usually retrieves user roles from a Single Sign On (SSO), and maps them to organization roles within Kodex.
- A given external user role, e.g. as given by the SSO provider, can be mapped to one or multiple organization roles within Kodex.
- An organization role can be given specific permissions on a project by adding it as an object role to the project. For example, if there's an organization role named dpo (for data protection officer), we could map it to the reviewer role in a project by using such a mapping, allowing data protection officers to review changes in the project.