AppControl Docs
  • Introduction
  • Overview
    • Features
    • Product architecture
      • AppControl Repository
      • Policy Checks
    • Initial set up
      • AppControl User
      • Install package
      • Configure system
      • Add apps
      • Add users
      • Give permissions
    • User Roles & Access
    • Getting Started
      • Platform Administrator
      • App Owner
      • App Administrator
      • Developer
  • Dashboards
    • Platform
    • Alerts
    • App
      • Log Rule
    • Policies
      • Compare Revisions
    • Releases
      • Create Release
    • Tasks
      • Task Assignment
      • Task Details
    • Insights
      • Components
      • Reports
      • Users
      • Logs
  • Administration
    • Policies
    • Pipelines
      • Approval
      • Backup
      • Build
      • Call API
      • Check Policy
      • Deploy
      • Deploy Configuration
      • Notification
      • Start / Stop
    • Tasks
    • App Groups
    • Access Groups
    • System
      • Accounts
      • Notifications
      • System Status
      • System Logs & Tools
      • System Configuration
      • Repository
        • Log Solution
      • Product License
      • Management API
      • Mendix Configuration
    • Feedback
  • Checks
    • APIs
      • Published APIs must use authentication
    • App
      • Project security level
      • Project security enabled
      • Demo users enabled
      • Anonymous users enabled
      • Strong password policy
      • Default admin username changed
      • Anonymous user access restricted
      • Default admin user restricted
      • Use strong hash algorithm
      • Check user role security for consistency
      • Restrict users to a single session
      • Perform strict page URL checks
      • Project naming standards
    • Components
      • Components with vulnerabilities
      • Mendix runtime version age
      • Mendix runtime support status
      • Non platform supported components
      • Max component age
      • Average age components
      • Use latest version of Marketplace module
      • Use latest version of Marketplace widget
      • Use latest version of Mendix
      • Limit number of Java libraries
      • Limit number of widgets
      • Use minimum Mendix runtime version
    • Constants
      • Do not expose constants to client
    • Development
      • Last commit to production
      • Last commit to project
      • Project documentation standards
      • Project organization standards
      • Project logging standards
    • Domain Model
      • Default member access rights restricted
      • Use read only attributes in XPath constraints
      • Anonymous users can only change own data
      • Anonymous users cannot change unlimited length strings
      • Domain model standards
      • Anonymous user access restricted
      • Naming standards - Domain Model
      • Documentation standards - Domain Model
    • Enumerations
      • Naming Standards - Enumerations
    • Microflows
      • Incorrect date format
      • Incorrect empty string check
      • Empty variable used
      • Apply entity access when generating documents
      • Use inherited entities from System module
      • Web service calls with templates should be escaped
      • Naming Standards - Microflows
      • Logging Standards - Microflows
      • Documentation Standards - Microflows
    • Pages
      • Attributes in data views should be editable
      • Naming Standards - Page Flows
      • Documentation Standards - Pages
  • Support
    • Docs
    • Feedback
    • Tickets
    • Releases
    • System Status
    • User Details
Powered by GitBook
On this page
  1. Overview
  2. Getting Started

Platform Administrator

PreviousGetting StartedNextApp Owner

Last updated 6 months ago

AppControl supports Mendix platform administrators to automate and control the usage of the Mendix platform in their organization. After performing the , the following are useful features for your role:

  • Global Policy. The global policy in AppControl checks the state of all deployed Mendix apps to ensure that they are compliant with your standards. After installing AppControl a default set of policy rules is used. Configure the global policy to bring it in line with the needs of your organization (E.g. minimum Mendix versions, naming standards, etc.).

  • Global Pipelines. Global pipelines can be configured to enforce your global policies, and to ease the build and deployment process for DevOps teams. By default there are no global pipelines, and thus you will need to configure at least one global pipeline if you want teams to use a standardized process for building and deploying apps.

  • Global Tasks. Global tasks enable you to keep track of manual activities that need to be performed per app (E.g. compliance activities, certificate renewals, etc.). If there are common tasks that must be performed by all app owners or app administrators, create a global task for this need and assign it.

  • Insights. Insights gives you insight into the Mendix versions and Mendix Marketplace components used by all Mendix apps in your organization. Use Insights to answer questions such as 'Which apps are still using Mendix 8?' or 'Which apps are using the SAML module version older than 3.0?'.

  • App Groups. As your Mendix landscape grows it can be useful to assign responsibilities for groups of apps to distributed teams. In AppControl you can create app groups for this need. By creating an app group you can give rights to a group administrator to create group policies, group pipelines, and group tasks.

  • Access Groups. Access groups give you the ability to grant access rights in AppControl to groups of persons to a group of apps. This can be useful if (for instance) you have a group of apps that are managed by an internal or external app management team.

initial setup
Policies
Pipelines
Tasks
Insights
App Groups
Access Groups