Prerequisites for a Microix Modern Administrator

Creation date: 5/28/2026 11:50 AM    Updated: 9/22/2026 12:58 PM

To ensure a smooth transition to Microix Modern, the current Microix Administrator should meet the following basic prerequisites:


1️⃣ ✔️ Familiarity With Microix Workflow

  • Understands how Microix Workflow Modules are used and how it was specifically setup for your organization as Microix is highly customizable. 

  • Knows the organization’s approval process

  • Onboarding for new users includes creating their account, assigning them to the correct workflow, and granting the appropriate security permissions based on their role and Module (s) used and providing end user training. 

  • Knows how Requesters and Approvers use the system per Module|add-ons  (If the admin is brand new to Microix, an introductory paid training may be needed.)


2️⃣ 🔐 Access to the System

  • Has an active Microix Admin login

  • Has permission to manage workflows, users, security and documents


3️⃣ 🧩 Understanding of Organizational Structure

  • Knows who the Requesters, Approvers, and Finance staff are

  • Knows which departments use Microix

  • Understands any special approval rules or restrictions


4️⃣ 📘 Basic MIP Fund Accounting Knowledge

  • Understands the MIP GL structure

  • Knows how accounts, segments, and vendors are used

  • Understands how documents post to MIP


5️⃣ 🖥️ Completion of a Modern Walkthrough (when upgrading)

  • Has completed a Modern walkthrough

  • Understands breaking changes and new features


6️⃣ 🛠️ Ability to Make Administrative Decisions

  • Can approve workflow changes

  • Can add or remove users

  • Can adjust permissions

  • Can modify approval paths

  • Can manage document corrections


📘 When Formal Admin Training Is Recommended (Request a Quote)

Formal training is recommended when:

  • 🆕 The admin is new to Microix

  • 🔄 The organization recently upgraded to Modern and needs a refresher

  • 🔧 Workflows need restructuring

  • 🔐 Permissions or controls need tightening

  • 🧭 The admin will manage ongoing system maintenance

  • 📉 The organization wants to reduce reliance on Microix Support

  • When A System Review Is Recommended -A System Review is recommended when your Microix setup is not fully implemented or when you need help with best practices, workflow adjustments, or overall optimization. With your permission, a Microix consultant will review your current setup and identify any needed improvements, along with estimated hours to provide a quote.


KB-Core Admin Responsibilities 

KB-Core Daily Tasks Every Microix Administrator Must Know: 

· Adding a New User and Sending a Welcome Email

· How to Set or Review Security Permissions for a User

· Granting Permissions Using Role Templates

· Signing In as Another User (Admin Only)

· How to Inactivate a User Account and Reclaim a Web License

KB-Workflow & Approval Management-Everything related to routing, approvals, and document movement. 

· How to Create a New Workflow

· How to Add/Edit Approval Level Titles

· How to Assign a Substitute Approver

· Requiring Approvers to View Attachments Before Approving

· How to Change a Document’s Status / Move a Document

· Understanding My Document List, Approval List, and Document Search

KB-Document & Attachment Management-For Admins who maintain or troubleshoot documents. 

· How to Delete an Attachment

· Adding Attachment After Transfer to MIP

· Extending the Time Limit for Attachments in Approval Emails

· Why Documents Older Than X Years Are Not Visible

KB-Workflow Modules Modern Release History

This link helps Administrators stay informed about updates, fixes, enhancements, and new features in Microix Modern. 

Workflow Modules Modern Release History

Admins can use it to:

· Review recent updates and system changes 

· Identify new features that may benefit users 

· Check for bug fixes related to reported issues 

· Plan training or communication when new functionality is released 

· Confirm version compatibility before contacting support 

· Stay current on ongoing improvements to the platform 

Why it matters: Keeping up with release history helps maintain system stability, prepare users for changes, and ensure the organization benefits from new capabilities. 

Microix Inc. - Confidential/Subject to Change NOTE: Please contact us if attached file is missing (if applicable) send an email to sales@microix.net Tip: To zoom in, click on any image in this Article