Administrator Guide

Managing tenant users in Toro Pulse

The Toro Pulse Admin page gives designated administrators a controlled way to manage shared tenant access. The primary use case is a single billed tenant account with additional end users who can collaborate under the same tenant workspace without exposing billing controls to every user.

Designed for shared enterprise teams Use the Admin page when one organization is billed at the tenant level and multiple users need governed access to dashboards, AI insights, and approval workflows.

What the Admin page supports

Permissions model

RoleIntended useTypical permissions
AdminTenant leadership, platform coordinators, or governance ownersManage tenant users, view tenant administration functions, and oversee governed workflow actions
OperatorOperational users who actively work inside the platformView reports and participate in governed actions such as approve, reject, and regenerate where enabled by the tenant
ViewerStakeholders who need visibility without operational change rightsRead-only access to assigned tenant information

Recommended operating model

  1. Keep a primary administrative account responsible for tenant governance.
  2. Add named end users instead of sharing credentials.
  3. Reserve Admin access for a small number of trusted users.
  4. Use Operator for day-to-day governed work.
  5. Use Viewer for leadership, audit, or read-only reporting access.

Creating a new user

From the Admin page, complete the required fields for Full Name, Email Address, Role, and Account Status. After the account is created, Toro Pulse can send a password reset email so the new user can establish their own credentials through the standard login flow.

Account status

Enabled users can sign in and access the platform based on their role. Disabled users remain associated with the tenant record but cannot actively sign in until re-enabled by an administrator.

Password resets

Administrators can initiate a password reset from the Admin page. The user receives an email similar to the main login password-reset experience, which helps maintain a consistent and professional onboarding process.

API layer overview

The Admin experience is backed by a tenant-scoped API layer. For customer-facing purposes, the important concept is that user-management requests are evaluated within the current tenant context and are only available to appropriately privileged administrative users.

Customer-facing note The API layer is intentionally tenant-scoped and role-aware so administrative actions remain contained to the correct organization workspace.