{"id":5514,"date":"2026-03-11T10:21:27","date_gmt":"2026-03-11T09:21:27","guid":{"rendered":"https:\/\/serviceautomation.eu\/why-municipalities-still-manually-create-accounts-in-zaaksysteem-and-rx-mission\/"},"modified":"2026-03-17T09:33:39","modified_gmt":"2026-03-17T08:33:39","slug":"why-municipalities-still-manually-create-accounts-in-zaaksysteem-and-rx-mission","status":"publish","type":"post","link":"https:\/\/serviceautomation.eu\/en\/why-municipalities-still-manually-create-accounts-in-zaaksysteem-and-rx-mission\/","title":{"rendered":"Why municipalities still manually create accounts in Zaaksysteem and Rx.Mission"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The complexity of the municipal application landscape<\/strong><\/h3>

Municipalities work with an ever-increasing number of applications. In addition to the core environment with Microsoft Entra (Active Directory), TOPdesk, and an HR system such as AFAS, employees use various domain-specific systems daily. <\/p>

Examples include:<\/p>

  • Zaaksysteem<\/p><\/li>

  • Rx.Mission<\/p><\/li>

  • Corsa<\/p><\/li>

  • ValidSign<\/p><\/li>

  • SmartDocuments<\/p><\/li>

  • iNavigator<\/p><\/li><\/ul>

    All these systems have their own accounts and authorizations. This is precisely where a challenge arises for many municipalities. <\/p>

    In practice, accounts in these systems are still often created and managed manually.<\/p>

    In practice: onboarding via tickets<\/strong><\/h3>

    When a new employee starts at a municipality, onboarding usually proceeds as follows:<\/p>

    1. HR enters the employee into AFAS<\/p><\/li>

    2. IT creates an account in Microsoft Entra \/ Active Directory<\/p><\/li>

    3. The service desk receives requests for access to applications<\/p><\/li><\/ol>

      For example:<\/p>

      • access to Zaaksysteem<\/p><\/li>

      • access to Rx.Mission<\/p><\/li>

      • permissions in Corsa<\/p><\/li>

      • an account in ValidSign<\/p><\/li><\/ul>

        These requests often arrive via TOPdesk tickets.<\/p>

        The service desk must then create an account or assign permissions in each system individually. For larger municipalities, this can involve 5 to 10 systems per employee. <\/p>

        Why this is becoming increasingly problematic<\/strong><\/h3>

        Manual account creation may seem manageable, but as the number of applications grows, more risks emerge:<\/p>

        • delays in onboarding<\/p><\/li>

        • incorrect authorizations<\/p><\/li>

        • accounts that remain active after termination of employment<\/p><\/li>

        • limited insight into who has access to what<\/p><\/li><\/ul>

          For municipalities working with sensitive information \u2013 such as personal data, permit files, and enforcement data \u2013 this can lead to compliance and governance issues.<\/p>

          Additionally, it simply takes up a lot of the service desk’s time.<\/p>

          Automation of account provisioning<\/strong><\/h3>

          More and more municipalities are therefore looking into automating account management.<\/p>

          The starting point is simple:
          HR data is the source.<\/p>

          When an employee is created in AFAS or changes roles, a workflow can automatically start to manage accounts and permissions.<\/p>

          For example:<\/p>

          AFAS \u2192 workflow \u2192 provisioning to:<\/p>

          • Microsoft Entra<\/p><\/li>

          • Zaaksysteem<\/p><\/li>

          • Rx.Mission<\/p><\/li>

          • Corsa<\/p><\/li>

          • ValidSign<\/p><\/li><\/ul>

            This turns account management into a streamlined process instead of manual work.<\/p>

            Conclusion<\/strong><\/h3>

            The number of applications within municipalities continues to grow. Without automation, the number of manual actions also increases. <\/p>

            By automating provisioning processes between systems such as AFAS, Microsoft Entra, TOPdesk, and municipal applications, IT departments can:<\/p>

            • accelerate onboarding<\/p><\/li>

            • reduce errors<\/p><\/li>

            • gain better insight into authorizations<\/p><\/li>

            • and improve compliance.<\/p><\/li><\/ul>

              How does this work within your municipality?<\/h2>

              Are accounts for applications such as Zaaksysteem or Rx.Mission still created manually, or is this already done automatically from HR or identity management?<\/p>

              We are curious about the issues you encounter regarding account management and automation.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

              \n\t\t\t\t\t
              \n\t\t\t\t
              \n\t\t\t\t\t\t\t
              \n\t\t\t\n\t\t\t\t\t\t<\/span>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t
              \n\t\t\t\t\t\t\t
              \n\t\t\t\t\tDo you have<\/span>\n\t\t\t\t\n\t\t\t\t\tquestions<\/span>\n\t\t\t\t<\/span>\n\t\t\t\t\tabout this?<\/span>\n\t\t\t\t\t<\/h5>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t
              \n\t\t\t\t\t
              Contact us!<\/h6>\t\t\t\t<\/div>\n\t\t\t\t
              \n\t\t\t\t\t\t\t
              \n\t\t\t\n\t\t\t\n\t\t\t\n\n\t\t\t\n\t\t\t
              \n\t\t\t\t\t\t\t\t
              \n\t\t\t\t\t\t\t\t\t\t\t\t