Skip to main content

GeniSpace Advanced Features Guide

This guide covers advanced usage of the GeniSpace platform for experienced users. Each section maps to a real platform capability and links to its detailed documentation.

Usage & Billing Analytics​

The Analytics module in the Console gives you visibility into token consumption and spending across your space.

  1. Open the Analytics module from the Console sidebar
  2. Review your token balance, today's usage, and monthly usage
  3. Break usage down by service (Agent, Operator, and Assistant services)
  4. Compare periods (today vs. yesterday, this month vs. last month)
  5. Review recent transactions (consumption, recharge, bonus, refund, adjustment) and the member usage leaderboard
tip

On self-hosted deployments, the Analytics view focuses on the token usage card; the billing and transaction details apply to the SaaS edition.

See Analytics Overview for the full breakdown.

Advanced Workflows​

Workflows go well beyond linear node chains. The workflow engine supports control flow and multiple trigger types so you can model real business logic.

Control Flow​

Use control-flow nodes to branch and iterate inside a workflow:

  • If/Else — Evaluate a condition and route execution down the matching branch
  • For Each — Iterate over a list, running the contained steps once per item

Combine these with operator, task, and data-source nodes to build multi-step processes that react to data.

Triggers​

A workflow task can be started in three ways:

TriggerDescription
ManualRun on demand from the Console or via API
EventTriggered by a platform event
ScheduledRun automatically on a schedule (cron-style)

See Workflow Overview and Workflow Builder for node configuration details.

ConfigMap & Environment Variables​

Separate configuration from your workflows and operators using ConfigMaps. A ConfigMap is a container of key-value variables (with an optional sensitive flag) that can be referenced at execution time.

  1. Go to System settings → Configuration tab (or /settings?tab=configmaps)
  2. Create a ConfigMap and add configuration variables (e.g. DB_HOST, API_TOKEN)
  3. Mark sensitive values (passwords, API keys) accordingly
  4. Bind the ConfigMap to a task, or set a default ConfigMap for the space

In workflows and operator configurations, reference variables with the {{variableName}} template syntax. For example, an operator URL of https://{{API_HOST}}/api/v1/{{RESOURCE}} is resolved at execution time. Values are merged by priority: task-level environment variables (highest), then bound ConfigMaps, then the default ConfigMap.

See ConfigMap Overview and the Workflow Environment Variables Guide.

Access Control Done Right​

GeniSpace layers access control across spaces, applications, and agents. Combine these layers to grant least-privilege access.

Space Roles​

Membership in a space is governed by roles — Owner, Administrator, Member, and Viewer — which map to fine-grained RBAC permissions (for example space.workbench.read / write / admin). Most resource permissions derive from a member's space role, and custom roles can refine them.

See Space Management.

Application Access Control​

Applications carry their own visibility and access settings, so you can control who can open and manage each published application or installed GeniApp independently of other resources.

See Application Management.

Agent Access Control​

Agents are scoped to a space, and access is governed by the space's agent permissions (read / write / admin). When configuring an agent's tools, you can further restrict which operators, tasks, and data sources it may use.

See Agent Overview.

Exposing Tools to Agents (MCP)​

GeniSpace agents can call tools through the MCP (Model Context Protocol) system. MCP tools are configured per agent, so each agent exposes only the capabilities you grant it.

In the agent's MCP Tools configuration you can:

  • Enable MCP tool invocation for the agent
  • Enable built-in tools (platform-provided renderers and utilities)
  • Choose an operator strategy: no operators, all operators the user can access, or a specified subset (operator tools are named operator_identifier_method_identifier)
  • Choose a task strategy: no tasks, all tasks, or specified tasks (with type SCHEDULED / EVENT / MANUAL)
  • Choose a data-source strategy: no data sources, all data sources, or specified ones (with operations READ / CREATE / UPDATE / DELETE)
  • Add external MCP servers by endpoint to bring in third-party tools
tip

For specialized agents, prefer the "specified" strategies to limit each agent to only the operators, tasks, and data sources relevant to its role. This improves accuracy and security.

See the MCP Tool Invocation guide for full configuration, routing, caching, and the agent MCP API.

Extending the Platform: GeniApps, Marketplace & Shell​

Beyond agents and workflows, you can extend a space with packaged business applications.

  • GeniApps are platform-managed iframe applications (HR, inventory, CRM, short drama production, and more). Install them into a space from the Application Marketplace in Console → Applications. On install or upgrade, a GeniApp can provision its own managed data sources and database schema.
  • The Shell hosts installed GeniApps in an iframe alongside Console navigation, so they appear in the sidebar after installation.
  • You can also publish your own Workbench applications and embedded/external applications, then manage access to them per application.

See Applications Overview and Application Management.

Next Steps​