Admin & Management

Topics Covered

  • User Management: Roles (User, Builder, Admin), permissions, and directory sync
  • Platform Settings: Remote Connection, License Management

Platform Settings

The Settings menu tab has two main sections:

  1. Overview
  2. User Management

These are presented as sub-tabs at the top of the content area.


Overview Section

Key features:

  • Master Server Connection
    • Displays connection status to the main server (e.g., jarvis.everworker.ai • Remote).
    • Includes a refresh button and connection state (e.g., “Connected”).
  • License Information
    • Shows current license tier (e.g., "Basic").
    • Displays the number of active workers (e.g., 12 / 23 workers)
  • Recent Users
    • Lists recently active or pending users, along with email and status.
    • “Manage users” button provides access to deeper user administration.

User Management Section

Key features:

  • Tabs for External and Microsoft Users
    • Allows switching between user types (likely reflecting different login methods).
  • User Table
    • Columns: Name, Email, Job Title, Status (e.g., Active, Pending), Roles (e.g., user, admin, builder), and Actions.
    • Each user can have multiple roles and a status badge for clarity.
    • Pagination and search functionality to filter users by name or email.
    • User Actions
      • Via a menu (three-dot icon), you can:
        • Resend Invitation (likely for users with “Pending” status).
        • Delete User.
    • Create New User Button
      • Provides a form or workflow to invite or register new users into the system.

Core Roles:

  • User: Can chat with Workers
  • Builder: Can create/edit Workers and manage memory
  • Admin: Full system access, including user roles, connectors, observability
  • Dashboard Viewer: Read-only access to analytics and dashboards

RoleBuild WorkersManage UsersManage Providers/ ConnectorView LogsAccess AnalyticsLicense ManagementMemory ControlQueue Management
UserNoNoNoNoNoNoNoNo
BuilderYesNoNoNoYes (Limited)NoNoNo
AdminYesYesYesYesYesYesYesYes
Dashboard ViewerNoNoNoNoYesNoNoNo
Log ReaderNoNoNoYesNoNoNoNo
Memory ManagerNoNoNoNoNoNoYesNo
Integrations ManagerNoNoYesNoNoNoNoNo
License AdminNoNoNoNoNoYesNoNo
Secrets ManagerPlannedPlannedYesNoNoNoNoNo
Queue ManagerNoNoNoNoNoNoNoNo

User

  • Primary Audience: End users (non-technical)
  • Access:
    • View and chat with pre-built Universal Workers
    • Manage personal session context (files, URLs)
    • Cannot build, edit, or configure workers
  • Limitations:
    • No access to Builder tools, Canvas, memory management, or logs

Builder

  • Primary Audience: Power users, AI engineers, solution designers
  • Access:
    • Full access to Universal Worker Builder and Canvas
    • Configure memory, connectors, providers
    • Use Worker Creator (Chat) to auto-generate workflows
    • Test and deploy workers
  • Limitations: -Cannot manage licenses or view admin dashboards unless granted dual role

Admin

  • Primary Audience: Platform owners, system operators
  • Access:
    • Everything a Builder can do, plus:
    • User management (roles, invites, sync)
    • Provider/connector management
    • System configuration (log cleanup, performance monitoring)
    • License allocation
    • Full access to Observatory

Super Admin (SUPERADMIN)

  • Primary Audience: Internal/system-level admin (usually EverWorker team)
  • Access:
    • Unrestricted platform access
    • Manages internal instance configuration, security, global settings
    • Controls all other roles and tenant-level settings
  • Not customer-facing

Dashboard Viewer

  • Primary Audience: Business stakeholders, analysts
  • Access:
    • Read-only access to analytics dashboards (ROI, usage, engagement)
    • No access to Builder tools or system configurations

License Administrator

  • Primary Audience: Procurement or IT role
  • Access:
    • Manage licenses, usage limits, and customer instance provisioning
    • Note: May not be a standalone UI role yet, but scoped internally for platform enforcement

Log Reader

  • Primary Audience: Technical support or QA
  • Access:
    • Read-only access to platform and system execution logs
    • Cannot modify workers or system settings

Memory Manager

  • Primary Audience: Knowledge admins
  • Access:
    • Add/remove memory items
    • Manage embedding configuration, chunking, tagging, and access controls

Integrations Manager

  • Primary Audience: DevOps / Integration lead
  • Access:
    • Configure, enable, or disable external system integrations
    • Manage connector settings, tokens, and test API access

Summary

EverWorker’s Admin & Management systems provide the structure and tools needed to run the platform securely at scale. From user roles and connectors to knowledge storage and observability, these systems ensure the platform remains governable, transparent, and enterprise-ready — while empowering Builders and Users alike.