<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kasja Maksymiak on Medium]]></title>
        <description><![CDATA[Stories by Kasja Maksymiak on Medium]]></description>
        <link>https://medium.com/@kasja?source=rss-b5e570f73bb3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LmhoU2s4ClLYqOZL-LwWrw.png</url>
            <title>Stories by Kasja Maksymiak on Medium</title>
            <link>https://medium.com/@kasja?source=rss-b5e570f73bb3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 23:09:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kasja/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Mendix Center of Excellence — Cloud Hosting Options]]></title>
            <link>https://medium.com/@kasja/mendix-center-of-excellence-cloud-hosting-options-f8455f522a41?source=rss-b5e570f73bb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8455f522a41</guid>
            <dc:creator><![CDATA[Kasja Maksymiak]]></dc:creator>
            <pubDate>Mon, 20 Jul 2026 12:50:39 GMT</pubDate>
            <atom:updated>2026-07-21T14:28:54.060Z</atom:updated>
            <content:encoded><![CDATA[<p>The best way to host your Mendix applications depends on your company’s existing infrastructure and rules. Choosing Mendix as your low-code platform does <strong>not</strong> mean you have to use Mendix Cloud.</p><p>You have <a href="https://www.mendix.com/evaluation-guide/deployment/flexibility/options/">several options</a> for hosting your applications:</p><ul><li><strong>Mendix Cloud —</strong> in the Mendix Cloud (<em>multi-tenant public </em>or<em> single-tenant dedicated</em>). More info <a href="https://docs.mendix.com/developerportal/deploy/mendix-cloud-deploy/">here</a>.</li><li><strong>Third-Party Cloud — </strong>on out-of the-box supported by Mendix other (third-party) cloud platforms, such as Azure or SAP, while still being connected to the Mendix Platform. More info <a href="https://docs.mendix.com/developerportal/deploy/private-cloud/">here</a>.</li><li><strong>Private Mendix Platform — </strong>on customizable other (third-party) cloud platforms like AWS, using Kubernetes, with a private alternative to Mendix Sprintr: the Private Mendix Platform (PMP) hosted on your own infrastructure. More info <a href="https://www.mendix.com/platform/governance/deployment/private-mendix-platform/">here</a>.</li><li><strong>On-Premises</strong> — on your own servers using the Mendix Portable Runtime deployment approach. More info <a href="https://docs.mendix.com/developerportal/deploy/portable-app-distribution-deploy/">here</a>.</li></ul><p>You can also decide how closely you want to connect to the Mendix Platform. For example:</p><ul><li>Use the <strong>Public</strong> Mendix Platform services</li><li>Use the Mendix Platform <strong>Connected</strong> to your own infrastructure</li><li>Or run your own <strong>Private</strong> Mendix Platform on your own infrastructure</li></ul><p>This flexibility means you can choose a setup that fits your company’s needs, whether that’s more control, stricter compliance, or simply aligning with your existing IT landscape.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*1XU1rfONOhoPl0Br-378xw.png" /><figcaption>Cloud Hosting Options for Mendix</figcaption></figure><h3>Mendix Cloud</h3><p>Mendix Cloud is a fully managed platform (PaaS) where Mendix applications are deployed, run, and operated by Mendix itself. It is built on AWS and Kubernetes, and optimized specifically for running Mendix applications.</p><ul><li>Fully managed infrastructure (hosting, scaling, backups, monitoring)</li><li>High availability and disaster recovery</li><li>Global regions</li><li>Integrated lifecycle tooling (deployment, logging, alerting)</li><li>Minimal need for DevOps setup</li></ul><p>Within Mendix Cloud, there are two main deployment models:</p><ol><li><strong>Mendix Cloud Public (multi-tenant)</strong></li><li><strong>Mendix Cloud Dedicated (single-tenant)</strong></li></ol><h4>Mendix Public Cloud</h4><p>Mendix Cloud Public is a multi-tenant platform, where applications from multiple customers run on shared infrastructure managed by Mendix.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*x3YVcnKSdYcXAf7UM2LFMA.png" /></figure><p><strong>When to use Mendix Public Cloud</strong></p><ul><li>You want speed and simplicity over control</li><li>Applications are standard business applications with predictable workloads and no high-volume peak loads</li><li>There are no strict regulatory or isolation requirements</li><li>You want to avoid platform engineering overhead</li></ul><h4>Mendix Cloud Dedicated</h4><p>Mendix Cloud Dedicated is a single-tenant version of Mendix Cloud:</p><ul><li>The platform is still managed by Mendix</li><li>But the infrastructure is dedicated to one customer only</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/894/1*di3uMRtt6CAUX0m07o7TuQ.png" /></figure><p><strong>When to use Mendix Cloud Dedicated</strong></p><ul><li>You need isolation for compliance or risk reasons</li><li>You want more control, but not full platform ownership</li><li>You operate business-critical or sensitive workloads</li></ul><h4>Public Mendix Platform (Sprintr)</h4><p>Mendix Sprintr acts as the central operational hub for all Mendix applications within your organization and is used to:</p><ul><li>Manage applications, environments, and deployments</li><li>Organize teams and access control</li><li>Track development progress through stories, feedback, and activities</li><li>Configure application settings and lifecycle management</li></ul><h3>Third-Party Cloud</h3><p>With hosting your Mendix applications on a Third-Party Cloud you can remain on your own cloud environment (e.g. Azure, SAP, Kubernetes on AWS) while remaining <strong>connected</strong> to the Mendix Platform for lifecycle management and operations.</p><h4>Out-of-the-box</h4><p>Mendix provides pre-configured deployment options for major cloud providers (e.g. Azure, SAP). It simplifies setup and reduces initial platform engineering effort.</p><h4>On Kubernetes</h4><p>With Mendix on Kubernetes applications are deployed on your own Kubernetes cluster or cloud subscription. You control where applications run and how the infrastructure is configured, while remaining connected to the Mendix Platform.</p><p>This results in a hybrid experience: application management remains centralized in Mendix, while infrastructure management is handled separately in your own cloud environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*deDgeGWKFitOqJz_CZQhcA.png" /></figure><p><strong>When to use Third-Party Cloud</strong></p><ul><li>You require full infrastructure control, but not full platform ownership</li><li>You do not have a fully mature DevOps / platform engineering setup</li><li>You want to balance control with speed of delivery</li><li>You want to maintain high Developer Experience</li></ul><h4>Mendix Platform connection</h4><p>Mendix applications running on a third-party cloud remain connected to the Mendix Platform, where application lifecycle management such as deployments and cloud node configuration is handled.</p><p>At the same time, the underlying cloud infrastructure (e.g. Kubernetes, networking, and scaling) is managed through the cloud provider’s own tools.</p><h3>Private Mendix Platform</h3><p>A Private Mendix Platform using third-party cloud running on Kubernetes is the most independent deployment model, where Mendix applications are deployed on a self-managed Kubernetes platform without any connection to the (Public) Mendix Platform for lifecycle management.</p><p>This model is typically used in air‑gapped or highly restricted environments, where no external connectivity to (Public) Mendix services is allowed. Instead, all deployments, configuration, and operations are handled through a self-hosted Private Mendix Platform (PMP).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JewBBCGjnei6fqRNDJzSNQ.png" /></figure><h4>Private Mendix Platform (PMP)</h4><p>Mendix Private Platform (PMP) can be best understood as running your own version of Sprintr (Mendix Platform) on your own infrastructure, instead of connecting to the (Public) Mendix Platform. In this setup, Mendix applications run on your own Kubernetes environment, and you manage everything yourself, including deployments, CI/CD, monitoring, and governance, using your own Private Mendix Platform and internal tools. This means Mendix is no longer a separate managed platform, but becomes just another workload within your enterprise platform. It gives you maximum control and alignment with your own IT standards, but also means you take full responsibility for operating and governing the platform.</p><p><strong>When to use Mendix Private Platform</strong></p><ul><li>You have strict security or compliance requirements, including air‑gapped environments where external connectivity is not allowed</li><li>You need full control over data location and sovereignty</li><li>Your applications require deep integration with internal systems</li><li>You want full control over your cloud architecture and platform setup</li><li>You are moving toward a platform-driven IT strategy (e.g. PMP)</li></ul><h3>On-Premises &amp; DIY Tools</h3><p>On‑Premises deployment means running Mendix applications directly on your own servers (virtual or physical) within your own data center or infrastructure.</p><p>The application is deployed as a runtime package (e.g. .mda) and you manage everything yourself:</p><ul><li>servers</li><li>runtime</li><li>database</li><li>networking</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Usc1IKJJ5eaid6y5qCDPrQ.png" /></figure><h4>Mendix Portable Runtime</h4><p>Mendix Portable Runtime is a deployment approach where a Mendix application is packaged into a self-contained, runnable artifact that includes all required dependencies.</p><ul><li>The app can be copied and run directly on different environments</li><li>Only a minimal runtime (e.g. Java) is required</li></ul><p><strong>When to use On-Premises with Mendix Portable Runtime</strong></p><ul><li>You operate in air‑gapped or highly restricted environments</li><li>You require maximum control over infrastructure</li><li>You need simple, portable deployment across environments</li><li>You have minimal platform requirements</li></ul><h3>Comparison Matrix</h3><p>More info <a href="https://www.mendix.com/evaluation-guide/deployment/flexibility/decision-guide/">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*7czv1ihHNm97BYyPgo9Tmw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8455f522a41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mendix Center of Excellence — Audit Logs]]></title>
            <link>https://medium.com/@kasja/mendix-center-of-excellence-audit-logs-11fc4a7dd89c?source=rss-b5e570f73bb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/11fc4a7dd89c</guid>
            <dc:creator><![CDATA[Kasja Maksymiak]]></dc:creator>
            <pubDate>Tue, 16 Jun 2026 14:13:48 GMT</pubDate>
            <atom:updated>2026-06-16T14:13:48.682Z</atom:updated>
            <content:encoded><![CDATA[<p>In many enterprises, Mendix adoption starts fast — and scales even faster.<br>Before you know it, you’re managing dozens or even hundreds of apps, environments, users, and deployments.</p><p>And then the questions start:</p><ul><li><em>Who changed this configuration?</em></li><li><em>Why did this deployment fail?</em></li><li><em>Which admin gave access to production environments?</em></li><li><em>Can we prove this for audit/compliance?</em></li></ul><p>That’s exactly where Mendix Control Center Audit Logs and the Audit Log API shift from “nice to have” to mission-critical capability.</p><h3>The Real Challenge: Lack of Traceability at Scale</h3><p>Low-code accelerates delivery, but it also introduces a new kind of complexity:</p><ul><li>Distributed ownership (Business + IT)</li><li>Rapid change cycles</li><li>Increasing compliance pressure (GDPR, NIS2, internal audits)</li><li>Growing platform footprint</li></ul><p>Without a centralized audit capability, you’re left with:</p><ul><li>Fragmented logs</li><li>Manual investigation</li><li>Limited forensic insight</li><li>Weak audit trail</li></ul><h3>Mendix Control Center Audit Logs: A Single Source of Truth</h3><p>The Audit Logs in Mendix Control Center provide a centralized, platform-wide audit trail of everything happening across your Mendix landscape.</p><p>At its core, it records:</p><ul><li><strong>Who</strong> performed an action (email address)</li><li><strong>What</strong> action was performed (deployment, creation, download etc.)</li><li><strong>When</strong> it happened (timestamp)</li><li><strong>Where</strong> it happened (service/resource)</li><li><strong>Outcome</strong> (success, warning, error)</li></ul><p>Plus detailed metadata like:</p><ul><li>Resource type (app, environment, user, backup, etc.)</li><li>Origin (user, API, system task)</li><li>IP address (for security tracing)</li><li>Full log details per event</li></ul><p>And importantly:<br>Audit history is retained for up to 365 days, giving you real audit depth.</p><p>Read more here: <a href="https://docs.mendix.com/control-center/audit-logs/">https://docs.mendix.com/control-center/audit-logs/</a></p><h3>Why This Matters (Beyond Logging)</h3><p>Audit Logs are not just “logs”, they are the foundation for:</p><h4>1. Security &amp; Incident Response</h4><p>Audit logs enable:</p><ul><li>Detection of suspicious access attempts</li><li>Investigation of failed or unauthorized actions</li><li>IP-based tracing of user behavior</li></ul><p>They explicitly support security monitoring and forensic analysis.</p><h4>2. Compliance &amp; Audit Readiness</h4><p>For enterprises, this is the big one.</p><p>Audit logs:</p><ul><li>Provide a traceable record of administrative actions</li><li>Support regulatory compliance requirements</li><li>Enable proof of control during audits</li></ul><p>This aligns directly with enterprise governance expectations where audit trails and policy enforcement are mandatory.</p><h4>3. Troubleshooting &amp; Root Cause Analysis</h4><p>When something breaks:</p><ul><li>You don’t guess</li><li>You don’t ask around</li><li>You trace the exact action sequence</li></ul><p>Audit logs allow you to:</p><ul><li>Identify configuration changes</li><li>Trace deployment actions</li><li>Understand system behavior over time</li></ul><p>They explicitly support problem solving and troubleshooting.</p><h4>4. Platform Transparency &amp; Insights</h4><p>With enterprise-scale Mendix landscapes:</p><ul><li>Who is actually using what?</li><li>Which services are changing frequently?</li><li>Where are operational risks?</li></ul><p>Audit logs provide visibility into user behavior and resource usage, turning governance from reactive to proactive.</p><h3>The Real Power Move: The Audit Log API</h3><p>While the UI is powerful, the Audit Log API is where things become truly enterprise-grade.</p><p>It allows you to programmatically access audit data from Mendix</p><p>(API specs: <a href="https://docs.mendix.com/apidocs-mxsdk/apidocs/apis-for-audit-logs/">https://docs.mendix.com/apidocs-mxsdk/apidocs/apis-for-audit-logs/</a>)</p><p>And that unlocks entirely new possibilities:</p><h4>1. SIEM Integration</h4><p>Push audit logs into:</p><ul><li>Splunk</li><li>Datadog</li><li>Azure Sentinel</li></ul><p>Result: Centralized security monitoring across your entire IT landscape</p><h4>2. Custom Dashboards &amp; Reporting</h4><p>Instead of manually browsing logs:</p><ul><li>Build Power BI / Tableau dashboards</li><li>Track trends (e.g., deployments, failures, access changes)</li><li>Provide board-level insights</li></ul><h4>3. Automated Compliance Reporting</h4><ul><li>Generate audit reports automatically</li><li>Filter by environment, user, or action</li><li>Deliver evidence for audits without manual effort</li></ul><h4>4. Real-Time Alerting</h4><p>Combine API + automation to trigger alerts on:</p><ul><li>Failed access attempts</li><li>Role/permission changes</li><li>Production deployments</li></ul><h4>5. Integration into DevOps Pipelines</h4><p>Audit logs become part of your delivery process:</p><ul><li>Validate deployment actions</li><li>Track pipeline events</li><li>Correlate changes across environments</li></ul><h3>Final Takeaway</h3><p>Mendix Audit Logs are not just a feature, they are a governance accelerator.</p><ul><li>They give you visibility</li><li>The API gives you control</li><li>Together, they enable enterprise-grade observability</li></ul><p>In a world where low-code accelerates change,<br>auditability becomes your safety net.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rORuT6_to6HoqazLXe4txg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11fc4a7dd89c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mendix Center of Excellence — Software Composition]]></title>
            <link>https://medium.com/@kasja/mendix-center-of-excellence-software-composition-c71b05a6bb4b?source=rss-b5e570f73bb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/c71b05a6bb4b</guid>
            <dc:creator><![CDATA[Kasja Maksymiak]]></dc:creator>
            <pubDate>Mon, 15 Jun 2026 09:02:35 GMT</pubDate>
            <atom:updated>2026-06-15T09:02:35.130Z</atom:updated>
            <content:encoded><![CDATA[<p>Low-code gives teams the power to move fast. Applications can be built, iterated, and deployed in a fraction of the time compared to traditional development.</p><p>But that flexibility comes with a challenge.</p><p>As your Mendix landscape grows beyond a handful of apps into dozens or even hundreds, maintaining a centralized view of quality, dependencies, and risks becomes increasingly difficult.</p><p>And without that visibility, you’re no longer in control.</p><h3>The Scaling Challenge: From Speed to Oversight</h3><p>In many organizations, Mendix adoption grows organically.<br>Different teams build applications, reuse components, and integrate modules. Often with the best intentions, but without a shared overview.</p><p><strong>Typical symptoms:</strong></p><ul><li>No clear insight into which components are used where</li><li>Limited visibility into security or quality findings across apps</li><li>Difficulty assessing impact when a vulnerability appears</li><li>Time-consuming manual analysis during audits or incidents</li></ul><p>For a Mendix Center of Excellence (CoE), this is a critical gap. You’re not just enabling teams, you’re responsible for governance, risk management, and platform quality at scale.</p><h3>Mendix Control Center: Software Composition</h3><p>Mendix addresses this challenge with the Software Composition capability in Control Center (<a href="https://docs.mendix.com/control-center/software-composition/">https://docs.mendix.com/control-center/software-composition/</a>).</p><p>This feature provides a centralized, cross-application overview of all components used across your Mendix landscape. Think of it as your single source of truth for dependencies and findings.</p><p><strong>What you get:</strong></p><h4>1. Centralized visibility</h4><p>A complete overview of:</p><ul><li>Components used across all applications</li><li>Associated findings (e.g., security or quality issues)</li></ul><p>No more jumping between apps in Mendix Sprintr — everything is aggregated in one place.</p><h4>2. Component-level insights</h4><p>You can drill down into individual components and see:</p><ul><li>Where they are used</li><li>Which applications depend on them</li></ul><p>This is crucial for understanding your dependency landscape.</p><h4>3. Impact analysis for incidents</h4><p>If a vulnerability is discovered in a specific component:</p><ul><li>Instantly identify all affected applications</li><li>Prioritize remediation based on impact</li></ul><p>This turns reactive firefighting into controlled, data-driven decision making.</p><h4>4. Export and reporting</h4><p>Need to share insights with stakeholders or auditors?</p><ul><li>Export findings easily</li><li>Integrate into governance reports</li></ul><p>Perfect for compliance, audits, and executive reporting.</p><h3>Why This Matters for a CoE</h3><p>For a Mendix CoE, Software Composition is not just a technical feature — it’s a governance enabler.</p><p><strong>It helps you:</strong></p><h4>1. Stay in control without slowing teams down</h4><p>You don’t need to block development to maintain oversight.<br>The Control Center gives you visibility without adding friction.</p><h4>2. Shift from reactive to proactive governance</h4><p>Instead of discovering issues during incidents:</p><ul><li>Monitor continuously</li><li>Act early on emerging risks</li></ul><h4>3. Enable safer reuse</h4><p>Reusability is core to Mendix — but it introduces dependency risks.<br>With Software Composition:</p><ul><li>You can promote trusted components</li><li>Detect risky or outdated ones early</li></ul><h4>4. Strengthen security posture</h4><p>You gain the ability to:</p><ul><li>Trace vulnerabilities across the entire landscape</li><li>Respond faster and more effectively</li></ul><h3>From Inventory to Insight</h3><p>Many organizations already have <em>lists</em> of applications.</p><p>But a list is not enough.</p><p>What you really need is: Insight into what’s inside those applications</p><p>That’s exactly where Software Composition delivers value:</p><ul><li>It goes beyond inventory</li><li>It provides context, relationships, and impact</li></ul><h3>Final Thoughts</h3><p>As your Mendix platform scales, governance needs to scale with it.</p><p>The Software Composition feature in Control Center gives your CoE the tools to:</p><ul><li>Maintain oversight</li><li>Manage risk</li><li>Support teams effectively</li></ul><p>Without compromising the speed and flexibility that makes low-code powerful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LocBUjUNMGfwNspYwB46vA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c71b05a6bb4b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mendix Center of Excellence — Project Categorization]]></title>
            <link>https://medium.com/@kasja/mendix-center-of-excellence-project-categorization-c7b16186b338?source=rss-b5e570f73bb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7b16186b338</guid>
            <dc:creator><![CDATA[Kasja Maksymiak]]></dc:creator>
            <pubDate>Thu, 04 Jun 2026 12:51:29 GMT</pubDate>
            <atom:updated>2026-06-04T12:51:29.226Z</atom:updated>
            <content:encoded><![CDATA[<p>As Mendix adoption grows, so does the number of applications. What often starts with a handful of apps can quickly expand into dozens — or even hundreds — spread across different business units, domains, and countries.</p><p>At that point, a common question emerges:</p><p><strong>“Do we still have a clear overview of our Mendix landscape?”</strong></p><p>Mendix Control Center provides organizations with a centralized view of their applications, which is a great starting point. However, in many organizations the real challenge isn’t finding the applications — it’s understanding their business context.</p><p>Questions such as:</p><ul><li>Which business unit owns this application?</li><li>In which country is it being used?</li><li>Which business capability does it support?</li><li>Is it still actively maintained?</li></ul><p>…are often much harder to answer than expected.</p><p>Without that context, an application portfolio can quickly turn into a long list of apps, rather than a meaningful overview of your digital landscape.</p><h3>The Missing Piece: Business Context</h3><p>As Mendix scales within an organization, applications are typically created by different teams for different business needs. Over time, this makes portfolio management increasingly challenging.</p><p>While Mendix already offers governance and portfolio management capabilities through Control Center, many organizations still struggle to consistently capture and maintain business-related information about their applications.</p><p>As a result, teams often run into challenges such as:</p><ul><li>Unclear ownership of applications</li><li>Difficulty reporting on applications by business domain or region</li><li>Limited alignment with enterprise architecture structures</li><li>Additional effort when preparing portfolio reviews, rationalization exercises, or strategic roadmaps</li></ul><p>The challenge is usually not a lack of applications or data — it’s a lack of structure.</p><h3>Using Project Categories to Create Structure</h3><p>One feature that can help address this is <strong>Project Categories</strong> in Sprintr.</p><p>Project Categories allow you to enrich Mendix applications with business metadata, making it easier to organize and manage your portfolio.</p><p>Examples include:</p><ul><li>Business Unit</li><li>Country or Region</li><li>Business Domain or Capability</li><li>Lifecycle Status</li><li>Criticality or Compliance Classification</li></ul><p>Instead of maintaining a flat list of applications, you create a portfolio that can be filtered, grouped, and analyzed from a business perspective.</p><p>You can read more about the feature here:</p><ul><li>Project Categories: <a href="https://docs.mendix.com/control-center/project-categories/">https://docs.mendix.com/control-center/project-categories/</a></li></ul><h3>Taking It One Step Further with Automation</h3><p>What makes Project Categories particularly interesting is that they are available through APIs.</p><p>This means categorization doesn’t have to remain a manual activity. Organizations can integrate Mendix portfolio data with existing governance processes and tooling.</p><p>For example:</p><ul><li>Synchronize application information with internal systems</li><li>Connect portfolio data to enterprise architecture repositories</li><li>Automate classifications based on ownership information</li><li>Enforce governance requirements before applications go live</li><li>Build reporting dashboards that combine technical and business insights</li></ul><p>This creates opportunities to embed Mendix portfolio management into the broader IT landscape, rather than managing it in isolation.</p><p>You can read more about the feature here:</p><ul><li>Project Category API: <a href="https://docs.mendix.com/apidocs-mxsdk/apidocs/project-category-api/">https://docs.mendix.com/apidocs-mxsdk/apidocs/project-category-api/</a></li></ul><h3>Why It Matters</h3><p>Portfolio management becomes increasingly important once organizations move beyond a few isolated Mendix applications.</p><p>The conversation shifts from:</p><p><strong>“Can we build applications quickly?”</strong><br>to<br><strong>“Can we manage them effectively at scale?”</strong></p><p>Having clear ownership, business context, and consistent categorization helps organizations make better decisions about governance, investments, architecture, and future growth.</p><p>Sometimes, the biggest improvements don’t come from adding new applications, but from gaining better visibility into the ones you already have.</p><h3>Final Thoughts</h3><p>Project Categories may seem like a relatively small feature, but they address a challenge many organizations encounter as their Mendix landscape matures.</p><p>By combining Control Center, Project Categories, and automation through APIs, organizations can create a portfolio that is not only visible, but also understandable and manageable.</p><p>And ultimately, that’s what portfolio management is about: turning a collection of applications into meaningful insight.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wRB6tarfORtKQHLjuD2kZQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7b16186b338" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Another IWD]]></title>
            <link>https://medium.com/@kasja/another-iwd-9450ccda5833?source=rss-b5e570f73bb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/9450ccda5833</guid>
            <dc:creator><![CDATA[Kasja Maksymiak]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 20:41:33 GMT</pubDate>
            <atom:updated>2026-03-02T20:41:33.684Z</atom:updated>
            <content:encoded><![CDATA[<p>𝗜’𝗺 𝗻𝗼𝘁 𝗰𝗲𝗹𝗲𝗯𝗿𝗮𝘁𝗶𝗻𝗴 𝗜𝗻𝘁𝗲𝗿𝗻𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝗪𝗼𝗺𝗲𝗻’𝘀 𝗗𝗮𝘆 𝘁𝗵𝗶𝘀 𝘆𝗲𝗮𝗿.</p><p>𝘐’𝘮 𝘥𝘰𝘯𝘦.</p><p>Done with the annual ritual.</p><p>Done with the same speeches.</p><p>Done with talking 𝘢𝘣𝘰𝘶𝘵 each other instead of 𝘵𝘰 each other.</p><p>Every year we repeat:</p><p>“𝗙𝗶𝘅 𝘁𝗵𝗲 𝘀𝘆𝘀𝘁𝗲𝗺, 𝗻𝗼𝘁 𝘁𝗵𝗲 𝘄𝗼𝗺𝗲𝗻.”</p><p>And yes, we should.</p><p>We need policy change.</p><p>Equal pay.</p><p>Safer work- and public places.</p><p>Real accountability.</p><p>But here’s the uncomfortable truth:</p><p>We’ve turned gender equality into a broadcast instead of a conversation.</p><p>Women speak.</p><p>Men listen politely.</p><p>Everyone posts.</p><p>Nothing fundamentally changes.</p><p>Because change doesn’t happen in hashtags.</p><p>It happens in uncomfortable dialogue.</p><p>And women — this part is for us too.</p><p>We often expect men to understand experiences we rarely invite them to truly explore:</p><p>• what safety calculations look like every day,</p><p>• what being interrupted repeatedly does to confidence,</p><p>• what invisible expectations feel like over time.</p><p>We demand awareness, but we don’t always invite men to have an equal conversation about it.</p><p>And men — I’m not blaming you for the gender gap.</p><p>But I am tired of hearing:</p><p>“It’s not my fault.”</p><p>“I don’t know any woman who experienced that.”</p><p>“But I don’t do that.”</p><p>If you don’t know a woman who has experienced gender bias, you probably haven’t asked enough questions — or the right ones.</p><p>Understanding requires effort.</p><p>Empathy requires imagination.</p><p>Leadership requires ownership — even when you didn’t create the problem.</p><p>Silence protects the status quo.</p><p>Real allies don’t just avoid being part of the problem.</p><p>They actively challenge it — especially among other men.</p><p>That’s what leadership looks like today: taking responsibility beyond your own experience.</p><p>So this year, I’m opting out of performative celebration.</p><p>No slogans.</p><p>No corporate cupcakes.</p><p>No one-day awareness campaign.</p><p>Just a simple ask:</p><p>🫶 Start conversations.</p><p>🫶 Ask uncomfortable questions.</p><p>🫶 Listen without defensiveness.</p><p>🫶 Hold each other accountable.</p><p>Equality will not be achieved by women talking louder. It will happen when all genders start talking and listening — differently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IWvwUaRemI5UA426pDft-Q.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9450ccda5833" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migrating your Mendix app to Git On-Premise]]></title>
            <link>https://medium.com/@kasja/migrating-your-mendix-app-to-git-on-premise-33165a217116?source=rss-b5e570f73bb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/33165a217116</guid>
            <dc:creator><![CDATA[Kasja Maksymiak]]></dc:creator>
            <pubDate>Mon, 23 Jun 2025 11:17:35 GMT</pubDate>
            <atom:updated>2025-06-23T11:17:35.289Z</atom:updated>
            <content:encoded><![CDATA[<p>By default, the code and files of all Mendix applications are stored in the Mendix online environment. However, you can store it in a system controlled by your own organization. This is a short how-to migrate your app from Mendix Git to Private Git.</p><h4>Important</h4><p>Please note that after migrating to Private On-Premise Git, you will not be able to use the following Mendix functionalities:</p><ul><li>Open App from Mendix Sprintr.</li><li>Choose Branch Line in the Studio Pro App Launcher.</li><li>Create Deployment Package in Mendix Sprintr.</li><li>Deploy to licensed node from Studio Pro modeler.</li><li>Use Mendix platform APIs such as the <a href="https://docs.mendix.com/apidocs-mxsdk/apidocs/app-repository-api/">App repository API</a>, <a href="https://docs.mendix.com/apidocs-mxsdk/apidocs/build-api/">Build API</a>, <a href="https://docs.mendix.com/apidocs-mxsdk/mxsdk/">Platform SDK</a>, <a href="https://docs.mendix.com/apidocs-mxsdk/apidocs/projects-api/">Projects API</a>, <a href="https://docs.mendix.com/apidocs-mxsdk/apidocs/epics-api/">Epics API</a>, and <a href="https://docs.mendix.com/apidocs-mxsdk/apidocs/user-management-api/">User management API</a></li></ul><h3>Moving Mendix repository to Private Git</h3><p>To import your Mendix project to GitHub follow these steps:</p><h4>Step 1: Prepare your Studio Pro modeler</h4><ol><li>Open your Mendix Studio Pro modeler.</li><li>Click <strong>Edit </strong>→ <strong>Preferences </strong>→ <strong>Version Control</strong> → <strong>Git</strong>.</li><li>Select the checkbox <em>Enable private version control with Git</em>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*VIe_ZhjUHhrf-rleEzfotg.png" /></figure><h4>Step 2: Create PAT</h4><ol><li>Go to <a href="https://user-settings.mendix.com/link/developersettings">https://user-settings.mendix.com/link/developersettings</a>.</li><li>Click <strong>New Token</strong>.</li><li>Select the Model repository checkboxes.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/691/1*48ys2pTTfk1nIx9MEBTs2A.png" /></figure><h4>Step 3: Copy the Team Server URL</h4><ol><li>Go to <a href="https://home.mendix.com/">https://home.mendix.com/</a> and open your app.</li><li>Open Team Server page and copy the Team Server URL.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nq9Pvb5WpRXZ6IVCvcakeQ.png" /></figure><h4>Step 4: Import Mendix project to Github</h4><ol><li>Go to <a href="https://github.com/">https://github.com</a>.</li><li>Click Import repository</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dtYkaJuCqTOhev8crM5vVw.png" /></figure><p>3. Fill in the following:</p><p>a) ‘The URL for your source repository’ → paste the Mendix Team Server URL.</p><p>b) Username → your company email address.</p><p>c) Password → your newly created Mendix PAT.</p><p>d) Owner → select Company GitHub instance<em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s81pVeGk1lFLba7F4AGGkg.png" /></figure><p>4. Click<strong> Begin import</strong>.</p><h4>Step 5: Create GitHub PAT</h4><ol><li>Go to <a href="https://github.com/settings/tokens">https://github.com/settings/tokens</a></li><li>Click <strong>Generate new token (classic)</strong>.</li><li>Select<em> ‘repo’ </em>and generate token.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*vk8jTcX4E49jaUej4Ac5tg.png" /></figure><p>4. Back on the GitHub PAT overview page click Configure SSO.</p><p>5. Under <em>‘Available to authorize’</em> → select [Company GitHub] click <strong>Authorize</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cydul6ebEvvrtWrDFdxwMg.png" /><figcaption>Authorized Single sign-on organization</figcaption></figure><h4>Step 6: Copy GitHub repository URL</h4><ol><li>Open the GitHub repository of your app.</li><li>Click <strong>Code </strong>and copy the HTTPS URL.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/472/1*S8fZa8HXKA8zw1GgiecHIg.png" /></figure><h4>Step 7: Open your Mendix project in Private Git in Studio Pro</h4><ol><li>Open your Studio Pro modeler.</li><li>Click Open <strong>Private App</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/945/1*5sw3aYbgao7yl3QPDIqIEw.png" /></figure><p>3. Fill in the App repository address that you have copied in step 6 and click <strong>Connect</strong>.</p><p>4. Fill in the following:</p><p>a) Username → your company email address.</p><p>b) Password → your GitHub PAT you have created in step 5.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*TtQM8jWH5nyp54cIJOcIlw.png" /></figure><h4>Step 8: Delete local project with the Mendix repository</h4><p>To avoid opening the wrong project, delete the local app project with the Mendix repository.</p><p>If you want to see if you have selected the correct project to open in your modeler, check if after selection you see the <strong>Choose Branch Line</strong> button. Projects in private git do <strong>NOT</strong> have a <strong>Choose Branch Line</strong> button <em>(see screenshot in step 7)</em>. You will also notice it in the top part of your modeler:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/1*SrkjpujXW0snWcJXIFZjsA.png" /></figure><h3>Working with Git On-Premise</h3><h3>Change branches</h3><p>When your app is in Private Git, you cannot choose a branch from the App Launcher <em>(see screenshot in step 7)</em>. The workaround is to open your app and click the following: <strong>Version Control</strong> → <strong>Manage Branch Lines</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/1*YvcpBSce5tm2ra-IzL9bKg.png" /></figure><h3>Deploying to Cloud environment</h3><ol><li>Create a deployment package in your Studio Pro modeler by clicking <strong>App </strong>→ <strong>Create Deployment Package</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/372/1*ShQIR_9nja1fse18vZe-7A.png" /></figure><p>2. Go to <a href="https://home.mendix.com/">Mendix</a> and open your app.</p><p>3. Click <strong>Environments </strong>→ <strong>Deployment Packages</strong>.</p><p>4. Click <strong>Upload a Package</strong> and select the newly created deployment package.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0HXxVLm5966sYfRHCnFDsQ.png" /></figure><p>To find your local deployment packages, open the local App directory by clicking <strong>App </strong>→ <strong>Show App Directory in Explorer</strong> → <strong>Releases</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/204/1*plAWVDuUi3H3LzBpzKM_Ow.png" /></figure><h3>Read more</h3><ul><li><a href="https://docs.mendix.com/refguide10/on-premises-git/">Working with Git On-Premises Version Control Server | Mendix Documentation</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33165a217116" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mendix Center of Excellence — Company onboarding]]></title>
            <link>https://medium.com/@kasja/mendix-center-of-excellence-company-onboarding-3cc5d58eaa83?source=rss-b5e570f73bb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/3cc5d58eaa83</guid>
            <dc:creator><![CDATA[Kasja Maksymiak]]></dc:creator>
            <pubDate>Thu, 05 Jun 2025 15:09:15 GMT</pubDate>
            <atom:updated>2025-06-05T15:09:15.122Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mendix Center of Excellence — Company onboarding</h3><p>How do you get your new Mendix developers quickly onboarded in your company’s Mendix ecosystem? Especially when your project management and documentation regarding Mendix are kept in different tools like Confluence, SharePoint, Azure DevOps etc.</p><p>Mendix has provided some cool features in the Mendix <a href="https://guidance.mendix.com/link/companyonboarding">Control Center</a> to help you out with it on a company level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fv3nB1a14bgAAEFmSZU8Jw.png" /></figure><h3>🔥 Landing page</h3><p>Set up a landing page for new developers with useful links to for example your internal company content: specific internal Confluence pages regarding guidelines or recommended academy learning paths and much more!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9orYvczaBy2UWaJE.png" /></figure><p>Pro tip: Check out the “<strong>Brand</strong>” page in Control Center where you can update your company branding with your company logo and cover image (banner). It will be automatically shown on your landing page.</p><h3>🔥 Onboarding email</h3><p>Send out automatically your own company onboarding email to people that create a new Mendix account with your company’s email-address. You can also link to your internal documentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*zbAVLm7NdA0Qc9KY" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3cc5d58eaa83" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mendix Center of Excellence — Roles & Permissions]]></title>
            <link>https://medium.com/@kasja/mendix-center-of-excellence-roles-permissions-f80642310351?source=rss-b5e570f73bb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f80642310351</guid>
            <dc:creator><![CDATA[Kasja Maksymiak]]></dc:creator>
            <pubDate>Mon, 24 Mar 2025 15:36:01 GMT</pubDate>
            <atom:updated>2025-03-24T15:37:27.021Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mendix Center of Excellence — Roles &amp; Permissions</h3><p>A continuation of my previous article <a href="https://medium.com/@kasja/manage-your-environment-alerts-in-mendix-cloud-bfbe3f4940da">Manage your environment email alerts in Mendix Cloud — Kasja Maksymiak — Medium</a>, but from a <a href="https://medium.com/@kasja/the-clash-of-the-titans-mendix-admins-c22ba7ce5c82">Mendix Company Admin</a> perspective.</p><p>When your Mendix landscape grows, it becomes more and more challenging to stay in control over the permissions of your Mendix applications.</p><p>You can decide to leave the ‘Manage Permissions’ management up to dedicated team member(s) of an app, but the risk is that when there’s no one to set the permissions, other team members get blocked in their work. You also loose control over what permissions are given out. For example: one lazy click away from providing full production database access to a junior developer.</p><p>But if you want to stay in control yourself, it’s a tedious work to set the permissions for each developer manually by hand. It also slows down the team’s efficiency as they need to contact the Mendix Center of Excellence each time they want their permissions changed.</p><p>Fear no more, there are two solutions to fix this!</p><h4>Frontend solution</h4><p>In <a href="https://controlcenter.mendix.com/">Control Center</a> under <strong>Roles and Permissions</strong> you can manage the company project roles and permissions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/290/1*5OroJ3RtxyLbCnXPklWJJA.png" /></figure><p>Here you can change the <strong>Business Engineer</strong> project role and set the project and node permissions to apply to everyone (existing and new project members) with the role Business Engineer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SqcHYzknW-lIXeqCyGMyGA.png" /></figure><p>If you set node permission of a certain role to <strong>Fixed</strong>, it will automatically update the permissions of all members with that particular role, for example Business Engineer. This means it will be applied to all existing members and all new members in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*dlUAhhtc30oO7PlMm7duqA.png" /></figure><p>You can set different settings for non-production and production environments. However, if you want to be able to set the permissions specifically per environment, the good old <strong>Custom </strong>permission settings are the way to go.</p><h4>Backend solution</h4><p>In case you need to use the <strong>Custom </strong>permission settings, you can also use the <a href="https://docs.mendix.com/apidocs-mxsdk/apidocs/deploy-api-4/">Mendix Deploy v4 API</a> to set the permissions instead of doing it manually in Sprintr (cloud.home.mendix.com).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2wAWmr0W9PMjXaQiJ25NcA.png" /><figcaption>Changing Custom Permissions manually in Sprintr</figcaption></figure><p>Be aware that in node permissions the UserID is still the member email address and <strong>not</strong> the UUID.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*7a5tH4K63xXYqQm2j-lwSA.png" /><figcaption>Changing Custom permissions using the Deploy v4 API</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f80642310351" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The clash of the titans — Mendix Admins]]></title>
            <link>https://medium.com/@kasja/the-clash-of-the-titans-mendix-admins-c22ba7ce5c82?source=rss-b5e570f73bb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/c22ba7ce5c82</guid>
            <dc:creator><![CDATA[Kasja Maksymiak]]></dc:creator>
            <pubDate>Tue, 11 Mar 2025 08:02:54 GMT</pubDate>
            <atom:updated>2025-03-11T08:19:53.011Z</atom:updated>
            <content:encoded><![CDATA[<h3>The clash of the titans — Mendix Admins</h3><p>Working with Mendix (as a Mendix Developer or as a Product Owner) you have probably heard about them numerous times: Mx Admin, Technical Contact, App Contact, Company Admin…But what is the difference between these ‘Mendix Gods’? And what are their superpowers?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VW6U9DRQBNx2Tw7zQizOHQ.png" /><figcaption>Mendix Admins</figcaption></figure><h3>Company Admin — ‘Mendix Admin’</h3><p>The Goddest of them all. The <a href="https://docs.mendix.com/control-center/company-settings/">Company Admin</a> has access to the entire Mendix Company portfolio including all company apps, Mendix (developer) accounts, private marketplace and company settings. All available in <a href="https://controlcenter.mendix.com/p/admin/dashboard">Control Center</a>.</p><p>More information about Control Center: <a href="https://docs.mendix.com/control-center/">Control Center | Mendix Documentation</a></p><h3>Project Admin — ‘SCRUM Master’</h3><p>The <a href="https://docs.mendix.com/developerportal/general/app-roles/">SCRUM Master</a> is the default app project <em>System role</em>. Other roles are Business Engineer, Product Owner, Application Operator etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*Uy9o4W7ASIKspm0Qna0SFg.png" /><figcaption>Roles &amp; Permissions overview in Control Center</figcaption></figure><p>The SCRUM Master project admin is automatically assigned to the Mendix (developer) account that creates the (app) project in Mendix. It has the permissions to the all functionalities in Mendix (Sprintr) Home.</p><p>More information: <a href="https://docs.mendix.com/developerportal/general/">Apps ‒ General | Mendix Documentation</a></p><h3>Cloud Admin — ‘Technical Contact’</h3><p>Where the Project Admin is mostly configuring the red part of Mendix Sprintr (see screenshot below), the <a href="https://docs.mendix.com/developerportal/general/app-roles/#technical-contact">Technical Contact</a> (TC) is responsible for the green part in Mendix Sprintr (see screenshot below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/402/1*DYJFpyp6Z9lXdbnj2K4P7A.png" /></figure><p>The Technical Contact is responsible for the following:</p><ul><li>Receiving notifications from Mendix about upcoming maintenance operations on the application;</li><li>Receiving alerts from your Mendix app when problems arise (for example, CPU load is high, running out of disk space);</li><li>Configuring the alert settings in the <strong>Monitoring</strong> tab of the cloud node;</li><li>Adjusting environments (for example, resize and add new environments);</li><li>Managing node permissions (if set to <em>custom</em>);</li><li>Managing licenses (as in, renewals, activations, and upgrades);</li><li>Being the first point of contact for the Mendix Support department.</li></ul><p>More information: <a href="https://docs.mendix.com/developerportal/general/app-roles/">App Roles | Mendix Documentation</a> and <a href="https://docs.mendix.com/developerportal/deploy/">Deployment | Mendix Documentation</a></p><h3>App Admin — ‘MxAdmin’</h3><p>The MxAdmin is the application administrator that is allowed to configure the technical aspects of your Mendix web/PWA/native Mendix app. So <strong>not</strong> in Mendix Sprintr, but by logging in in the app itself. For example: configure the Single Sign-On, email server credentials, refresh the app’s model reflection etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g3yY6c6l0LO2EVrrvtsAGA.png" /><figcaption>MxAdmin login</figcaption></figure><p>The name ‘MxAdmin’ can be changed to something else in the Studio Pro <em>Security Settings</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/1*jW89PY7hbcniXeXcy9LHxw.png" /><figcaption>Change MxAdmin name and local password</figcaption></figure><p>The password of MxAdmin for a specific environment can be changed in the ‘Cloud part’ of Mendix Sprintr under <em>Environment details</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uJKssx2z3GpWiMl41EyNzw.png" /><figcaption>Change MxAdmin password in Sprintr</figcaption></figure><p>In my opinion it applies to all Mendix Admin roles — please let only the experienced Mendix Developers use the Mendix Admin superpowers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c22ba7ce5c82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Office life with dating trends in 2025]]></title>
            <link>https://medium.com/@kasja/work-environment-with-dating-trends-in-2025-67d1b8930810?source=rss-b5e570f73bb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/67d1b8930810</guid>
            <dc:creator><![CDATA[Kasja Maksymiak]]></dc:creator>
            <pubDate>Fri, 14 Feb 2025 10:45:14 GMT</pubDate>
            <atom:updated>2025-02-14T10:58:13.935Z</atom:updated>
            <content:encoded><![CDATA[<p>🌹 <strong>𝗛𝗮𝗽𝗽𝘆 𝗩𝗮𝗹𝗲𝗻𝘁𝗶𝗻𝗲’𝘀 𝗗𝗮𝘆! </strong>🌹</p><p>What does Valentine’s Day have to do with work and Linkedin, you may ask?<br>Work relationships are<strong> 𝘀𝘁𝗶𝗹𝗹</strong> relationships. When working full time, we spend on average more time with our colleagues than with our spouses. Healthy work-related relationships are just as important as our private relationships!</p><p>Last november, the dating app Bumble has released their annual dating trends predictions for 2025: <a href="https://mashable.com/article/dating-trends-2025-according-to-bumble">https://mashable.com/article/dating-trends-2025-according-to-bumble</a><br>I hope these dating trends will translate into our work environment as well this year.</p><p>This is how I think the 2025 dating trends will <strong>and should</strong> be visible in our work-related relationships:</p><p>❤️ <strong>Return of the romance</strong><br>Embracing lovey-dovey gestures in private with “micro-mance”, just showing appreciation for each other in a small and cute way. This is a perfect opportunity to show appreciation for your colleagues in a non-romantic way! Don’t get me wrong, it’s nice to get a notification on Linkedin that you have received a digital appreciation post from someone, but nothing beats a compliment in real-life or a cupcake to celebrate a successful app release. Keep celebrating small successes and support each other in tough times. Also at work.</p><p>❤️ <strong>Stability is in</strong><br>Being open about future plans, needs and goals in life. I think it’s the way to keep your employees happy and engaged. It’s to understand these things from a work perspective as well. Personally, I think it deepens the work relationship when you can see it from both perspectives — private and work: plans, needs, goals and ambitions. Communication is key, in all types of relationships.</p><p>❤️ <strong>Keeping it real</strong><br>Giving authentic insights into the good and the bad things that are happening to us. Embracing vulnerability and creating a safe space to share the good and the bad. The good and bad things that happen at work affect our private life and vice versa. Some people prefer to keep their work- and private life separated, I 100% respect that. But I’m a strong advocate of sharing the good and bad of both worlds. In this way, I can better understand my colleagues and help them out a bit more after a difficult night because of a crying baby, for example.</p><p>❤️ <strong>Evolving masculinity</strong><br>Conversations on male stereotypes are a hot topic, not only at work but also in our private lives. I couldn’t be more excited about this 2025 (dating) trend! Let’s challenge all biases and stereotypes! I think we are starting to open up more about our own thoughts and feelings, instead of only sticking to the facts. I hope we will do this at work as well. It will hopefully solve a lot of unspoken frustrations.</p><p>It’s Valentine’s Day, now go do something nice for someone you appreciate! Not only today, but every day! ❤️</p><p>With lots of love,<br>Kasja ❤️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67d1b8930810" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>