Tag Archives: Digital transformation

Final Submittion – OUR JOURNEY AT ACDC 2O26

Posted on by

Problem statement: We came to ACDC Hackaton 2026 with an ambition to solve the problem that exist in supply chain, that affects everyone involved. Global spare-parts supply chains are slow, fragile, carbon-heavy, and often fail when parts are obsolete, or manufacturers no longer exist.

Original Solution we wanted to build: CraftPortal replaces shipping with digital “crafting,” using AI and cloud technology to match, recreate, and produce parts locally- fast, resilient, and sustainable. It was, however, focused on the idea from ou perspective and plan to refine this concept during the hackathon.

Evolution Journey: and then happened why we love ACDC Hackaton for.

– “Put the Customer in focus”, said Sara on the opening day, our beloved judge on Digital Transformation category.

So, we worked on the idea to enrich our web application solution to include the ISV package and give our potetial customer with UI and UX they recognize well, namely M365, Power Platform, BizApps.

– “I love your futuristic concept…” said Mikael from Redstone Realm perspective and inspired us to combine Microsoft 365 / Dynamics 365, SharePoint, Teams, and Azure

“Simple code screenshot is not enough, show me how it solves your problem”, noted Keith (Code Connoisseur),  and we challenged the status Quo and wanted to generate bigger impact…. So what we did is

“Turn data into insights….”, reminded Cathrine from Data, AI and Analytics, and we revised our data model focusing to build a solid fondation for our solution, so we could start to map external data sources and motiveted us to explore RAG.

“Everything you have there has to be there for a strong reason” warned us Fredrik from Low-Code angle in the start, and we critically reviewed our ecosystem to follow strict focus on the power of the low code.

“No security holes” declared Scott on Governance and Best Practices and you don’t mess with Scott. No fluff, we need a proper best practice focused ALM and Governance for the whole application.

As a result of continued brainstorming during these 3 days, and dialogue, our refined Solution started to look like this: … scroll down:)

DIGITAL TRANSFORMATION

The Concept

Supply chains are slow, fragmented, and carbon-heavy. Parts ship across the world when they could be printed locally. CraftPortal changes this – a marketplace where recipes travel through the portal, parts get made nearby. Faster. Greener. Smarter.

Customer needs a part. Can they print it? Yes – browse marketplace, select blueprint from IP Owner, print, deliver. No – publish a tender, receive bids from Manufacturers, select, award, contract, they print, deliver. Two paths. Same portal.

We built two paths to CraftPortal. A SaaS web application for users who want to jump straight in. And an ISV package for customers who want CraftPortal wired into their Microsoft 365 environment.

Users choose: Web App or Power Apps:

Customers who prefer Model Driven App get a clean, familiar UI – the Power Apps experience they already know, tuned for digital inventory workflows:

But they can surely use our fancy web app. Vendors – IP Owners and Manufacturers – use the Portal interface. They browse public tenders, submit bids, upload recipes, manage contracts, track orders. All through Power Pages.

Value & Monetization

CraftPortal sits in the middle of every transaction. Recipe rented? We’re there. Part printed? We’re there. That’s the value.

Monetization options:

  • Subscription – monthly/annual access to the platform
  • Transaction-based – percentage per recipe rental, per tender, per print job

Or both. Base subscription for access, transaction fee for volume.

LOW-CODE

Low-Code: The Redstone Behind CraftPortal

We built CraftPortal in 3 days. A marketplace. Tender flows. Vendor management. Document automation. AI agents and Power pages portal. How? Low-code.

The Building Blocks are as follows:

Power Pages for the Portal. Model Driven Apps for back office. Power Automate for every flow. Copilot Studio for autonomous agents. Dataverse for data. Generative Pages for dashboards.

We wired it together with clicks, not code.

The Low-Code Highlights

  • Autonomous agents – Copilot Studio detects Dataverse changes, posts to Teams, triggers RPA
  • RPA integration – Power Automate Desktop opens Bambu Lab Studio and clicks Print.
  • Teams + SharePoint + Dataverse – Fully automated channel and document location creation via Power Automate
  • Generative Pages – KPI dashboard pulling live Dataverse data
  • OneFlow contracts – Power Automate creates and sends contracts for signature
  • Link Mobility SMS – Automated bid notifications
  • Custom Connectors – ISV package API integration
  • FetchXML Builder – Low-code query generation (we click buttons, it writes XML)

Deep Dives

Want the details? We documented everything here:

The Result

A full digital inventory platform. Built by a small team. In 3 days. Low-code made it possible.

CODE CONNOISSEUR

Low-code gets you far. But sometimes you hit a wall – a custom UI that doesn’t exist, real-time updates that Power Automate can’t handle, or an API that needs to be built from scratch. That’s when we switch gears. Pro-code fills the gaps.

We have various code projects and components in our solution:

  1. PCF Control. That allows customers to order the appropriate equipment that should be printed. Client Side Salsa | Arctic Cloud Developer Challenge Submissions
  2. Power Pages Portal. That manages turning basic Minecraft resources into different tools and help clients to find an appropriate vendor for printing adapts to all devices and screen sizes. Chameleon | Arctic Cloud Developer Challenge Submissions
  3. Web Portal for the 3D printer. Using this custom local web portal we manage our printer device. Crafting, Crafting, Crafting…. Category: Pro Code  | Arctic Cloud Developer Challenge Submissions
  4. Model builder app – which is helping customer recover lost recipes from the single shot; Right now – bring real-time data to the app | Arctic Cloud Developer Challenge Submissions
  5. Azure Function – used to communicate with the external vendor API. ISV Package – the missing link | Arctic Cloud Developer Challenge Submissions

DATA, AI, ANALYTICS

The Dashboard

Our CraftPortal KPI Dashboard brings it all together. Built with Generative Pages and React, pulling live data from Dataverse:

  • Summary cards – Total Projects, Open Projects, Total Bids, Wandering Traders
  • Project Status Distribution – Donut chart showing lifecycle states
  • Bid Conversion – Submitted vs selected bids
  • Win Rate by Trader – Performance leaderboard
  • Projects per Month – Trend analysis over time
  • Top Wandering Traders – Gamified rankings

Light mode. Dark mode. Minecraft item icons from the official API. Business intelligence with a blocky twist.

We built the foundation. Dataverse as our core. Power BI dashboards for KPIs – tender status, bid conversion, vendor performance, projects per month. Live telemetry streaming from our IoT-connected Crafting Tables via Azure IoT Hub. Real-time monitoring of print jobs, temperatures, and device health.

Last year we went deep on Microsoft Fabric – Medallion architecture, Data Activator triggers, the whole pipeline. We didn’t want to repeat ourselves.

The Vision

The vision was fun: a custom Knowledge-based Copilot powered by Fabric. Pull external data from the official Minecraft API (GitHub – PrismarineJS/minecraft-data: Language independent module providing minecraft data for minecraft clients, servers and libraries.)

via Azure Data Factory. Deploy a proper RAG pipeline – chunking strategies, metadata filtering, semantic search, hybrid search, custom retrievers. Debunk RAG the right way.

Unfortunatley, we barely finished the data platform in time. The RAG adventure stays on the roadmap.

Sometimes three days isn’t enough. But the foundation is solid. The diamonds are waiting to be mined.

GOVERNANCE & BEST PRACTICES

Essence

Our goal during the hackathon was to show the complex implementation of the project with different aspects of the implementation.

When it comes to even the industry focus switched to AI related topics it still requires advanced level of the solution design to enable existing services for the LLM.

That is why we mentioned advanced level technologies such as: Azure Local, Lighthouse, and IoT Hub.

At the same time complex solutions usually require more effort for implementation. By following best practices of each piece of that puzzle, we are increasing the overall success rate of the delivery. ISV Package – the missing link | Arctic Cloud Developer Challenge Submissions

REDSTONE REALM

We created our business solution using Microsoft technologies - Open AI, Azure DevOps LLMs, Azure Function, Outlook and Microsoft teams. Check out the article ISV Package – the missing link | Arctic Cloud Developer Challenge Submissions

By deliberately meeting and exceeding every requirement across Digital Transformation, Low-Code, Pro-Code, Data & AI, Redstone Realm, and Governance & Best Practices – while continuously refining our solution through your direct feedback – we believe CraftPortal represents the complete ACDC vision, and we thank the judges for challenging us, guiding us, and inspiring us to build something truly worthy of this win.

Thank you for ACDC 2026!

With love, team LogiQraft.

PS! We really wanted to share a PREMIERE of our final movie with you, before the official release so here you go https://www.youtube.com/watch?v=KV2p3FNTLNI

ISV Package – the missing link

Posted on by

We’ve shown you the concept. The roles. The flows. The tech stack. Now let’s talk about how this actually lands in enterprise.

The simple Steve logs into an external portal. Rents recipes. Publishes tenders to print from manufacturing vendors. Monitors production and delivery status. All from the portal interface.

Works great.

But enterprise Steve, the one working at Equinor, IKEA, or Siemens -+doesn’t just browse marketplaces. Enterprise Steve has:

  • An ERP system
  • A CRM system
  • Procurement workflows
  • Approval chains
  • Compliance requirements
  • IT policies

Enterprise Steve needs CraftPortal connected to his world. His tenant. His systems. His processes.

The ISV package bridges these two worlds. Customer data stays in customer tenant. CraftPortal handles the marketplace, IP Owners, Manufacturers, the recipe catalog.

No workflow fragmentation. No copy-paste between systems. No “let me check the other portal.” One flow. Connected.

What Customer Get

Power Platform Components

ComponentCraftPortal Examples
TablesTenders, Recipes, Vendors, Manufacturers, Bids, Projects, Parts
DashboardsTender Overview, Production Status, Vendor Performance
PCF WidgetsRecipe Viewer, 3D Model Preview, Status Tracker
Power Automate templates“New Tender → Notify Vendors”, “Bid Awarded → Create Project”, “Part Printed → Update Inventory”
Security ModelRoles: Procurement Manager, Vendor, Manufacturer, Viewer

What We Get

  • AppSource listing = discoverability, Microsoft co-sell, enterprise credibility
  • Do this right and CraftPortal becomes invisible infrastructure — always there, impossible to replace

That’s not a customer. That’s a permanent relationship.

The tech stuff

Our ISV package includes two data integration flows. Custom Connector for on-demand requests — direct calls to CraftPortal API when you need real-time actions. Cached Core Data for near real-time sync — we push core data into the customer’s environment via Azure EventGrid into Azure SQL and Dataverse. Why both? Cached data enables full delegation in Power Apps. No query limits. Instant performance. Citizen developers query local tables instead of external APIs. CraftPortal data that feels like their own.

The Code

Azure Function Trigger & Interface

Trigger Type

1) HTTP-triggered Azure Function (API Gateway)

  • Used for synchronous operations and for publishing events
  • Secured via Azure AD authentication

2) Event Grid–triggered Azure Function (Event Processor)

  • Subscribes to Event Grid topic events
  • Processes vendor integration asynchronously
  • Updates Dataverse with final status/result

Interface Characteristics

  • REST-style endpoints
  • JSON request/response payloads
  • Versioned route (example):

/api/v1/vendor/operation

The Release

Power Platform Environment Strategy

Source control strategy

Repo structure (example)

  • /solutions/<SolutionName>/ (exported source using Power Platform CLI/PAC)
  • /pipelines/ (YAML for CI/CD)
  • /tests/ (integration test scripts, Postman collections, Playwright scripts, etc.)
  • /docs/ (release notes templates, runbooks)

CI Pipeline

CD Pipeline

Building the ISV package deliverable

An ISV-style deliverable usually includes:

Managed solution ZIP(s)

  • Core solution (managed)

Installation guide

  • Required licenses and prerequisites
  • Import steps
  • How to set environment variables
  • How to create/bind connections
  • Security roles to assign

Configuration workbook

  • List of env vars, defaults, required values
  • Connection references mapping
  • Any URLs/endpoints

Release notes + known issues

  • What changed, what to verify

Support / troubleshooting

  • Common import errors
  • How to re-run failed flows
  • Health check steps

Infrastructure as a code

In our solution, we are using both managed power platform ISV and dedicated cloud infrastructure for them.

It means that each customer should deploy his own Azure infrastructure to unlock Power Platform solution distributed via the AppSource.

We are introducing it via the one click Azure infra deployment process. Model driven app has dedicated admin App which is Allowing user run call the deployment by himself after the main package installation.

Referance: https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deploy-to-azure-button?WT.mc_id=IoT-MVP-5002324

Deployment

Note: The selection of the resourcegroup is not part of the BICEP / ARM template. It expects a resource is available. This selection is provided by the portal.

To support that scenarios, We need to provide the all the required bicep files, which are the blueprints for the Azure Services.

Benefits of Bicep

Bicep provides the following advantages:

  • Support for all resource types and API versions:
  • Orchestration
  • Repeatability

The following examples show the difference between a Bicep file and the equivalent JSON template. Both examples deploy a storage account:

Directory Structure

Deployment.

We are using couple of Docker compose files for prod and dev deployment.

It allow us simplify the infrastructure for the local development setup.

Keep in mind that the main rule of using docker-compose: No sensitive data should be hardcoded inside, all environment specific details must be placed to the .env file.

We are following a classic approach with private azure docker registry (ACR) to store frontend and backend docker images.

How to convince IP Owners?

The idea behind is receive all the benefits of owning the infrastructure + extra features of the Platform owner(LogiQraft) like dedicated, specifically designed AI services, Proactive monitoring system, etc…

To make it work, we are using Azure Lighthouse + Managed Identity.

How it works:

  1. The customer delegates a scope (subscription / resource group) to you via Azure Lighthouse. 
  2. Your identity in your tenant (this can be:
    • a Managed Identity, or 
    • a service principal/app)

is granted a role on their resources through that delegation.   

  1. You then query their Application Insights / Log Analytics data using your identity, and Azure enforces the delegated RBAC.

Why Lighthouse is ideal:

  • No need to create/maintain identities in every customer tenant
  • Customers can revoke access easily 
  • Scales across many tenants
  • We assume that IP Owners would be careful to share their IP and by following this approach we are addressing their concerns
Categories: Redstone Realm , Governance & Best Practices , Code Connoisseur , Digital Transformation

Badges:  Power Of The Shell, ACDC Craftsman, Plug N’ Play

Minecraft Dataflow – Recipe Import 

Posted on by

This document describes the dataflow used to import external Minecraft items into the application and map them to the Recipe table, enhancing the value of existing data that we have in the model driven app. The recipes are then used by our customer/user. 

1. Dataflow Creation 

A new dataflow is created using a blank query. The query connects to a public Minecraft API to retrieve item data in JSON format. 

2. Minecraft API Query 

The blank query is named “Get Items” and contains logic that calls the Minecraft API, converts the response into a table, and selects the required item columns. 

3. Dataflow Connection 

The connection is configured to allow the dataflow to access the Minecraft Items API. 

4. Execute the query 

Once the connection is established, the query is executed automatically to retrieve data from the Minecraft API. 

5. Table Mapping 

The output of the query is mapped to the desired Dataverse table (la_recipe). Each column from the API response is mapped to its corresponding column in the Recipe table. 

6. Dataflow Publish 

After mapping, the dataflow is published so it can be used for importing data. 

7. Running the Dataflow 

The dataflow can be scheduled or run manually. The first execution occurs automatically if it is set up as manual. The progress and status can be monitored. 

8. Check Results 

After the dataflow has run, the imported data can be verified in the model-driven app to confirm that Minecraft items are available in the Recipe table. 

Show and tell – CraftPortal Evolved: From Minecraft to Supply Chain

Posted on by

in our first post, we talked about the problem. Supply chains are slow. Parts ship across the world. Weeks pass. Carbon burns. Sometimes the manufacturer doesn’t even exist anymore.

We asked: what if supply chain worked like Minecraft?

Now let’s show you what we mean. (no, its not the same picture)

Think about how Steve plays Minecraft.

Steve needs a diamond sword. He doesn’t call a supplier in another country. He doesn’t wait for a ship. He finds the recipe, gathers materials, walks to his crafting table, and makes it. If he needs something far away, he uses a portal – instant.

Now think about CraftPortal.

A customer needs a part. Instead of ordering and waiting for shipping, they log into the Portal and post a request: “I need this part, these specs.”

IP Owners see the request. We call them Wandering Traders. They don’t ship physical parts – they sell recipes. Digital blueprints. They bid on the request.

Customer picks a recipe. Downloads it through the portal. Instant – like Steve stepping through a Nether portal.

Now the customer has two options:

Option 1: They have their own 3D printer – their Crafting Table. They print the part locally. Done in hours.

Option 2: They can’t print it themselves. They order from a Manufacturer – a Villager with better equipment. The Villager crafts it for them from a local facility.

Either way: recipe travels through the portal, part gets made locally.

No ships. No planes. No weeks. No carbon.

The Tech Behind It

The Portal is Power Pages – the marketplace. Recipes live in Dataverse. Copilot and AI Builder handle automation and intelligence. Azure IoT connects the Crafting Tables. Model Driven App runs the back office. Teams keeps everyone talking.

And LogiQraft? We’re the Redstone Engineers. We build the wiring that makes it all work.

Digital transformation

Posted on by

Wayfinder Academy: Redefining Digital Transformation in Magical Education

In an ever-evolving world where magic and technology coexist, Wayfinder Academy and its Logiquill portal represent the forefront of digital transformation within the magical education sector. By seamlessly integrating intelligent automation, data-driven insights, and a personalized approach to student guidance, we’ve set a new standard for how magical institutions can enhance their operations while meeting the expectations of the modern student.

A Magical Solution for Dynamic Needs

The mission of Wayfinder Academy is clear: to ensure that every magical student finds an environment that nurtures their unique talents, temperament, and aspirations. Our innovative processes are built on the belief that students thrive when matched with the right school, and we’ve developed a groundbreaking redundancy plan to ensure this mission continues uninterrupted—even under the most unexpected circumstances.

A turning point in Hogwarts’ history came when the Sorting Hat was temporarily stolen during a sorting ceremony, leaving the school in disarray.

This incident underscored the need for a robust, adaptable system that could provide an alternative for sorting and student reassignment. Enter the Wayfinder Academy, with its Logiquill portal: a solution that combines magical precision with technological advancements to guide students toward their ideal paths.

Intelligent Automation: A Transformative Approach

Our process begins with the student’s application submission via the Logiquill portal. From the moment the application is received, intelligent automation takes center stage:

  1. Data Collection: Students upload memorable photos and historical records are requested from their current school. These data points form the foundation of our analysis.
  2. AI-Driven Interviews: Each student participates in a digital interview with a virtual “digital twin” of one of our esteemed teachers. During this session, a pulsometer captures emotional responses and stress metrics, creating a comprehensive profile.
  3. Real-Time Analysis: Emotional and physiological data, along with responses, are stored in our dataverse. Advanced algorithms interpret these inputs to assign attributes and recommend the best faculty placement.
  4. Personalized Results: Students receive an animated, interactive experience—an owl delivers their results, followed by a magical feather writing their new faculty assignment. They also gain access to detailed reasoning and insights through the portal.
Meeting Expectations with Seamless Integration

The Logiquill portal is more than a sorting tool—it’s a hub for continuous support and engagement. Students are offered a personalized coaching program, featuring:

  • Monthly Letters: Tailored tips for successful integration into their new faculty.
  • Virtual Mentorship: Access to digital twins of professors who provide one-on-one guidance.
  • Interactive Forums: A space for students to connect, share ideas, and discuss events.

Our platform’s capabilities extend beyond sorting and mentorship. By linking Meta, LinkedIn, and Instagram accounts, the portal analyzes social engagement to generate actionable insights, track progress, and enhance the overall experience.

Delivering More with Less Through Innovation

The Wayfinder Academy exemplifies how magical institutions can deliver exceptional experiences while maximizing efficiency. Our approach achieves this by:

  • Reducing Manual Effort: Automated processes streamline application review, data analysis, and faculty recommendations.
  • Enhancing Personalization: AI and real-time data ensure every student receives individualized guidance tailored to their needs.
  • Driving Continuous Improvement: Insights derived from forum discussions and social media analysis enable proactive support and dynamic enhancements to our services.
A Bridge Between Expectation and Capability

The integration of intelligent automation into magical education through the Wayfinder Academy and Logiquill portal is a testament to the potential of digital transformation. By weaving a spell that bridges the gap between customer expectations and operational capabilities, we’ve created a solution that empowers students and institutions alike.

Wayfinder Academy is not just reshaping how magical students find their paths—it’s setting a new precedent for innovation, personalization, and efficiency in education. With every detail meticulously designed, we’re proud to demonstrate how businesses can achieve more with less while delivering unparalleled experiences to their communities.

We love existential risks!

Posted on by

The existential risk is real! As Slytherins there is nothing we would love more than a bit of chaos. So of course we take all risks and use AI!

We use Azure service APIs for both prompting and text-too-speech combined with pro-code run in our Python Flask app:

The chat completion prompt goes as follow:

You are an assistant that helps transform a text to a specific tone of voice.
It is supposed to be a letter read out loud.
Start with greeting the recipient and end with goodbye from the sender.
If appropriate, add references to the Harry Potter universe.
Keep it short.

This prompts adds a dazzle of Hogwarts magic to each message;

Original message:
I don’t like you anymore. You have proven to be untrustful!

Magically transformed message:
Oh, how the tides have turned! I find myself in a whirlwind of emotions, and I must confess, I don’t like you anymore. Your betrayal stings like a Cruciatus curse, and it’s clear you’ve proven to be utterly untrustworthy!

After obtaining the magically bedazzled message, we run text-to-speech from Speech Services to magically transform the written message to speech in your preferred tone:

More is Less. Effective work with Feature rich Logiquill Portal

Posted on by

We hope you liked our Logiquill platform we demonstrated to you yesterday. With it, we really enable our Wayfinder academy employees to manage their work in more effective way, reducing operational stuff, manual work and all of it – by use of the technologies we describe below. Hence by saving time on those time consuming processes, they can allocate it to the more meaningful and strategic tasks. This is what we call Digital transformation.

At this portal, in the Admin view, we have features like (as displayed on the screenshot below):

  • Digital Twins of our judges (mentors), generated by AI, and connected to the database which has the custom survey tailored to guide the student thru questions, that helps to identify their values, aspirations, reactions to stress, etc.
  • Heart rate readings which is a real time data, coming from the Pulsoxymeter device.
  • Emotion recognition via the third party solution (more about this you can read here Unveiling Hidden Feelings with the Magic of AI | Arctic Cloud Developer Challenge Submissions)
  • Speech to text for the response on the survey.

With all this Digital Transformation, do you feel this Existential Risk?

Posted on by

Or maybe, our honorable jury feels like its a good idea delegating some work in the hackaton to their Digital Twins and free up some time for “Me time”? Well, we thought about this already, as in our Wayfinder Academy, we really needed you to help us in interviewing students that send us their applications to get help on defining the faculties they truly belong to. So, given how busy you are, we used Elai.IO to generate videos that visualize you running an interview.

It went so well, that we went further to implement Copilot Agents (WE LOVE THEM!!!) so that they, fed by the data related to you and available, will provide real time experience for the students going thru the interview or getting some mentorship as if they are talking to you and not your digital twin.

Are you excited to see it?

Below is the view we have when the interview is running, where you see both the video, and some other data (described here Magic Sensors: the enchanted Howlers of the tech world—they always tell you what’s wrong, loudly and repeatedly. | Arctic Cloud Developer Challenge Submissions)



And below is the students view, isn’t it beautiful?

Power BI alerts to warm you up!

Posted on by

Faruk the Fabricator who travelled all the way from sunny Istanbul, got really frozen outdoors. So he came back unusually alerted and went straight into work, to warm up.

Data activators is up. When failure is close, our Fabricator will know.

An alert has been set for the KPI column. When it falls below a certain value we send an email and alert the user.

More will come with table based data activators. This is just the beginning.

Faruk the Fabricator is just warming up…

PS: we claimm PlugNPlay badge for the sending notifications to TEAMS

Low body temperature and Low Code: Dataverse + Model-driven app

Posted on by

Keeping up with our Low code focus, even after the outdoor activity which rushed our metabolism to its highest level! It feels GRRRRREAT!!!! Thanks for arranging this.

We are building a backend for the academy administrators  using Dataverse and Model driven application.

  • Streamline Customization: Tailor forms, views, and processes to specific roles, ensuring academy administrators have access to the exact tools they need without overloading the interface.
  • Reduce Development Time: Focus on delivering business value rather than spending weeks coding. The drag-and-drop interface and prebuilt templates save hours of manual work.
  • Enable Scalability: Easily adapt to growing needs, whether adding new survey question categories or introducing workflows to automate survey evaluations.
  • Boost Collaboration: Team members with varying technical expertise can collaborate effectively, bridging the gap between IT and business teams.

The dataverse allows us easily set up the data model for Survey Questions for students:

We are using the power of the Model-driven apps to easily create a back office to easily set up which forms and views are accessible for our academy administrators: