Skip to content

Admin Areas and Important Settings

What this page helps with

The admin area is where company-level administration is handled. This page explains the most important settings and decisions from an operator point of view.

Users

User administration controls who can access the product and with which responsibility level.

Typical topics:

  • role
  • active or inactive state
  • language
  • password or invitation handling
  • focused or broader UI visibility

Use this area when you need to:

  • invite a new user
  • disable access
  • change responsibility level
  • simplify what a user should see

Groups and tags

Groups and tags help control visibility and business scope.

Typical tasks:

  • define meaningful keys and names
  • keep inactive entries out of daily use
  • limit who can see which areas or resources

Good practice:

  • use stable naming
  • keep scopes understandable
  • avoid creating many overlapping visibility concepts

Mail and templates

This area controls how operational mails are sent and how templates are reused.

Typical topics:

  • mail host and port
  • security settings
  • sender address
  • test delivery
  • alert, mail, and report templates

Treat this area as operationally important, because changes here affect:

  • notifications
  • invitations
  • operational communication

Jobs, storage, and metrics

These areas help admins monitor how the tenant behaves over time.

Typical uses:

  • enable or disable jobs when appropriate
  • review storage growth
  • inspect metrics and durations
  • follow cleanup behavior

This information is especially useful when users report:

  • stale data
  • delayed updates
  • unusual growth
  • background processing problems

AI administration

Where AI-related admin pages are available, use them to control company-level defaults and availability rather than per-tenant behavior.

Common mistakes

  • granting roles too broadly
  • leaving old users active
  • using unclear group or tag structures
  • changing mail settings without testing
  • treating jobs and metrics as technical-only topics instead of everyday admin tools