Gateflow

A complete course description may consist of many, many different bits of information. Text fields are usually the responsibility of course coordinators or lecturers, while other fields like semester, cost, exam status etc. are areas handled by administrative resources. Our unique gateflow let you split fields into groups tailored to each interest group allowing work to be performed in parallel removing bottlenecks.

Gates

In a more traditional workflow, you have to decide who is next in line, unless the workflow is linear and "single file" only. We believe this is suboptimal. Your only concern should be whether you are done.

Our gateflow is a bit different. A gateflow consist of many gates, each representing a set of work to be done. Each gate has a gate keeper who decides when the work is finished and then close the gate. When Gates are closed, new gates may open up.

Non-linear

Several gates can be open at the same time. This allows different interest groups to work on the content in parallel tracks removing bottlenecks.

Notifications

Each gate in the gateflow can be configured separately from each other. Gate A may involve individual users, e.g. lecturers, or program coordinators. Another gate B may involve a group of people, e.g. the study administration, that work on content collectively. It would make sense to email users in gate A, while group B probably spends more time in the system and is perfectly capable of keeping track of tasks using the dashboard.

Field-level access

Each gate can further be configured to require or disable access to individual fields in the content. One gate group, e.g. the library, may want to check that the reading list is correct, but shouldn't have to concern themselves with learning goals etc. Defining required and disabled fields for each gate reduces stress and complexity for each user! It also avoids accidents...

Access calculations

Access can be tied to roles, as you would expect, but the biggest feature of our gateflow is that access can be dependent on the content itself.

Large organizations may have many study administrations, but there is only need for one "study administration" gate. Access to a particular content being handled by the study administration can be further specified by requiring that the user has the same study program as the content. Or the same institute, or faculty. Access can be many-faceted and as specific as you want.

This is a very powerful feature and we would love to explain why we believe this is the best solution for large organizations with complex workflows.

They trusted us:

After a frustrating year of trying to get another CMS on the air, it was a great relief to enter into a cooperation agreement with Norweb. Edutorium had most of the systematics and capabilities we needed at BI, and where we needed more, Norweb's developers showed forward-looking and solution-oriented and with a great deal of flexibility. So we ended up with a product that was very well adapted to our processes and workflow

Eivind Bergem
Director of Education Quality
BI Norwegian Business School