User Settings in GrandMA3 User Settings in GrandMA3

Watch for Free

Enter your email to watch User Settings in GrandMA3

The Blueprint for Volunteer Excellence

MxU helps you fix Sunday with worship and tech volunteer training. Say goodbye to distracting services and team burnout.

WORLD-CLASS TRAINING LEARNING MANAGEMENT SYSTEM 1:1 COACHING

User Settings in GrandMA3

101 Lighting Lighting Console Configuration

Description

Users and profiles in GrandMA3 are more than just logins—they define how views are displayed, how settings are stored, and how your experience on the desk behaves. Understanding the difference between users and profiles helps streamline programming, especially when working with multiple operators, consoles, or onPC setups.

Users vs. Profiles

Every session runs under a specific user, but it's the profile that stores view configurations, screen layouts, and preferences. Profiles are portable and can be exported and imported across show files or systems:

  • Create or manage users under Menu > Settings > User Configuration.

  • Export a user profile to a USB stick using the soft key in the bottom menu.

  • Import that profile into a new show file to keep your views consistent.

User Access and Roles

Assign different access levels for various volunteers or team members:

  • Guest: Playback-only access—can run cues but can’t edit anything.

  • Program: Full programming control without administrative permissions.

  • Admin: Complete access to patching, users, programming, and playback.

This structure helps limit errors while still enabling productivity.

Managing Views Across Systems

Different users can also have different screen configurations. This is helpful when one station is running MA3D and another is running the main desk—you can change the display setup without affecting other operators.

Logging into a different user can be done from the user configuration screen or directly from the user pool. Once logged in, all corresponding views and screen setups will load with the profile.

Best Practices for Churches

Avoid creating a user for every volunteer. Too many users can bloat the file and create inconsistencies that make remote troubleshooting difficult. Instead, settle on a few shared profiles that work across your team and train everyone on those.

This way, transitions between services or volunteers stay smooth and predictable.