Docs
Search K

Appearance

What Is the Console? ​

The Console is MinuteView’s central control room. Any configuration that is system-wide (not per-user or browser-specific) lives here. If you ever need to change how MinuteView behaves, enable a module, wire up an integration, or manage who can do what—start in the Console.

Why the Console Exists ​

  • Single Source of Truth: All global settings in one place—no hunting through scattered menus.
  • Secure Administration: Only authorised administrators can make platform-wide changes.
  • Scalability & Consistency: Standardise how environments are configured across teams and sites.

First-Time Access (Fresh Install) ​

After installing MinuteView:

  • Only the MVAdmin account can sign in to the Console.
  • Use MVAdmin to bootstrap the system: create additional users, define roles, and grant Console access to others.

Once additional roles and users are created, Console access can be delegated appropriately.

What You Configure Here ​

Typical areas managed in the Console include (but are not limited to):

  • Global Settings – Preferred login type, log retention, service accounts, Automations Engine URL.
  • Authentication Integrations – e.g., Autodesk Vault details when using Vault as a login method.
  • API & Automations – Legacy PowerShell REST endpoints and the newer Automations Engine pointers.
  • Search Connection (Mesh) – Elasticsearch and AI service accounts for search and AI features.
  • User Management – Users, groups, roles, and linked external identities (Vault/ACC).
  • Database User – Credentials for MinuteView Server to connect to SQL (encrypted at rest).
  • Job History & Logs – View and manage system/job logs retained under your configured lifespan.

If a setting affects everyone (or the server), it should be in the Console.

What Is Not In the Console ​

  • Per-user preferences (themes, personal saved searches, local UI tweaks).
  • Client-side/browser-only settings tied to a single machine or session.

Typical Workflow for New Admins ​

  1. Log in as MVAdmin.
  2. Create Users & Roles: Define who will administer what. Grant Console access via roles.
  3. Set Core Services: Configure service accounts (AI, Elasticsearch), Automations Engine URL, and preferred login method.
  4. Review Legacy Areas: Note that legacy API Configuration may be replaced by Automations—plan migration accordingly.
  5. Verify Logs & Jobs: Ensure Job Logs Lifespan and history retention meet organisational needs.

Best Practices ​

  • Use Roles, Not Individuals: Assign permissions through roles and groups for easier maintenance.
  • Keep Credentials Current: Update Database User and service accounts when passwords or servers change.
  • Document Changes: Track who changed what and when; treat Console adjustments like code changes.
  • Limit MVAdmin Usage: Create separate admin accounts; reserve MVAdmin for emergencies or break-glass scenarios.

See Also ​

  • Global Settings – Core platform options.
  • User Management – Users, groups, roles, and linked accounts.
  • Service Accounts – Required for Mesh/AI and other integrations.
  • Job History – Debug and audit execution history.

Tentech