Skip to content

Navigation by role

Role permissions in Rival Enterprise do more than gate specific API or publishing actions: they directly shape the left-navigation menu each user sees upon signing in.

Instead of cluttering the interface with restricted options or greyed-out controls, Rival dynamically renders a focused workspace tailored strictly to what each role needs to perform their primary function. For the underlying permissions behind these views, see the Capability matrix.

The platform divides navigation options into four core operational sections:

  • Workspace — the primary operational environment where active agents, tools, workflows, and execution activities are monitored and run daily.
  • Build — the development workspace where builders create new assets using RivalBot, visual drag-and-drop canvases, or custom code runtimes.
  • Marketplace — the central catalog discovery layer where users search, filter, test, and adopt approved AI assets across the organization.
  • Command Center — the administrative control hub providing high-level telemetry, security governance, team management, and workspace configuration options.
Navigation sectionEnterprise AdminEnterprise Team MemberStandard Rival User
WorkspaceOrganization-wideAssigned and team-scopedPersonal only
BuildFull accessFull accessFull access
MarketplaceInspect, run, and publishBrowse and adopt approved assetsPublic marketplace
Command CenterFull administrative accessOnboarding and Learn onlyNot shown

Primary goal: run, govern, and scale automated AI across the entire organization.

Interface focus: full, un-redacted platform access providing operational oversight, development tools, catalog approval queues, and deep administrative metrics.

Workspace

  • Agents — access, monitor, and run all organization-wide AI agents.
  • Tools — view and manage active functions, MCP server endpoints, and connectors.
  • Workflows — inspect active process pipelines and execution states.
  • Activity — global activity log detailing real-time execution events across all teams.

Build

  • Agent — construct new goal-oriented AI workers.
  • Workflow — assemble multi-step process pipelines.
  • Function — author custom code handlers in Python, JavaScript, or Lua.
  • MCP Server — configure Model Context Protocol server links.

Marketplace

  • Direct access to inspect, run, and publish agents, functions, MCP servers, and workflows to the organization’s private marketplace.

Command Center

  • Executive Summary — high-level platform adoption trends and ROI metrics. See Executive summary.
  • People and Access — manage user invites, SSO federation, SCIM sync, and role assignments. See People and access.
  • Adoption — departmental tool consumption rates and active user counts. See Analytics.
  • AI Governance — global guardrails, PII blocking rules, and model routing policies. See Governance framework.
  • Activity — central system audit trail and compliance logs. See Audit logs.
  • Requests — queue for pending marketplace submissions and connector access grants. See Requests.
  • Onboarding — workspace default configurations and zero-touch setup templates.
  • Learn — administrative setup guides and best-practice documentation.

Primary goal: execute daily tasks and build automations within pre-established company guardrails.

Interface focus: the same workspace, build, and marketplace tools as an admin, but paired with a streamlined Command Center that removes administrative governance overhead.

Workspace

  • Agents — access approved agents assigned to the user or team.
  • Tools — run team-assigned functions and approved connectors.
  • Workflows — execute multi-step business pipelines.
  • Activity — view personal and team-level execution activity.

Build

  • Agent — construct new goal-oriented AI workers.
  • Workflow — assemble multi-step process pipelines.
  • Function — author custom code handlers in Python, JavaScript, or Lua.
  • MCP Server — configure Model Context Protocol server links.

Marketplace

  • Browse, search, filter, and adopt admin-vetted assets across agents, functions, MCP servers, and workflows.

Primary goal: get individual work done independently in a non-enterprise, self-serve environment.

Interface focus: centered entirely around direct interaction with RivalBot, rapid tool generation, and the public marketplace, removing enterprise Command Center modules entirely.

  • Workspace — personal agents, tools, workflows, and personal execution activity.
  • Build — unrestricted creation tools for functions, MCP servers, workflows, and agents.
  • Marketplace — public marketplace browsing and personal tool management.