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. Administration

Policies

The policy manager is used to configure the policies that you want to use to check your apps. AppControl has a default set of checks and all of these are included in the global policy. This is automatically created, configured and is checked automatically. The global policy can be configured to meet the needs of your organizations.

There are 3 different types of policies that can be managed in AppControl:

  • Global Policy. This will apply to all apps in your organization.

  • Group Policy. This policy applies to all apps in a specific app group.

  • App Policy. This policy applies to a specific app.

Policies are applied hierarchically (Global > Group > App), however only a single policy is used to check an app. If for instance a group policy is configured, this policy will be used instead of the global policy. If you want specific checks to be mandatory for all apps (or the entire policy), you can make the complete global policy mandatory or just specific checks in the global policy.

Depending on your user role you will see 1 or more tabs in the policy manager. If a policy has not yet been created for a specific group or app, you can choose to create a new policy. After opening the policy you can enable and disable specific policy checks. Some checks have additional options. Click on a check to view and configure its settings.

Policies are checked for compliance every hour.

For details about all available check types see the 'Checks' section of this documentation.

Policy Settings

Aside from the individual policy checks that you enable or configure, there are settings that apply to the entire policy:

  • Mandatory? If enabled, this policy applies to all apps in the scope (Global or Group) of the policy, and the configuration cannot be overridden by group or app administrators (for Global policies) or app administrators (for Group policies).

  • Ignore Marketplace modules? If enabled, policy checks will not apply to Marketplace modules.

  • Enabled? If set, this policy will be checked. If not, this policy will not be checked.

PreviousLogsNextPipelines

Last updated 6 months ago