Use this glossary to quickly understand the key terms and concepts you’ll encounter while working with Autohive.

TermDefinition
AgentAn AI-powered assistant capable of carrying out tasks or answering questions. Agents can be general-purpose or specialised (e.g., Bumble The Biz Strategist).
AttachmentA file uploaded directly into a chat message for reference by agents or teammates.
Billing ownerThe member responsible for subscription payments and invoices. Usually also a workspace owner.
ChatThe real-time conversation interface where users and agents communicate. Supports direct, group, and DM conversations.
Command centerAdministrative modal (Hive Command Center) that consolidates your preferences and connections.
Content hubCentral repository for all documents, media, and knowledge used by agents. Supports versioning, folders, search, and permissions.
Cron expressionA string defining complex job schedules (e.g., 0 9 * * MON-FRI).
Custom roleA set of granular permissions to tailor access beyond built-in roles.
ExploreSection of Autohive where users discover, preview, and activate new agents.
History (job)The log of executions for a specific job, including status, duration, and outputs.
IntegrationA connection between Autohive and an external service (e.g., Slack, Google Drive, Webhooks).
JobA saved instruction that triggers an agent or workflow on a schedule or event.
Job run / executionA single occurrence of a job performing its task.
Job schedulerThe subsystem that calculates and triggers job runs based on cron, intervals, or dates.
MemberA human user who has access to a workspace. Members can have different roles and permissions.
MentionUsing @ in chat to reference an agent, member, or file, alerting them and providing context.
NotificationAn alert delivered via email, push, or in-app banner or label based on chat mentions, job outcomes, or admin rules.
Owner (workspace)Top-level role with full control, including billing, and all admin functions.
PermissionA specific capability (e.g., job:create, content:delete) that can be granted via roles.
RoleA collection of permissions assigned to members. Built-in roles include Owner, Admin, Member, and Viewer.
Run after triggerA job trigger type that starts a job after another job completes successfully.
SecretSecurely stored credential (API key, token) used by jobs or integrations.
Trigger (job)The mechanism that determines when a job runs, such as cron, interval, specific date, manual, or event.
WorkspaceA logical container for agents, content, jobs, and members, often representing a project or organisation.
WebhookHTTP endpoint used for inbound (triggering agents/jobs) or outbound (sending data) integrations.