IntelliBuddies AI Command Center - FAQs

Administration and access

What is IntelliBuddies AI Command Center?

AI Command Center is the web application for managing, executing, monitoring, and administering IntelliBuddies automation. It brings together Agents, Local Agents, users, resources, triggers, and execution reports. See AI Command Center.

What functions does AI Command Center provide?

It provides automation management, user and role administration, licensing, shared assets, triggers, human tasks, and execution monitoring. See platform capabilities, administration, and shared assets.

What browsers can I use?

Use a browser listed in the server requirements. Browsers used for local web automation have separate client requirements.

Why does Microsoft Edge show two password reveal icons?

Edge's built-in password reveal control may appear alongside the login page's own control. If your Edge version exposes a password reveal setting, you can disable the browser control there. This affects display only; it does not change your AI Command Center credentials. See the sign-in interface.

Who can administer AI Command Center?

Users with the Administrator role manage tenant-level administration. Multitenancy also has a Super Administrator role for managing tenants. Other users receive access through their assigned permissions. See roles and tenant administration.

What is a tenant?

A tenant provides a separate organizational context within a multitenant deployment. The Super Administrator can create, edit, or disable tenants. See multitenancy and tenant management.

What are roles, and can I create custom roles?

Roles are collections of permissions that control access to platform entities and actions. Administrators can create custom roles for the access users need. See system roles and creating a custom role.

How do groups and inherited roles affect access?

Users can receive roles through group membership in addition to their directly assigned roles. Review both memberships and inherited roles when investigating access. See groups and inherited roles.

How do I configure LDAP or Azure Active Directory authentication?

Register an authentication provider, configure its directory connection, and set up user and group synchronization. See authentication providers, Microsoft Active Directory, and Azure Active Directory.

Why can another user not see or execute my automation?

Check the user's role permissions and the automation's sharing configuration. Running a Local Agent also requires access to the selected Buddy. See roles, Agent sharing, Local Agent sharing, and Buddy sharing.

Where can I see license allocation and feature availability?

Administrators can review allocation in Settings → Subscriptions → Licenses and activation in Features. See licenses, features, and Installation and Licensing FAQs.

Buddies and Smart Stations

Are Buddy and robot the same?

In IntelliBuddies, a Buddy is the execution host for local automation built with Process Designer. The term refers to the software robot that performs the automation. See Buddy types.

How is Assistant Buddy different from Smart Buddy?

Assistant Buddy provides local automation for its associated user and workstation. Smart Buddy executes centrally managed automation on a provisioned Smart Station using a configured Windows execution account. See Assistant Buddy, Smart Buddy, and Buddy management.

How do I assign and manage Buddies?

Use the Buddies page to configure, enable, disable, share, or delete Buddies as permitted by your role. Smart Buddy creation also requires the appropriate account, license, and Smart Station. See Buddy management.

What is a Smart Station, and how do I provision it?

A Smart Station is a physical or virtual workstation hosting Smart Buddies. Create the station with its exact hostname, copy the generated connection key, and configure that key in the workstation's Smart Station Agent. See creating a Smart Station and connecting the agent.

What are the Smart Station Service and Agent?

The Service manages execution and station status. The Agent is the workstation tray application used to connect or disconnect the station and inspect its state. See Smart Buddy architecture.

Which credentials does a Smart Buddy use?

The AI Command Center account is associated with the Buddy and its license. The Windows Execution Account supplies the Windows user context in which local automation runs. These accounts serve different purposes. See Windows Execution Account and AI Command Center Account.

What is the difference between foreground and background execution?

Foreground automation uses an interactive Windows session; Smart Buddy can create a session when required. Background automation can run under the configured account with or without an interactive session. Choose the process type according to its activities and application requirements. See execution account behavior.

How many processes can a Buddy execute at once?

A Buddy supports five parallel Buddy Worker Processes. Safe concurrency depends on the workflows: automation sharing a screen, keyboard, mouse, files, or other resources can conflict. See Buddy Worker Process and execution account guidance.

How many Buddies, processes, or users can I add?

Plan capacity using deployment sizing and applicable license limits rather than a single platform-wide count. Workload, server resources, and station configuration affect capacity. See server sizing, station sizing, and license limits.

Execution and triggers

What is a job, and how do I create one?

A job is one execution of a local process by a Buddy; the current UI describes these executions as Local Automation. Submit an automation manually, through a trigger, or through an API. For a manual run, select the Local Agent, Buddy, and input parameters. See running local automation.

How can I run a process at a particular time every day?

Create a Time Trigger and configure its execution target, parameters, and daily schedule. See time trigger criteria. Platform Agents have separate time trigger management.

What event triggers are available for local automation?

AI Command Center documents Time, Email, and File System triggers. Assistant Buddy additionally documents local File System, Database, Process, and Hot Key triggers. See Command Center triggers and Assistant Buddy triggers.

How do email and file events become workflow input parameters?

Configure event filters and bind event data to the process parameters in the trigger configuration. For file triggers, also check the monitored folder's permissions. See email trigger parameters and file trigger parameters.

Can I execute local automation from the command line?

Yes. Use Assistant Buddy's documented command-line interface and supply the required options for your process. See Assistant Buddy command-line execution.

Where can I inspect execution status and logs?

Use Reports → Local Automation for Buddy executions and Reports → Automation for platform Agent executions. Assistant Buddy also provides local job logs. See Local Automation, Agent automation details, and Assistant Buddy operations.

What should I check when scheduled automation does not run?

Check that the trigger is enabled, its target and parameters are correct, and its schedule or event criteria match your expectation. For local automation, check Buddy availability and station connectivity. Review execution and server logs for errors. See triggers, Smart Station, and server logs.

What do Agent health scores and states mean?

Health evaluation combines multiple dimensions over an evaluation window and can apply hard overrides. An inactive Agent is assessed differently from one with recent executions. See Agent health scoring and states.

Shared resources and diagnostics

What are Enterprise Variables?

Enterprise Variables store reusable configuration values and credentials. You can create them in AI Command Center or Process Designer, but edit and delete them through AI Command Center. See Enterprise Variables and creating variables.

How do I access Enterprise Variables in a process?

Use the supported activities or predicates to retrieve and update values. See accessing Enterprise Variables, Get EVars, and Set EVars.

Is it secure to store credentials in Enterprise Variables?

Credential-type variables are always encrypted. Other types support optional encryption, and sensitive values remain hidden during design. Use the documented credential type and access controls for shared secrets. See security and encryption.

How do Enterprise Variable scopes work?

Variables can have Global or User scope. A User-scoped variable takes precedence over a Global variable with the same name for that user. Two variables cannot share the same name within the same scope. See variable scopes.

When should I use a Connection instead of an Enterprise Variable?

Use a Connection to configure access to an external service or system. Use an Enterprise Variable for a reusable configuration value or credential accessed by workflow logic. See Connections and Enterprise Variables.

How do I move automation definitions and resources between environments?

Create an export job, download the package, and import it into the destination environment. Review the export and import reports and the documented behavior for each entity type. See export and import. Moving a suspended execution to another Agent version is a separate migration operation.

Can I restore something I accidentally deleted?

An administrator can restore items present in the Recycle Bin during its configured retention window. Permanently deleted items cannot be recovered from it. See Recycle Bin and restoration. Historical data removed by a Delete retention policy should not be treated as recoverable recycle-bin content.

What is the difference between audit, server, and execution logs?

Audit logs record user and entity actions. Server logs help diagnose platform operation. Execution logs show the progress and results of individual automation runs. See audit logs, server logs, and execution logs.

General Retention Policy

What is the difference between archiving and deleting retained data?

Archive moves eligible historical data to the configured archive database. Delete permanently removes it. Policies support Process Instances, RPA Jobs, Server Logs, and Audit Logs; Server Logs support Delete only. See policy scope and actions.

Can I create multiple policies for the same entity?

No. Only one policy per entity type is supported. If an entity is unavailable when adding a policy, check whether one already exists. See retention policy limitations.

What happens when I disable a policy?

Scheduled execution pauses, but the policy configuration remains available. Re-enable it to allow scheduled execution; Run Now is available for enabled policies. See enabling, disabling, and running policies.

Can I change the entity later?

No. You can edit retention days, action, status, and schedule, but changing the entity requires deleting the policy and creating another. See editing a policy.

How do I verify retention policy execution?

Choose View Log from the policy's context menu to inspect execution results. For Archive policies, also verify the configured archive connection. See policy actions and archive database connection.

Technical Retention Policy

What time format is supported, and can a policy run multiple times per day?

Daily schedules accept one or more execution times in 24-hour HH:MM format. Other supported schedules include Weekly, Monthly, Specific Dates, and Recurring. See scheduling options.

What should I check if a retention schedule did not run?

Verify the policy is enabled, its backend schedule exists, the scheduler service is healthy, and the time format and timezone are correct. Inspect the policy logs after an outage instead of assuming a missed run was replayed. See retention troubleshooting.

For Agent workflows and human tasks, see Agents and Human Tasks FAQs.