Skip to content
Studio (opens in a new tab)Get in touch
Menu
A Softeria developer explaining a diagram on a whiteboard

How it works

Experts build.IT decides.

The person who knows the job describes the solution, and Studio designs the database, writes the code and sets up sign-in. The IT department sets the limits it is built within.

What each side does

The domain expert

Builds what the work needs

  • Describe the solution in plain language, the way you would explain it to a colleague
  • Studio designs the database, writes the code and sets up sign-in
  • Try it on test data, then on live data where your group allows it
  • Change it yourself when the work changes — no new quote, no queue

The IT department

Sets the rules, sees everything

  • Everyone signs in through your identity provider — no new passwords
  • The groups in your directory decide who may build, use live data and publish
  • Rules on the data decide which records each person can see
  • A log of who built, changed and opened what
  • Hosting, backups and security updates are run by us

In practice

One request, two roles, one screen.

Kari in site operations asks for an inspection checklist. Studio builds it. The rules IT has set apply from the first version, and who built, changed and opened it is logged.

Request · Kari · Site operations

A checklist for site inspections. Inspectors fill it in on their phone and attach photos, and the project manager signs off. Inspectors should only see projects in their own region.

Studio built

Data model
projects, inspections, photos
Screens
phone and desktop
Sign-in
company account
Access
inspectors see their own region’s projects

Governance · set by IT

Identity
Microsoft Entra ID
Kari’s group
Builders
Live data
Limited
Publish
Team leads and IT
Audit log
On

Audit log

  1. kari built “Site inspections”
  2. kari changed the data model
  3. ola (IT) published to Site operations
Illustration: a site-operations employee asks Studio for an inspection checklist. Studio builds the data model, screens, sign-in and an access rule, while the governance settings chosen by IT and an audit log show alongside.

Illustration

Who is in the room

Both sides, at the same table.

The point is not that IT stops being involved. It is that the involvement happens once, when the rules are set, instead of every time somebody needs a form changed.

What IT controlsWhat runs underneath